-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Add nested and object fields to field capabilities response #33803
Conversation
This commit adds nested and object fields to the field capabilities response. Closes elastic#33237
Pinging @elastic/es-search-aggs |
\cc @costin |
FTR, I've used this PR in SQL and it behaved as expected. |
while (dotIndex > -1) { | ||
String parentField = ft.name().substring(0, dotIndex); | ||
ObjectMapper mapper = mapperService.getObjectMapper(parentField); | ||
if (mapper != null) { |
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.
I was wondering whether this condition may ever be false, maybe mention sub fields in a comment? Should we also break as soon as responseMap.containsKey(parentField)
is true?
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.
Should we also break as soon as responseMap.containsKey(parentField) is true?
If we start from the leaf, yes, I pushed
235df36 to reverse the iteration order.
This commit adds nested and object fields to the field capabilities response. Closes #33237
Extend querying support on multiple indices from being strictly identical to being just compatible. Use FieldCapabilities API (extended through elastic#33803) for mapping merging. Close elastic#31837 elastic#31611
This commit adds nested and object fields to the field capabilities response. Closes #33237
This commit adds nested and object fields to the field capabilities response.
Closes #33237