Hi, I added some additional columns to star-tree i...
# troubleshooting
p
Hi, I added some additional columns to star-tree index, but I don’t see the new column being part of the start tree index in the new segments doesn’t modifications get reflected in the new segments? IIRC reloads doesn’t help with modifications to the star tree index, correct me if I am wrong
j
Yes, reload cannot modify the existing star-tree, it can only add new star-tree if no one exists yet
p
once the index config is applied, shouldn’t the new segments use the updated index config?
j
Yes, the new segments should be able to pick up the new config
p
hmm, weird I don’t see it happening in the newer segments, let me double check
j
For realtime table, the new config will only be picked up by the next consuming segment
The current consuming segment will still use the old table config
p
I don’t see it in the newer segments too, I enabled this around midnight yesterday. There are a lot of segments that got generated after that, but I don’t see it in any of those
Is there a scenario where a column will be skipped by star-tree?
if the cardinality of the column is more than
max.leaf.records
then the column wouldn’t be included in the index?
j
No, star-tree should not skip any column explicitly configured
What is the old and new star-tree config?
You may search the log for
Starting building star-tree with config: ...
which should print the star-tree configs used
p
let me check that