Jackie-Jiang commented on PR #15515: URL: https://github.com/apache/pinot/pull/15515#issuecomment-2802798359
> The current design document mentions MIN( offline table timestamp ...) as time boundary strategy. Is your suggestion to have field in the logical table config to specify the time boundary strategy? This could allow user to choose a approach among multiple available. Yes. This is critical for use cases where user adds new OFFLINE tables once the previous table grows too large. We need to turn off time boundary handling for old tables and only keep it for the latest one -- 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 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
