deemoliu commented on issue #12396: URL: https://github.com/apache/pinot/issues/12396#issuecomment-1944497834
+1 as @Jackie-Jiang mentioned current expected behavior is updating the record location when there is a tie to keep the newer record. However realistically, message orders are not guaranteed coming from Kafka side. another notes on the comparison columns, there are #1 normal cases that comparison value have the possibility to be same accidentally, and #2 there are cases the comparison column value are the same for all messages in purposes (e.g. scenario like filling empty field and avoid missing out of order events). I feel the case #1 cannot be avoided, if it can be solved then the second case can also be solved. meanwhile #2 we should have a proper way to handle it instead of `configure the comparison column value to use a consistent value`. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
