DanielLeens commented on issue #10777: URL: https://github.com/apache/seatunnel/issues/10777#issuecomment-5137972222
Thanks for the interest. This is still a useful PostgreSQL CDC feature gap to work on, and the safest first slice is the same narrow scope described earlier: 1. add a PostgreSQL-specific schema change resolver; 2. wire it into `PostgresIncrementalSource` so PostgreSQL DDL can enter the existing SeaTunnel schema-evolution path; 3. keep the first PR limited to a small supported set such as add / drop / rename / modify column; 4. add focused parser / resolver tests and document unsupported PostgreSQL DDL clearly. If you want to take it, please open a scoped PR against `dev` and link it here, or comment with the exact first-phase scope you plan to implement. That will make it easier for reviewers to keep this aligned with the existing MySQL / Oracle CDC schema-evolution model. -- 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]
