rosemarYuan opened a new pull request, #977:
URL: https://github.com/apache/flink-agents/pull/977

   <!--
   * Thank you very much for contributing to Flink Agents.
   * Please add the relevant components in the PR title. E.g., [api], 
[runtime], [java], [python], [hotfix], etc.
   -->
   
   <!-- Please link the PR to the relevant issue(s). Hotfix doesn't need this. 
-->
   Linked issue: #754 
   
   ### Purpose of change
   
   This is the third PR in the three-PR stack tracked by #754:
   1. #756 — API changes (under review)
   2. #821 — CEL runtime (Java and Python)
   3.  **This PR** —Documentation
   
   PR #821 introduced Action trigger conditions, but the existing documentation 
still described Actions mainly as event-type listeners. This PR documents the 
user-visible trigger-condition contract consistently across Java, Python, and 
YAML.
   
   A trigger condition can be either an exact event type or a condition 
expression, which uses Common Expression Language (CEL). This change:
   
   - explains OR semantics across trigger-condition entries, fan-out across 
matching Actions, exact event-type precedence, and per-Action short-circuit 
behavior;
   - documents the event data available to condition expressions, including 
nested values, name collisions, missing values, numeric conversion, and 
supported macros;
   - explains YAML validation and quoting rules for condition expressions, 
custom event types, and event aliases;
   - clarifies that event aliases replace only complete event-type entries;
   - provides decorated, annotated, and programmatic Action examples, including 
a complete Java registration example;
   - documents `action.trigger-condition.evaluate-failure-strategy`; and
   
   ### Tests
   
   This is a documentation-only change. No Tests.
   
   ### API
   
   No public API or runtime behavior is changed. This PR documents the Action 
trigger-condition APIs and configuration introduced by #821.
   
   
   ### Documentation
   
   <!-- Do not remove this section. Check the proper box only. -->
   
   - [ ] `doc-needed` <!-- Your PR changes impact docs -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [x] `doc-included` <!-- Your PR already contains the necessary 
documentation updates -->


-- 
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]

Reply via email to