wenjin272 opened a new issue, #1227: URL: https://github.com/apache/flink-agents/issues/1227
Parent: #1225 ### Problem and scope Language guidance currently conflates the Flink job/submission entry point, Agent definition, and Action/Resource implementation. FAQ and feature pages also contain obsolete local-mode and blanket JDK asynchronous-execution restrictions. #### Scope - [ ] Add `Choose APIs and Languages` under Create an Agent, replacing the isolated `Should I choose Java or Python?` FAQ answer. - [ ] Distinguish three choices: Flink job/submission language (Java/Python), Agent definition (Java/Python/YAML), and component implementation (Java/Python). Explain that submission and dependency provisioning follow the hosting job/entry point, rather than simply the Agent definition language. - [ ] Explain supported combinations and link to their concrete setup paths, without implying every combination is supported. - [ ] Define the cross-language wire contract: supported basic values map across languages; custom objects become nested map/dict representations and require explicit reconstruction when a target-language type is needed. Verify the exact supported types against current implementation. - [ ] Remove obsolete local-mode limitations and blanket claims that JDK 11–20 cannot execute asynchronously. Document genuine feature-specific constraints on the relevant feature pages. - [ ] Apply consistent terminology to Setup, FAQ, Deployment, Chat/Embedding Models, Vector Stores, and cross-language authoring guidance. Present cross-language concepts before Async/Durable. #### Coordination and acceptance Can proceed alongside #1226. Coordinate with Improve Setup and the Quickstart user journey, Improve Agent core concepts, Actions, Events, and execution guides, Clarify YAML reference and Tool Use responsibilities, and Improve consistency, Action State Store, and configuration guidance; they apply this contract in their own workflows. All affected pages must use the same three dimensions and current capability boundaries, with usable links to setup and examples. Closing this issue is not a prerequisite for starting those edits. #### Review coverage DOC-006, DOC-010, DOC-051. These are traceability identifiers; the full actionable scope is described above. -- 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]
