ppawel commented on issue #34608: URL: https://github.com/apache/beam/issues/34608#issuecomment-2979115924
IMO this should rather be fixed in upstream logic of the user pipeline - if you remove duplicates silently then how does the user know what is going to be saved? In our pipelines, this situation appears when we have concurrent modifications of the same entity in short time spans and we had to deal with it by fixing our logic. If DatastoreIO would not raise those exceptions, we would get data corruption issues. -- 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: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
