Repository navigation
Discover does not use tiebreaker sort order #32221
Description
Activity
Pinging @elastic/kibana-app
I can confirm this is still an issue in Kibana 7.1.1 in the Discover App view.
This issue has been fixed by #41918
Reacted by Jennifer Campion and Mike ThompsonOn 7.7.0 I feel like i am still seeing this problem? I am needing to add the log.offset field, then sort by descending to get anything to show up in the right order
Reacted by kristopherdick-clcI have installed ELK 7.9.2 and can confirm that this does not seem to work anymore in the "Discover" view!
I added a numeric field in logstash which adds nanoseconds and is sortable and configured this new field as "tie breaker" field.It only seems to work if I manually add my new nanoseconds-field to the discover view (as column) and then sort by it. But this is a) a manually needed step for each user and b) wastes display space because of the additional column.
Actually when I look at the comments of #41918: it describes multi-field-sorting directly in the discover view. This does work (as I described above). But this issue here describes imho another problem: the tie-breaker-configuration does not work as I would expect it from the documentation => thus this issue here might never have been fixed at all !?
Reacted by kristopherdick-clc, Robin Schneider, Sergej Zagursky, Dukejung, Christian Gudrian and Adrian Baker
This is a bug with the discover view. In this screenshot, the expected behavior is that the
offsetfield would be sorted, because thecontext:tieBreakerFieldsis set tooffset,_docin advanced settings.The "view surrounding documents" view, or context view, uses the tiebreaker fields to determine sort order. The Discover view should also use the same sort order.
There are some related issues with the context view: #12937 #18647