kz930 opened a new issue, #8325: URL: https://github.com/apache/texera/issues/8325
### Feature Summary A workflow can be built and read in the editor, but there is no form of it that runs anywhere else. A user who wants to keep a pipeline after the fact, hand it to a colleague who does not run Texera, or step through it in a notebook has nothing to take away. What is missing is an export: given a plan, produce a single Python file that reads the same sources, applies the same operators in the same order, and prints its results. The operators already describe their work as Python for the engine, so the pieces exist; what is absent is a form of that description that stands on its own, without the runtime around it, and something to stitch the pieces into one script. ### Proposed Solution or Design An operator says how it reads outside the engine by implementing a `StandaloneCodeGenerator` trait, returning a block of pandas that names its inputs and outputs by position: `in1df`, `in2df`, `out1df`. A translator walks the plan in topological order, gives every output port a variable, substitutes those placeholders for the variables its upstreams were given, and prints the leaves. A variadic port, of which Union is the one example, needs the whole list of upstreams rather than a fixed count, since any count the operator states would be wrong for some workflow. The compiling service exposes the result as an endpoint, so the editor can offer the script for a plan the user has open. An operator that has no generator yet leaves a commented placeholder in the script rather than a line that looks like it works, so the export is useful before every operator implements it. ### Affected Area Workflow Engine (Amber), Workflow UI -- 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]
