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
{{ message }}
This repository has been archived by the owner on Aug 9, 2022. It is now read-only.
Right now the filtering is directly based on on the field names in the index. Can this be made user friendly, example durationInNanos is not user friendly. If this can be changed as latency (in ms) and the at the query layer convert to nanos and apply it in filter.
Also, the filter only supports is, in between and not in between, equal to operation can we support less than, greater than instead?
The text was updated successfully, but these errors were encountered:
This behavior is similar to Kibana Discover. If you leave one side blank in in between, it will become negative infinity or positive infinity, which is same as less than or greater than
I understand that its based on kibana, thats why called it as a new enhancement. I don't think this filtering is customer friendly, we should think of ways to make this easy.
Right now the filtering is directly based on on the field names in the index. Can this be made user friendly, example
durationInNanos
is not user friendly. If this can be changed aslatency (in ms)
and the at the query layer convert to nanos and apply it in filter.Also, the filter only supports
is, in between and not in between, equal to operation
can we support less than, greater than instead?The text was updated successfully, but these errors were encountered: