GitHub user sshiv012 added a comment to the discussion: Proposal: operators
that emit on more than one output port
Update on the PR plan, following @Xiao-zhen-Liu's review and the two-phase
approach above.
**Phase 1: multi-port results for native operators (Split, If)**
1. #9271 **feat: keep and send the results of every output port** (ready for
re-review)
- Now includes #9272, which is closed. Following the review, port 0 is no
longer a special case anywhere in the result path:
- `WorkflowResultStore` and `operator_port_executions` size and count are
kept for every external output port.
- `WebResultUpdateEvent` keys both `updates` and `tableStats` by operator
id, then by port index, for every port including 0. The separate `portUpdates`
field is gone.
- `WorkflowResultService` keeps one map per result kind, keyed by operator
and port. Getters default to `portIndex = 0`.
- The pinned window tabs from #9063 now follow each port's live updates and
statistics. The timer that re-read port 1 is removed.
- Rebased onto `main`, with the #9049 conflict resolved. The inline nits are
addressed.
2. **Export per output port** (next, opens after #9271)
- Adds `portIndex` to `ResultExportRequest` and
`ResultExportService.getOperatorDocument`, which hardcodes port 0 today.
- Gives each port's file its own name.
- Turns cell download back on for ports past the first in the pinned window.
Dropped: **result panel tabs per port**. #9063 already adds per-port tabs to
the pinned windows, and #9060 removed the bottom panel's Result tab.
GitHub link:
https://github.com/apache/texera/discussions/8914#discussioncomment-19727987
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]