This message was deleted.
# general
s
This message was deleted.
v
I am not sure what you are talking about, I routinely see super high cardinality string dimensions, with millions and millions of values.
Is your only concern the size of the index in the segment?
if that is truly your concern you can turn off bitmap indexes for specific dimensions (that will have a perf hit on filtering on those dims)
Set create bitmap index to False
numeric dimensions do not have bitmap indexes
m
Thanks for the reassurance here! I'm glad to hear that both strings and numeric dimensions can scale to that degree. I know the bitmap indexes are compressed but I haven't played with how compressed they can be for longer bitmaps. In my case numeric is a more natural representation of this dimension, and I don't think we'll usually filter to just one value, so the filter perf hit won't be too bad.
Is there any interesting interaction with rollup being true / false? not knowing too much about the implementation, with rollup enabled you'd have to partition / shuffle the data by dimension to eventually get to one row for that dimension combination.
c
nested columns and soon, new in druid 26, numeric columns created with ‘auto’ schema do have indexes; they use a cardinality based threshold to decide when to use or not use the indexes in query processing
disclaimer that this stuff is new and somewhat experimental
but based on the measurements will likely apply that strategy to classic string columns at some point in the future
also since those auto numeric columns have bitmap indexes, they are larger than classic numeric columns, in exchange for faster filtering
at some point in the future i’d like to add pure range based numeric indexes as a middle ground for very high cardinality numeric columns instead of a bitmap per value, but haven’t gotten there yet