wipheg opened a new pull request, #11401:
URL: https://github.com/apache/seatunnel/pull/11401

   ### Purpose of this pull request
   
   Closes #11042.
   
   This PR exposes structured CDC source identifiers as stable metadata fields.
   
   It adds `Schema`, `Collection`, and `Namespace` metadata keys and wires them 
into the existing CDC metadata projection path.
   
   Connector coverage:
   
   - MySQL-CDC / TiDB-CDC: `Database`, `Table`
   - PostgreSQL-CDC / Opengauss-CDC / Oracle-CDC / SQLServer-CDC: `Database`, 
`Schema`, `Table`
   - MongoDB-CDC: `Database`, `Collection`, `Namespace`
   
   Missing identifiers remain absent instead of being filled with placeholders 
or duplicated values.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes.
   
   CDC users can now project structured source identifiers through the 
`Metadata` transform.
   
   Relational CDC example:
   
   ```hocon
   metadata_fields {
     Database = source_database
     Schema = source_schema
     Table = source_table
   }
   ```
   
   MongoDB-CDC example:
   
   ```hocon
   metadata_fields {
     Database = source_database
     Collection = source_collection
     Namespace = source_namespace
   }
   ```
   
   The metadata contract and connector coverage matrix are documented in both 
English and Chinese docs.
   
   ### How was this patch tested?
   
   Added focused tests:
   
   - `MetadataTransformTest`
   - `SeaTunnelRowDebeziumDeserializeSchemaTest`
   - `MongoDBConnectorDeserializationSchemaTest`
   
   Ran:
   
   ```bash
   ./mvnw spotless:apply
   ```
   
   ```bash
   ./mvnw -pl 
seatunnel-transforms-v2,seatunnel-connectors-v2/connector-cdc/connector-cdc-base,seatunnel-connectors-v2/connector-cdc/connector-cdc-mongodb
 
"-Dtest=MetadataTransformTest,SeaTunnelRowDebeziumDeserializeSchemaTest,MongoDBConnectorDeserializationSchemaTest"
 "-DskipIT" "-DskipE2E" "-DfailIfNoTests=false" 
"-Dsurefire.failIfNoSpecifiedTests=false" test
   ```
   
   Full `./mvnw -q -DskipTests verify` was attempted locally, but it failed in 
unrelated existing E2E/JDBC modules.
   
   ### Check list
   
   * [ ] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
   * [x] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [ ] If necessary, please update `incompatible-changes.md` to describe the 
incompatibility caused by this PR.
   * [ ] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)


-- 
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]

Reply via email to