[Docs] Cross-Language Actions#714
Conversation
github-actions
Bot
added
doc-included
|
@xintongsong Today, cross-language is mentioned in a few docs plus the FAQs (Q2/Q3), but there's no concept landing page as such. Worth adding a dedicated |
|
|
||
| ### Cross-language Actions | ||
|
|
||
| An action declared in one language can dispatch its body to the other language by setting a `target` on the decorator/annotation. The decorated function or annotated method then acts as a stub — it should raise so direct calls outside the framework fail loud. |
There was a problem hiding this comment.
The three other cross-language sections — chat models (chat_models.md), embedding models, and vector stores — each carry the same caveat: "Cross-language resources are currently supported only when running in Flink, not in local development mode." The Java-from-Python action path documented here goes through the same Pemja bridge inside ActionExecutionOperator (CrossLanguageActionRuntimeTest exercises it via the Flink operator harness, not local mode). Does that same local-dev limitation apply to cross-language actions? If so, a matching one-line note here would save users a confusing local-mode failure — and there's no general caveat elsewhere in this page that already covers it.
There was a problem hiding this comment.
Thanks for the quick turnaround. The limitations block matches the wording in chat_models.md, embedding_models.md, and vector_stores.md line-for-line — including the run-in-flink ref, which resolves to the ## Run in Flink heading in deployment.md. That covers the local-mode caveat I raised. LGTM.
2 participants
Linked issue: follow-up to #709
Purpose of change
Doc-only follow-up to PR #709 (Cross Language Actions), which shipped without doc updates.
Tests
Docs-only, no tests.
API
No API changes.
Documentation
doc-included