flyrain commented on PR #4923: URL: https://github.com/apache/polaris/pull/4923#issuecomment-4962287906
With event-ID UUIDs as Kafka keys, two events for the same table can land in different partitions. And Kafka(https://kafka.apache.org/10/documentation.html) guarantees ordering only within a partition. An update could be processed before the corresponding create or rename. Polaris itself intentionally delivers events FIFO to each listener. I think it fine for certain use cases, but not for others, like table replication. Should we clarify a bit in the doc? For example, only use one partition if consumer requires ordering. -- 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]
