Jackie-Jiang opened a new issue, #12508: URL: https://github.com/apache/pinot/issues/12508
This is a followup on the discussion in #10137 When `realtime.segment.flush.threshold.rows` is used, the flush threshold for the new CONSUMING segment is determined by both this value and the max partitions consumed by any server. This is not very straight forward, and rebalancing a table could cause new consuming segment size to change. In order to tackle this problem, we may add a new config (proposing `realtime.segment.flush.threshold.segment.rows`) which works independent of partitions consumed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
