DanielLeens commented on issue #11126: URL: https://github.com/apache/seatunnel/issues/11126#issuecomment-4794941951
Leon's workaround is useful for one narrower case, but it is still not the same as the feature requested here. `enable_upsert=true` handles row conflicts during writing. This issue is asking for something earlier and different: a table-level save mode that can decide "this target table already contains data, so skip this table and continue the rest of the job". That distinction is why this still looks like a valid feature request. For the implementation scope, I would keep the next step focused on these points: 1. define the behavior at table level, not row deduplication level 2. make the behavior explicit for three cases: table does not exist, table exists but is empty, table exists and already has data 3. clarify whether the first implementation is batch-only or supports streaming too 4. make unsupported connectors fail fast instead of pretending they can pre-check target data So I would keep this issue open as a feature request rather than treating the upsert path as a full substitute. -- 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]
