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

[5.4] [context view] Use _doc for tie-breaking instead of _uid #12237

Merged
merged 1 commit into from
Jun 9, 2017

Conversation

weltenwort
Copy link
Member

Backports PR #12096

@weltenwort weltenwort self-assigned this Jun 8, 2017
Using fields with docvalues (like `_doc`) for tie-breaking yields
significantly better performance than using `_uid`, which lacks
docvalues at the moment. The downside is that sorting by `_doc` by
default is not stable under all conditions, but better than no
tie-breaking at all.

The new setting `context:tieBreakingFields` enables the user to
customize the list of fields Kibana attempts to use for tie-breaking.
The first field from that list, that is sortable in the current index
pattern, will be used. It defaults to `_doc`, which should change to
`_seq_no` from version 6.0 on.

In addition to just showing a notification, errors that occur while
loading documents from the database will be stored as part of the
`loadingStatus` along with a reason code (if known). This is used to
display more nuanced and helpful error messages to the user.

The first such error message indicates a missing or invalid tiebreaker
field required for sorting the context.
@weltenwort weltenwort force-pushed the backport/12096/5.4 branch from e51e3a1 to 10cf2b9 Compare June 8, 2017 14:04
@weltenwort
Copy link
Member Author

looks like unrelated failures - jenkins, test this

@weltenwort weltenwort merged commit ada213b into elastic:5.4 Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant