GitHub user pltbkd added a comment to the discussion: [Feature] Sub-agent Resource for Flink Agents - Framework part
Sorry for the confusion. I actually meant asAsyncCallable, which was renamed from asDurableCallable. Besides, I realize there might be a third option: - A quick `submit` as 'pub' (still a durable execution): its result is a recipe/handle rather than the actual result, potentially returning a Future. - The `future.isDone()` & `future.get()` or another `query` method works as 'sub': internally, they also perform durable execution, and their results are the running status or the actual result/exception. In this way, the subagent works asynchronously if it supports it, or falls back to either of the previous two models if it cannot (for example, internal subagents). The downside is that a single logical call is split into multiple durable executions, and the number of executions depends on how many times the user calls `query`. Would you prefer this approach, or stick to one of the previous options? GitHub link: https://github.com/apache/flink-agents/discussions/909#discussioncomment-17889713 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
