This is an automated email from the ASF dual-hosted git repository.
wenjin272 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/flink-agents.git
The following commit(s) were added to refs/heads/main by this push:
new 60bf8cd0a [docs] Add decision model entries to the resource, event,
and cross-language indexes (#1300)
60bf8cd0a is described below
commit 60bf8cd0a69c40970deb342c24690db65744a613
Author: Yi Zhang <[email protected]>
AuthorDate: Wed Oct 21 11:27:50 2026 +0800
[docs] Add decision model entries to the resource, event, and
cross-language indexes (#1300)
Generated-by: Qoder
---
.../development/create-agent/choose-apis-and-languages.md | 1 +
docs/content/docs/development/create-agent/events.md | 1 +
docs/content/docs/development/create-agent/resources.md | 12 ++++++++----
docs/content/docs/development/create-agent/yaml.md | 6 +++++-
4 files changed, 15 insertions(+), 5 deletions(-)
diff --git
a/docs/content/docs/development/create-agent/choose-apis-and-languages.md
b/docs/content/docs/development/create-agent/choose-apis-and-languages.md
index 8257b19ad..4268595bc 100644
--- a/docs/content/docs/development/create-agent/choose-apis-and-languages.md
+++ b/docs/content/docs/development/create-agent/choose-apis-and-languages.md
@@ -56,6 +56,7 @@ Cross-language support is available for the following
component APIs:
| Actions | [Cross-language Actions]({{< ref
"docs/development/create-agent/actions#cross-language-actions" >}}) |
| Function Tools | [YAML cross-language example]({{< ref
"docs/development/create-agent/yaml#cross-language-agents" >}}) and [Tool
Use]({{< ref "docs/development/calling-llms/tool_use" >}}) |
| Chat models, embedding models, and vector stores | [Cross-Language
Resources]({{< ref
"docs/development/create-agent/resources#cross-language-resources" >}}) |
+| Decision models | [Decision Models]({{< ref
"docs/development/decision_models" >}}) and [Cross-Language Resources]({{< ref
"docs/development/create-agent/resources#cross-language-resources" >}}) |
For YAML examples, see
[Cross-language agents]({{< ref
"docs/development/create-agent/yaml#cross-language-agents" >}}).
diff --git a/docs/content/docs/development/create-agent/events.md
b/docs/content/docs/development/create-agent/events.md
index 72ae30b80..0fbd094c3 100644
--- a/docs/content/docs/development/create-agent/events.md
+++ b/docs/content/docs/development/create-agent/events.md
@@ -276,3 +276,4 @@ Event that your Actions can handle to continue the workflow:
| Call a chat model | `ChatRequestEvent`, `ChatResponseEvent` | [Chat with
Models]({{< ref "docs/development/calling-llms/chat#chat-events" >}}) |
| Call tools | `ToolRequestEvent`, `ToolResponseEvent` | [Tool Use]({{< ref
"docs/development/calling-llms/tool_use#built-in-events-and-actions" >}}) |
| Retrieve context | `ContextRetrievalRequestEvent`,
`ContextRetrievalResponseEvent` | [Vector Stores]({{< ref
"docs/development/vector-search/vector_stores#built-in-events-and-actions" >}})
|
+| Call a decision model | `DecisionRequestEvent`, `DecisionResponseEvent` |
[Decision Models]({{< ref "docs/development/decision_models#event-driven-calls"
>}}) |
diff --git a/docs/content/docs/development/create-agent/resources.md
b/docs/content/docs/development/create-agent/resources.md
index c77ffb17f..082c81126 100644
--- a/docs/content/docs/development/create-agent/resources.md
+++ b/docs/content/docs/development/create-agent/resources.md
@@ -38,6 +38,8 @@ the following type names:
|---|---|---|
| `CHAT_MODEL_CONNECTION` | Connect to a chat model service, including
endpoint and authentication settings. | [Chat Models]({{< ref
"docs/development/calling-llms/chat-models" >}}) |
| `CHAT_MODEL` | Configure a chat model setup: connection, model, prompt,
tools, and generation parameters. | [Chat Models]({{< ref
"docs/development/calling-llms/chat-models" >}}) |
+| `DECISION_MODEL_CONNECTION` | Connect to a decision model service. |
[Decision Models]({{< ref "docs/development/decision_models" >}}) |
+| `DECISION_MODEL` | Configure a decision model setup: connection and model. |
[Decision Models]({{< ref "docs/development/decision_models" >}}) |
| `EMBEDDING_MODEL_CONNECTION` | Connect to an embedding model service. |
[Embedding Models]({{< ref "docs/development/vector-search/embedding_models"
>}}) |
| `EMBEDDING_MODEL` | Configure an embedding model setup for converting text
into vectors. | [Embedding Models]({{< ref
"docs/development/vector-search/embedding_models" >}}) |
| `VECTOR_STORE` | Store and retrieve documents using vector search. | [Vector
Stores]({{< ref "docs/development/vector-search/vector_stores" >}}) |
@@ -269,10 +271,12 @@ for these workflows.
## Cross-Language Resources
An Agent can use supported Resource implementations from either Java or Python.
-This applies to chat model connections and setups, embedding model connections
-and setups, and vector stores. Choose an implementation based on the provider
-capabilities you need; the Agent's definition language does not require the
-implementation to use that same language.
+Chat model connections and setups, embedding model connections and setups, and
+vector stores support cross-language use in both directions. Decision model
+connections and setups support cross-language use only from Java to Python:
+Java Agents can use Python implementations, but Python Agents cannot use Java
+implementations. Within these limits, choose an implementation based on the
+provider capabilities you need.
| Calling language | Descriptor for the other language | Implementation class |
|---|---|---|
diff --git a/docs/content/docs/development/create-agent/yaml.md
b/docs/content/docs/development/create-agent/yaml.md
index 80edc5825..8cb084e12 100644
--- a/docs/content/docs/development/create-agent/yaml.md
+++ b/docs/content/docs/development/create-agent/yaml.md
@@ -811,7 +811,11 @@ in a Java Flink job and use each component's `type:` to
select its implementatio
Application payloads must use the supported
[Java and Python data types]({{< ref
"docs/development/create-agent/choose-apis-and-languages#data-passed-between-java-and-python"
>}}).
-Not every resource type is cross-language. Currently `actions`, `tools`,
`chat_model_connections`, `chat_model_setups`, `embedding_model_connections`,
`embedding_model_setups`, and `vector_stores` support `type:` on the opposite
language; others (e.g. `mcp_servers` and external `subagents`) do not.
+Cross-language support varies by component:
+
+- `actions`, `tools`, `chat_model_connections`, `chat_model_setups`,
`embedding_model_connections`, `embedding_model_setups`, and `vector_stores`
support both directions: `type: python` when loaded from Java, and `type: java`
when loaded from Python.
+- `decision_model_connections` and `decision_model_setups` support only
Java-to-Python cross-language use: Java-loaded YAML can use Python
implementations, but Python-loaded YAML cannot use Java implementations.
+- Other components, including `mcp_servers` and external `subagents`, do not
support cross-language use.
## YAML API Specification
