Jackie-Jiang opened a new pull request #4374: Enhance the time boundary service for backward-compatibility URL: https://github.com/apache/incubator-pinot/pull/4374 Handle the time boundary with the following logic: Case 1 - segment has the same start and end time: Directly use the end time as the time boundary for backward-compatibility. There are use cases with time unit other than DAYS, but have time value rounded to the start of the day for offline table (offline segments have the same start and end time), and un-rounded time value for real-time table. In order to get the correct result, must attach filter 'time < endTime' to the offline side and filter 'time >= endTime' to the real-time side. Case 2 - segment has different start and end time: Rewind the end time with the push interval and use it as the time boundary to get consistent result during the push of multiple offline segments. If directly use the end time as the time boundary, then the first pushed offline segment will push forward the time boundary, while the remaining offline segments are not arrived yet, which will cause inconsistent result.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
