Skip to content
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

Support unmapped fields in search 'fields' option #65386

Merged
merged 10 commits into from
Dec 1, 2020

Conversation

cbuescher
Copy link
Member

Currently, the 'fields' option only supports fetching mapped fields. Since
'fields' is meant to be the central place to retrieve document content, it
should allow for loading unmapped values. This change adds implementation and
tests for this feature.

Closes #63690

Christoph Büscher added 2 commits November 23, 2020 16:40
Currently, the 'fields' option only supports fetching mapped fields. Since
'fields' is meant to be the central place to retrieve document content, it
should allow for loading unmapped values. This change adds implementation and
tests for this feature.

Closes elastic#63690
@cbuescher cbuescher added >enhancement :Search Foundations/Mapping Index mappings, including merging and defining field types v8.0.0 v7.11.0 labels Nov 23, 2020
@elasticmachine elasticmachine added the Team:Search Meta label for search team label Nov 23, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@cbuescher cbuescher force-pushed the unmapped-fields-63690 branch from 3193e0d to 81b05d3 Compare November 24, 2020 11:42
Copy link
Contributor

@jtibshirani jtibshirani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The overall approach looks good to me, I left some detailed comments.

@cbuescher
Copy link
Member Author

@jtibshirani thanks a lot for your review so far, I pushed an update that should address your comments.

Copy link
Contributor

@jtibshirani jtibshirani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some small final comments (accidentally split across two reviews).

@cbuescher
Copy link
Member Author

@jtibshirani I pushed another update to the branch and think I adressed your additional comments, thanks. Anything else you think needs doing here before merging?

Copy link
Contributor

@jtibshirani jtibshirani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I left one last note about an open comment, but it looks ready to merge after we sort that out.

@cbuescher cbuescher merged commit 3c3a432 into elastic:master Dec 1, 2020
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this pull request Dec 1, 2020
Currently, the 'fields' option only supports fetching mapped fields. Since
'fields' is meant to be the central place to retrieve document content, it
should allow for loading unmapped values. This change adds implementation and
tests for this feature.

Closes elastic#63690
cbuescher pushed a commit that referenced this pull request Dec 3, 2020
Currently, the 'fields' option only supports fetching mapped fields. Since
'fields' is meant to be the central place to retrieve document content, it
should allow for loading unmapped values. This change adds implementation and
tests for this feature.

Closes #63690
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Meta label for search team v7.11.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support unmapped fields in search 'fields' option.
4 participants