joeyutong commented on issue #723: URL: https://github.com/apache/flink-agents/issues/723#issuecomment-4622894829
@weiqingy Sorry for the late reply, and thanks for the detailed follow-up. I agree with the proposed fix for the built-in tool context path. The framework-owned payloads should be normalized in code, including UUIDs used as dict keys/values and output_schema, so they are safe to checkpoint and restore. For Python memory values, I think we should update the docs to clarify two things: which Python-side value shapes are compatible, and that this contract is not fully aligned with the Java-side one because Python values need to be materialized across the Pemja boundary first. I also think adding a Python-side validator with a clear error message is reasonable. It is a behavior change, but at this early stage of the project, I think failing early is better than letting unsupported values reach Flink state and fail during restore. -- 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]
