-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Switch to field_caps API #11014
Comments
w00t |
Nice! @spalger - Are you planning to remove all uses of For example, I believe Kibana uses |
@skearns64 Not as part of this specific ticket, but that will be the case after the linked meta issue for cross-cluster is complete. Though we won't be outright removing field_stats in the same version, we'll just deprecate that option for index patterns and remove it in a future major. |
@epixa @spalger @skearns64 I removed the shard limits in the upcoming 5.4 release so we should be able to just query instead of pre-select the indices. |
here is the issue elastic/elasticsearch#24012 |
@s1monw nice! |
in which version will @it be fixed? |
A part of #11011
With elastic/elasticsearch#23007 elasticsearch added a new API that provides a more integration-friendly look into the capabilities of fields in elasticsearch indexes. We should migrate to this API which is backed by mappings and will fix some unfortunate bugs introduced when we switched our field-capability-awareness to use the field stats API.
The text was updated successfully, but these errors were encountered: