@ancient-wolf-19325 What is special about the event-version in the ArrayNode config

The

event-version

in the ArrayNode config controls how eventing is handled for ArrayNodes. Setting

event-version

to 0 uses the legacy approach (populating

ExternalResourceInfo

in a single event, similar to the old maptask), while setting it to 1 enables a new mode where separate

NodeExecutionEvents

are written for each subNode execution, providing full metadata and improved visibility for subnodes in the UI and admin. This allows for more robust tracking and debugging of individual subnode executions within an ArrayNode, especially when mapping over different Flyte node types or scaling to many subnodes. See the config struct and comments in config.go and the implementation details in PR #4165. Would you like more detail on how this affects event emission or UI behavior? Sources: - config.go - PR #4165 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.