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
Describe the bug
The system allows setting custom tiebreaker fields in advanced settings ([currency,category]). When these fields don't exist or aren't sortable in a particular index pattern, the system fails instead of falling back to a reliable default like _doc. This creates a poor user experience where the context view fails completely without clear indication of why or how to fix it.
So tieBreakerField here appears to be a secondary sorting field used to ensure consistent ordering when multiple documents have the same timestamp value.
Describe the bug
The system allows setting custom
tiebreaker
fields in advanced settings ([currency,category]). When these fields don't exist or aren't sortable in a particular index pattern, the system fails instead of falling back to a reliable default like_doc
. This creates a poor user experience where the context view fails completely without clear indication of why or how to fix it.So
tieBreakerField
here appears to be a secondary sorting field used to ensure consistent ordering when multiple documents have the same timestamp value.The
fetchAnchorRow
call will fail immediately because the tieBreakerField validation occurs at the start:If no valid
tieBreakerField
, for examplecurrency
for sample flights, these will happen:To Reproduce
Steps to reproduce the behavior:
Expected behavior
a fall back and not break usage
OpenSearch Version
all
Dashboards Version
all
The text was updated successfully, but these errors were encountered: