Remove support for expression based scripted fields #14310
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
jenkins, test this |
Bargs
force-pushed
the
removeExpressions
branch
from
ff27812 to
ac7b39c
Compare
|
jenkins test this |
Bargs
force-pushed
the
removeExpressions
branch
from
d45d2ba to
6be4439
Compare
Bargs
force-pushed
the
removeExpressions
branch
from
6be4439 to
71212d5
Compare
bmcconaghy
approved these changes
Nov 13, 2017
2 tasks
This was referenced Sep 15, 2020
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #14216
Related #14214 (it's probably easier to review #14214 first)
This PR removes the ability to create scripted fields with the
expressionlanguage. It also adds an error message to the scripted field list page if anyexpressionscripts already exist which instructs the user to convert all their scripts to painless.