You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When timestamps are equal, the tiebreaker field should be used to provide a consistent sort order. This field was being used only in the Context view, but not in the Discover view.
To reproduce this issue, go to Advanced Settings > Discover and set a tiebreaker field like offset,_doc.
The reason will be displayed to describe this comment to others. Learn more.
No tiebreakerField (I've set the field to empty in Advanced Configuration) leads to the following sort {"undefined":{"order":"desc","unmapped_type":"boolean"}.
This isn't a bug, it was intentional. The tiebreaker was needed in the context app because it uses search_after so we needed a guaranteed sort order. Discover has no such requirement so we don't use it there. Applying this setting in Discover doesn't really hurt anything, but it does make the sort code slightly more complex for no real benefit IMO. Also the setting is specifically called "context:tieBreakerFields", so if we're going to use it in Discover we should probably update the name of the setting and the description in the docs.
+1 for this. It would offer a pretty reasonable workaround for elastic/beats/7559
Use case; Using discover to analyze logs uploaded by filebeat which have millisecond collisions. Saved searches are a workaround but an extra-click barrier and less sharable. When using filebeat on indices using log.offset as a secondary sort field by default (or tiebreaker) seems to make a lot of sense.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wylieconlon
added
release_note:enhancement
Feature:Discover
Summary
When timestamps are equal, the tiebreaker field should be used to provide a consistent sort order. This field was being used only in the Context view, but not in the Discover view.
To reproduce this issue, go to Advanced Settings > Discover and set a tiebreaker field like
offset,_doc.Before:
After:
Closes #32221
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] This was checked for cross-browser compatibility, including a check against IE11- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers