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
We have a date dimension parameter as part of star-tree index mapping. As part of date dimension, the users can specify up to 3 calendar intervals.
These calendar interval by definition and logic are same as the calendar intervals present in date histogram aggregator.
Since the cardinality of the date field is quite high, we use the calendar intervals to round the date as per the calendar interval.
The defaults are half_hour and minute.
Since we round off the original timestamp with the specified calendar intervals , there will be results from star tree which are different from original query.
Describe the solution you'd like
Related component
Search:Aggregations
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
Meta - #15257
We have a date dimension parameter as part of star-tree index mapping. As part of date dimension, the users can specify up to 3 calendar intervals.
These calendar interval by definition and logic are same as the calendar intervals present in date histogram aggregator.
Since the cardinality of the date field is quite high, we use the calendar intervals to round the date as per the calendar interval.
The defaults are
half_hour
andminute
.Since we round off the original timestamp with the specified calendar intervals , there will be results from star tree which are different from original query.
Describe the solution you'd like
Related component
Search:Aggregations
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: