Document the limitation around field aliases and percolator queries. #40073
Conversation
This file contains hidden or 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
Currently if a field alias is updated, any percolator queries that contain the alias will still refer to its old target. This PR documents the issue while we look into addressing it. Relates to elastic#37212.
jtibshirani
added
>docs
Collaborator
|
Pinging @elastic/es-search |
cbuescher
approved these changes
Mar 15, 2019
Contributor
Author
|
Thanks @cbuescher for the review. |
jtibshirani
added a commit
that referenced
this pull request
Mar 15, 2019
Currently if a field alias is updated, any percolator queries that contain the alias will still refer to its old target. This PR documents the issue while we look into addressing it. Relates to #37212.
jtibshirani
added a commit
that referenced
this pull request
Mar 15, 2019
Currently if a field alias is updated, any percolator queries that contain the alias will still refer to its old target. This PR documents the issue while we look into addressing it. Relates to #37212.
jtibshirani
added a commit
that referenced
this pull request
Mar 15, 2019
Currently if a field alias is updated, any percolator queries that contain the alias will still refer to its old target. This PR documents the issue while we look into addressing it. Relates to #37212.
jtibshirani
added a commit
that referenced
this pull request
Mar 15, 2019
Currently if a field alias is updated, any percolator queries that contain the alias will still refer to its old target. This PR documents the issue while we look into addressing it. Relates to #37212.
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Mar 16, 2019
…te-size-hard-failure * elastic/master: use shell with JAVA_HOME for starting archive (elastic#40118) Remove Migration Upgrade and Assistance APIs (elastic#40075) Revert "Fix IndexSearcherWrapper visibility (elastic#39071)" Remove transport name from tcp channel (elastic#40074) Document the limitation around field aliases and percolator. (elastic#40073) SQL: Refactor Literals serialization method (elastic#40058)
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Mar 16, 2019
…size-7.0 * elastic/7.0: Document the limitation around field aliases and percolator. (elastic#40073)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Currently if a field alias is updated, any percolator queries that contain the
alias will still refer to its old target. This PR documents the issue while we
look into addressing it.
Relates to #37212.