-
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
Improve Top Hit aggregation "field" names #54460
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
Thanks, I never would have guessed this! |
Here's a suggestion: Value field Order field |
Looks like this is affecting users in 7.5, if I'm reading this correctly: https://discuss.elastic.co/t/kibanas-top-hits-aggregation-sort-by-field-broken/216971 |
@sulemanof can this issue be closed? Seems like #56367 fixed it, right? |
@flash1293
Then yes, it can be closed. |
@gchaps Do you think the current state is fine? |
@flash1293 Yes, I think the current state is ok. |
Currently the top hit aggregation in the visualize editor has two fields, labeled "Field", without any further explanation. This can be very confusing and it would make sense improving this form slightly:
The first "Field" selector allows selecting which field the value should be taken from (and then also how to aggregate the value in case we get the last n (in the screenshot 100) values from this field. For numerical fields this can be an aggregation like avg/sum, for strings it can be concatenated.
The second "Field" is belonging with the "Order" and actually defining by which field the documents are sorted to retrieve the top n from it (often users will use a timestamp here descending to get the last x documents matching).
I would suggest we rename those labels slightly, to something like "Order Field" and "Value Field", and give them a help icon with a tooltip, giving some short description how they behave?
@cchaos @gchaps either of you have some input for this?
The text was updated successfully, but these errors were encountered: