GitHub user zyratlo added a comment to the discussion: A control-variable port on every operator: design and prototype
I like this. Having one optional port on every operator is a lot cleaner than adding a "from input" version of each operator that needs a run-time value, and the folder example makes the use case easy to see. Since the port is optional, existing workflows and anyone who doesn't need control variables won't notice a difference. One suggestion I have is about the limit where only the first tuple reaching the port is converted and the rest are dropped. If someone accidentally connects a multi-row table, they'd silently get results from the first row. Could we show a warning when more than one tuple arrives on the port? GitHub link: https://github.com/apache/texera/discussions/8915#discussioncomment-19082665 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
