-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Add warning of incomplete Kibana support to nested fields #107971
[Docs] Add warning of incomplete Kibana support to nested fields #107971
Conversation
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-search (Team:Search) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thomasneirynck might make sense to add to the Using ESQL in Kibana limitations too for visibility
@stratoula will have more enlightened opinion on this one, I think we agreed that adding to Kibana ESQL limitations might be overkill |
@leemthompo this is the nested fields docs so mentioning ES|QL limitations doesnt make sense there. Do you mean that we need to add the limitations on the kibana docs? Let's align on the ES|QL docs, I want to introduce some changes. |
💚 Backport successful
|
Adds a warning to the docs of nested fields to indicate incomplete Kibana support.
This is a long standing limitation (elastic/kibana#1084).
It would be useful to warn users of this gap in support before they are starting to model their data.