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

   ### Purpose of this pull request
   
   Fixes #12834 in PostgreSQL CDC connector.
   
   On a type-name cache miss, `TypeRegistry.get(String)` previously queried 
matching names without considering the source connection's `search_path`. When 
schemas contain types with the same name, it could select a type that 
PostgreSQL would not resolve for that connection.
   
   This change prefers the visible type and uses OID order as a deterministic 
fallback when none is visible. Cached-name and direct-OID lookups are 
unchanged. It does not change downstream `ADD COLUMN` type-name handling.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. A late-discovered, unqualified type name shared by multiple schemas now 
resolves to the type visible on the source connection's `search_path`. There is 
no new option or public API change. The behavior is documented in the English 
and Chinese PostgreSQL CDC pages.
   
   ### How was this patch tested?
   
   - Added `PostgresCDCIT#shouldResolveNewTypesUsingPostgresSearchPath`, 
covering both search-path orders, the no-visible-type fallback, and direct OID 
lookup. It passed against PostgreSQL Testcontainers: 1 test, 0 failures.
   - The scoped PostgreSQL CDC connector tests passed: 70 tests.
   - Scoped build, Spotless, and diff checks passed on Java 11.0.19.
   
   Full repository PR CI has not run yet.
   
   ### Check list
   
   - [x] No new JAR binary or dependency.
   - [x] English and Chinese connector documentation updated.
   - [x] No configuration or public API incompatibility requiring an 
`incompatible-changes.md` entry.
   - [x] Existing connector only; no plugin registration or distribution 
change. The existing PostgreSQL CDC E2E test was extended.


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