Hi, was wondering if changing the config : `realti...
# getting-started
s
Hi, was wondering if changing the config :
realtime.segment.flush.threshold.rows
from 100000 to 10000 and then refreshing segments would also refresh the already committed segments i.e. segments would have 10000 entries now? Please let me know
m
No I don’t think so - it’ll only apply to segments going forwars
👍 1
s
Yes, tested it
m
if you want the new config to kick in immediately you can call
forceCommit
on the table to have it commit the consuming segment
s
No, I specifically wanted it for already committed segments.
m
I’m wondering whether we could chop up the existing segments using the merge rollup task - https://docs.pinot.apache.org/operators/operating-pinot/minion-merge-rollup-task
I need to give it a try
x
Existing segments won’t be repartitioned. Any reason you want this?
s
No, had an issue with order of events hence was looking for a workaround. Issue is resolved so not needed anymore.
👍 2