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 global ordinals in top_metrics #64967

Merged
merged 4 commits into from
Nov 16, 2020

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Nov 11, 2020

Adds support for fetching keyword and ip fields in top_metrics.
This only works if we can get global ordinals for those fields so we
can't support the entire keyword family, but this gets us somewhere.

Closes #64774

Adds support for fetching `keyword` and `ip` fields in `top_metrics`.
This only works if we can get global ordinals for those fields so we
can't support the entire `keyword` family, but this gets us *somewhere*.

Closes elastic#64774
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (:Analytics/Aggregations)

@elasticmachine elasticmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Nov 11, 2020
@nik9000 nik9000 force-pushed the global_ords_top_metrics branch from 0384f91 to 59e7cf5 Compare November 11, 2020 22:24
@nik9000
Copy link
Member Author

nik9000 commented Nov 12, 2020

run elasticsearch-ci/2

Copy link
Member

@not-napoleon not-napoleon left a comment

Choose a reason for hiding this comment

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

I think this is fine. I like that we're able to leverage the VSRegistry for top metrics now. I'm still not sure the MultiValuesSourceConfig logic is the right long term solution, but I don't have a better plan and I have no interest in digging into it now, so there's no reason to block on that.

@nik9000
Copy link
Member Author

nik9000 commented Nov 16, 2020

I think this is fine. I like that we're able to leverage the VSRegistry for top metrics now. I'm still not sure the MultiValuesSourceConfig logic is the right long term solution, but I don't have a better plan and I have no interest in digging into it now, so there's no reason to block on that.

Yeah. I didn't have any good ideas other than "don't do this now and tangle it up in support for bytes". It can come later, yeah.

@nik9000 nik9000 merged commit 450fb55 into elastic:master Nov 16, 2020
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Nov 16, 2020
Adds support for fetching `keyword` and `ip` fields in `top_metrics`.
This only works if we can get global ordinals for those fields so we
can't support the entire `keyword` family, but this gets us *somewhere*.

Closes elastic#64774
nik9000 added a commit that referenced this pull request Nov 16, 2020
Adds support for fetching `keyword` and `ip` fields in `top_metrics`.
This only works if we can get global ordinals for those fields so we
can't support the entire `keyword` family, but this gets us *somewhere*.

Closes #64774
@pugnascotia pugnascotia changed the title Support global ords in top_metrics Support global ordinals in top_metrics Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Aggregations Aggregations >feature Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v7.11.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Keyword support or alternative for top_metrics aggregation
4 participants