anthonychengit opened a new pull request, #7996: URL: https://github.com/apache/texera/pull/7996
### What changes were proposed in this PR? Make <code>CheckpointState</code> implement <code>Serializable</code>, so the existing Kryo binding can persist worker checkpoints. Before: finalize checkpoint → serialize <code>CheckpointState</code> → no matching binding → <code>NotSerializableException</code> After: finalize checkpoint → Kryo binding → flush/close → restore the original checkpoint payload The regression test uses a real worker write path, stores a non-empty Unicode payload, reads the record back from sequential storage, and asserts the returned size and restored value. Two existing write-branch tests now await successful completion instead of discarding failures. ### Any related issues, documentation, discussions? Closes #7907 ### How was this PR tested? Added positive persistence/round-trip coverage while retaining the existing estimate-only and checkpoint-isolation cases. ~~~powershell $env:STORAGE_JDBC_URL='jdbc:postgresql://localhost:15432/texera_codex_jooq?currentSchema=texera_db,public' $env:STORAGE_JDBC_USERNAME='postgres' $env:STORAGE_JDBC_PASSWORD='' sbt "WorkflowExecutionService/testOnly org.apache.texera.amber.engine.architecture.worker.promisehandlers.FinalizeCheckpointHandlerSpec" sbt "scalafixAll --check" "scalafmtCheckAll" ~~~ Result: 6 tests passed; Scalafix and Scalafmt checks passed. The focused suite used an isolated embedded PostgreSQL database and port. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: OpenAI Codex (GPT-5) -- 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]
