-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Field stats API skips geo_point fields #20707
Comments
@jpountz could you take a look at this? |
--------- **Commit 1:** Update expected table headers to fix functional test * Original sha: f65c9b5 * Authored by Matthew Bargar <[email protected]> on 2016-09-26T12:40:41Z **Commit 2:** [indexPatterns] add workaround for elastic/elasticsearch#20707 * Original sha: 22c6f7c * Authored by spalger <[email protected]> on 2016-09-30T10:21:07Z
--------- **Commit 1:** Update expected table headers to fix functional test * Original sha: f65c9b5 * Authored by Matthew Bargar <[email protected]> on 2016-09-26T12:40:41Z **Commit 2:** [indexPatterns] add workaround for elastic/elasticsearch#20707 * Original sha: 22c6f7c * Authored by spalger <[email protected]> on 2016-09-30T10:21:07Z
The current behaviour of this API is to ignore all fields for which we do not know how to compute stats. Geo points are fixable, but should we add other fields like geo shapes as well as meta fields such as |
My naive opinion is that all values that work as "field" identifiers in queries or aggregations should be included in the stats. |
--------- **Commit 1:** Update expected table headers to fix functional test * Original sha: 8392fa0be6cb7bc2f23661ca921e15f07959fc85 [formerly f65c9b5] * Authored by Matthew Bargar <[email protected]> on 2016-09-26T12:40:41Z **Commit 2:** [indexPatterns] add workaround for elastic/elasticsearch#20707 * Original sha: 351c30b1541e72065abf8f3dcc4c3cee9a97fc1f [formerly 22c6f7c] * Authored by spalger <[email protected]> on 2016-09-30T10:21:07Z Former-commit-id: 7a13d9e
This seems to have been fixed by #21947. After that though the field stats API has been removed. |
Elasticsearch version: master
Plugins installed: none
JVM version: 1.8.0_102
OS version: macOS Sierra
Description of the problem including expected versus actual behavior: fields of type
geo_point
are not described in the_field_stats
outputSteps to reproduce:
sense requests: https://gist.github.com/spalger/72050d99ee9dc5a4ee8d1186e9cc05c9
which results in a matching filter, but no
pin.location
field listed in the field_stats outputThe text was updated successfully, but these errors were encountered: