GitHub user sshiv012 added a comment to the discussion: Proposal: operators
that emit on more than one output port
Update: how I plan to land multi-port output results
I've rebuilt this on top of #9054 (thanks @kz930) and split it into small PRs,
so each one is easy to review on its own.
Showing results for every output port
1. #9271 feat(amber): keep result metadata per output port (ready for review)
- Backend tracks results per output port instead of per operator.
- Also fixes an HTML port hiding a table port's statistics and size.
- No change to what the frontend receives.
2. #9272 feat: send live result updates of every output port (draft, stacked
on #9271)
- Adds portUpdates to the result update event.
- The frontend result service keeps per-port results.
- No UI change yet.
3. Result panel: one tab per output port (not opened yet)
- Each port with a result gets its own tab, named after the port.
4. Export per output port (not opened yet)
- Export picks the port, and files get a -port<N> suffix.
Python UDF output ports
5. Route a Python UDF's output to the port it names (not opened yet)
- Python only. A UDF can send output to a named port instead of only port
0.
6. Let a UDF output port declare table or visualization (not opened yet)
- Port setting in the property editor. Useful once 3 and 5 are in.
Order: 1 → 2 → 3 / 4, with 5 and 6 running alongside. 1 and 5 don't depend on
anything.
Questions for maintainers:
- #9054 kept live updates on the first port on purpose. #9272 extends them to
all ports, and I'd welcome feedback on that design before it leaves draft.
- PR 3 (tabs per port) may overlap with the pinned windows planned in #9052.
Which direction would you prefer?
Not included: R UDF multi-port output. It needs per-port schemas in RUDFOpDesc
and changes in the separate texera-rudf plugin, sO I'd suggest it as a
follow-up.
FYI @Xiao-zhen-Liu
GitHub link:
https://github.com/apache/texera/discussions/8914#discussioncomment-19407034
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]