liusy-bd commented on issue #10417: URL: https://github.com/apache/seatunnel/issues/10417#issuecomment-3817715594
非常感谢！seatunnel 版本为 2.3.12，此问题是测试 savepoint 后 恢复 出现的问题，测试前写入pamion 已经有一段时间了 pamion 表是存在的 ---- Replied Message ---- | From | Daniel ***@***.***> | | Date | 01/29/2026 21:18 | | To | apache/seatunnel ***@***.***> | | Cc | skylark-lsy ***@***.***>, Author ***@***.***> | | Subject | Re: [apache/seatunnel] [Bug][Connector-v2] [Oracle-CDC] [Paimon][checkpoint] CheckpointCoordinator inside have error. (Issue #10417) | DanielCarter-stack left a comment (apache/seatunnel#10417) Based on the stack trace at line 138 and code analysis, the NPE is caused by paimonCatalog being null when the PaimonSinkWriter constructor is called during checkpoint recovery. The root cause is in the PaimonSink constructor (lines 100-126): when the database or table does not exist, the constructor returns early (lines 105 and 110), leaving the paimonTable field as null. During checkpoint recovery, the restoreWriter method (lines 154-167) then uses this null paimonTable to create a PaimonSinkWriter, triggering the NPE. This appears to be fixed in later commits on the dev branch (e.g., 085023a), which adds null checks and proper error handling for missing tables. To verify: Could you provide your SeaTunnel version and confirm whether the Paimon table exists when the job starts? If this is a known issue, upgrading to the latest version or applying the fix from the dev branch should resolve it. Relevant files: seatunnel-connectors-v2/connector-paimon/src/main/java/org/apache/seatunnel/connectors/seatunnel/paimon/sink/PaimonSink.java seatunnel-connectors-v2/connector-paimon/src/main/java/org/apache/seatunnel/connectors/seatunnel/paimon/sink/PaimonSinkWriter.java — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> -- 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]
