rozza commented on PR #3: URL: https://github.com/apache/flink-connector-mongodb/pull/3#issuecomment-1432780477
Hi @Jiabao-Sun, As indexes are mutable relying on the natural sort order of them is not going to guarantee the same order of data - so sorting is required, it may end up being very cheap with the hint anyway. Mutability is the heart of the issue - is the data static between the bounds of min and max for the duration of the processes? If not then you cannot guarantee that all data is covered and the offset would not be enough for a comparison, it may miss data if new data was added. So for exactly-once semantics it requires the data to be static and no changes of data between the bounds for the duration of the processes. I hope that helps, Ross -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
