Hi, I have a question regarding fields with with l...
# general
v
Hi, I have a question regarding fields with with low cardinality. (fields like transaction_status). Needed to ask if we should be keeping those as integers in pinot and maintain enums on application end. or Can we keep the field values as string in pinot and pinot's forward index already optimizes for low cardinality string fields. Will the lookup and aggregation performance for string values be nearly same as with integer?
k
Pinot will optimize it by creating a dictionary
What kind of aggregation do you plan to perform on enum column
v
These queries: select count(1), status from trips group by status select * from trips where status = 'Early'
j
Yes, the performance should be fairly close (int is slightly faster) if you use dictionary encoding and add inverted index to the column