[DOCS] DISSECT does not support reference keys #102002
Merged
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
abdonpijpelink
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-ql (Team:QL) |
|
Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL) |
💚 Backport successful
|
abdonpijpelink
added a commit
to abdonpijpelink/elasticsearch
that referenced
this pull request
Nov 10, 2023
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 10, 2023
davidkyle
pushed a commit
to davidkyle/elasticsearch
that referenced
this pull request
Nov 13, 2023
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.
The
DISSECTcommand does not support reference keys. This PR removes reference keys from the "Data processing" documentation, and adds the lack of support as a limitation.While working on this, I noticed we have documented Grok limitations that are not on the "Limitations" page. Adding those in this PR too.