ok. Based on what I see it seems that there is no problem. If you see your earlier screenshot all the segments are for the same time period. Hence the all granularity is being respected. Having said that, why is segment granularity ‘all’ so critical?. Segment granularity has an impact only on query performance not on results. Using ‘all’ discards the performance advantage you gain by partitioning by time
Segment Granularity ALL is required to solve the distinct count issue mentioned below
We need to show a unique exact count in our application and for now, I cannot move on to SQL query because that is required a lot of effort on the application side and our entire application is running on native queries. So for now easiest solution is to have a single segment and in that case, the distinctCount aggregator will work fine. I have already verified the performance by having 15M records in a single segment and in my case, we will not have that many records for now.