DanielLeens commented on issue #10371: URL: https://github.com/apache/seatunnel/issues/10371#issuecomment-4884354010
Thanks for the follow-up. I checked both the config details in the thread and the current schema-change handling path. This still looks like a real bug rather than only a usage problem. The key point is that Debezium is already failing to parse that `CHANGE COLUMN ... FIRST` DDL cleanly, but SeaTunnel should still not fall through into a `NullPointerException`. In the current path, a `CHANGE COLUMN` event can still reach the schema-change handler without a usable row-type context, and that leads to the crash you reported instead of being ignored or rejected with a clear message. One more detail from the config: the `table-pattern` you shared appears to exclude tables matching `spot_transaction_intra_prov_.*`, so this table may not actually be inside the captured set. That may explain why the upstream schema-change metadata becomes incomplete, but it still does not justify an NPE on the SeaTunnel side. So my current judgment is: 1. this is a genuine bug in the schema-change handling path 2. the regex / table-selection part may be a trigger, but it is not a valid reason for the job to crash 3. the safer behavior here should be to skip or reject this schema-change event cleanly, not fail the task with a null-pointer error For future updates, please use English in the issue thread if possible so more community members can help directly. We've labeled this as `help wanted`. If you have a chance to verify whether the same path still reproduces on the latest `dev` branch, that would still be useful, but the current evidence is already enough to keep this open as an actionable bug. -- 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]
