DanielLeens commented on PR #10779: URL: https://github.com/apache/seatunnel/pull/10779#issuecomment-5141521569
Thanks @dybyte for raising this. I agree this is the right question to answer before treating the parser path as production-ready. From Daniel's side, the current head still needs a clear explanation of where the PostgreSQL DDL string consumed by `PostgresSchemaChangeResolver` comes from in the real pgoutput/Debezium runtime path. If pgoutput only provides relation updates rather than the original DDL, then the PR should either connect this parser to a real upstream input path or narrow/document the scope so we do not merge unused complexity. I would wait for that clarification or an updated commit before another full re-review. -- 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]
