I am wondering if my time dimension is in millisec...
# general
n
I am wondering if my time dimension is in millisecond granularity, how it will be used in star-tree? Should I truncate it to day or week first? P.S. I see that star tree will automatically include dictionary-encoded Time/DateTime columns to the dimensionsSplitOrder property.
m
If you have different millisecond value for each row, then you are preventing pre-aggregation. At this point, you need to ask if the application really needs to slice/dice at millis level? If not, then you can either use a different time unit (say days), or you can snap the millis for the entire day to the beginning of the day or some fixed value.
n
I understand. Because I see this in the doc, I am wondering will the enableDefaultStarTree append millisecond cols to the dimension?
All dictionary-encoded Time/DateTime columns will be appended to the dimensionsSplitOrder following the dimensions, sorted by their cardinality in descending order. Here we assume that time columns will be included in most queries as the range filter column and/or the group by column, so for better performance, we always include them as the last elements in the dimensionsSplitOrder.
m
It will append it to the split order. As in the after splitting data on specified dimension columns, it will be further split by time.