hutiefang76 commented on PR #12498: URL: https://github.com/apache/seatunnel/pull/12498#issuecomment-5872040718
I followed up on the inherited-key limitation in f1592357c. A normal PostgreSQL batch source can carry PK/UNIQUE metadata even when the sink has no configured keys. The new `ducklake_bulk_write_ignore_inherited_keys` option is off by default and only ignores that inherited metadata in the Sink copy. Explicit `primary_keys` and all non-INSERT rows remain rejected; source metadata is preserved. I ran actual PostgreSQL PRIMARY/UNIQUE sources through the Sink into DuckLake and reconnected to verify the rows on JDK 8 and 17. The regression also checks that duplicate keys are appended rather than deduplicated. Both versions passed 51 targeted tests and module verify; the four Markdown checks passed. This adds an explicit append-only choice, so the new head needs another look at that option and its contract. -- 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]
