danielnadean opened a new pull request, #11589: URL: https://github.com/apache/seatunnel/pull/11589
## What changed This PR adds a bilingual Sink write mode guide under connector common options and links it from the general FAQ, connector FAQ, sink common options, and sidebar navigation. The new guide explains: - when to use JDBC `generate_sink_sql` vs `query` - how `schema_save_mode`, `data_save_mode`, and `custom_sql` relate to row writing - when `primary_keys` and `enable_upsert` affect JDBC upsert behavior - how Doris save modes differ from JDBC generated SQL - which file/object-storage sinks expose save mode options, including the current ObsFile/CosFile boundary ## Why Users frequently ask whether `generate_sink_sql`, `schema_save_mode`, `data_save_mode`, `custom_sql`, and `enable_upsert` should be combined, and whether file/object-storage sinks support the same save mode options as JDBC-style sinks. The previous documentation explained parts of this across individual connector pages, but did not provide a cross-sink decision guide. ## Validation - Checked the current source-backed option boundaries for JDBC, Doris, File, ObsFile, and CosFile sinks. - Verified Markdown relative links with a local script. - Ran `git diff --check`. - Ran `./mvnw spotless:check -DskipTests -DskipUT -DskipIT`. No compile, unit, integration, E2E, Docker, or runtime validation was run because this is a docs-only change. -- 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]
