[jira] [Updated] (FLINK-39383) [Docs] Improve scan.incremental.snapshot.chunk.key-column documentation for MySQL/PostgreSQL/Oracle/DB2/SQLServer connectors

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-39383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-39383:
-----------------------------------
    Labels: pull-request-available  (was: )

> [Docs] Improve scan.incremental.snapshot.chunk.key-column documentation for MySQL/PostgreSQL/Oracle/DB2/SQLServer connectors
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-39383
>                 URL: https://issues.apache.org/jira/browse/FLINK-39383
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: ericzeng
>            Priority: Minor
>              Labels: pull-request-available
>
> The `{*}scan.incremental.snapshot.chunk.key-column{*}` option had several gaps
>   and inaccuracies in its documentation across multiple connectors:
> 1. NOT NULL / no-primary-key constraint was undocumented.
> The option is required when a captured table has no primary key and the chosen column must be NOT NULL. None of the connector docs mentioned this.
> 2. Multi-table format was undocumented (MySQL).
> The MySQL connector supports `<table-pattern>:<column>[;...]` for assigning different chunk key columns to different tables. This was not documented in either the flink-source or pipeline connector docs.
> 3. Option was entirely missing from PostgreSQL pipeline connector docs. 
> 4. Stale option description wording across all connectors.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)