wenjin272 commented on issue #1121: URL: https://github.com/apache/flink-agents/issues/1121#issuecomment-5691531838
Thanks for taking this on @wenjin272! I think the main challenge is how users should declare cross-language resources after these implementations are moved. This may be slightly beyond the scope currently described in the issue, but I believe it should be addressed together; otherwise, we may still need API-level wrapper classes or implementation-class references solely for resource declaration, leaving the migration incomplete. One possible approach is to add explicit language/runtime metadata, such as `JAVA` or `PYTHON`, to `ResourceDescriptor`. The resource type would still come from the annotation, YAML field, or `addResource` argument, while the descriptor would directly reference the actual implementation class. This could allow us to remove the per-resource cross-language declaration wrappers symmetrically from both Java and Python. This is only a proposal for reference, and the design is still open for discussion. I’ll also discuss it with other community members. -- 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]
