-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Discover] Fix filtering out custom meta fields of Elasticsearch plugins enhanced documents #137147
[Discover] Fix filtering out custom meta fields of Elasticsearch plugins enhanced documents #137147
Conversation
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
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.
lgtm
@elasticmachine merge upstream |
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.
Followed your instructions to test and it works as expected, LGTM 👍
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @kertal |
…ins enhanced documents (elastic#137147) * Restoring the ability of showing custom meta fields like _size (cherry picked from commit 6323628)
…ins enhanced documents (elastic#137147) * Restoring the ability of showing custom meta fields like _size (cherry picked from commit 6323628)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ins enhanced documents (elastic#137147) * Restoring the ability of showing custom meta fields like _size (cherry picked from commit 6323628) # Conflicts: # src/plugins/data/common/search/tabify/tabify_docs.ts
Summary
In #114517 multiple flattening of documents implementations were unified. This caused a bug with meta fields. The implementation assumed meta fields would match a given set of meta fields, filtering out all other fields. However, there's a way to extend the set of meta fields in Kibana with Elasticsearch plugins like the Mapper Size Plugin
There was not way to view the
_size
meta field in Discover (apart from the JSON view). This fix changes the implementation to exclude the fields that should not be merged ('_source', '_type')Testing
https://www.elastic.co/guide/en/elasticsearch/plugins/current/mapper-size.html
yarn es archive https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-8.3.2-darwin-aarch64.tar.gz
cd .es/elasticsearch-8.3.2-darwin-aarch64
./bin/elasticsearch-plugin install mapper-size
xpack.security.enabled: false
in./config/elasticsearch.yml
ES_PATH_CONF=./config ./bin/elasticsearch
ines/elasticsearch-8.3.2-darwin-aarch64
elasticsearch.ignoreVersionMismatch: true
in yourconfig/kibana.dev.yml
_size
tometaFields
of Advanced settings_size
and ingest data like it is described in https://www.elastic.co/guide/en/elasticsearch/plugins/current/mapper-size-usage.html_size
should be displayed with a value when expanding a document, and you can add the field to Discover's document explorerFixes #121394
Checklist