mengw15 opened a new pull request, #9049: URL: https://github.com/apache/texera/pull/9049
### What changes were proposed in this PR? Records two facts per result port in `operator_port_executions`, so a finished execution's results can be listed without the computing unit (#5363): - `output_mode` (new `output_mode_enum`): whether the port's result is a paginated table or a visualization. Today only the engine's physical plan knows this, and it lives in the CU. The engine already looks up the output port when it creates the port's storage, so `OperatorPortResultUriAvailable` now carries the port's declared mode, and the row is inserted with it. - `result_count`: the number of rows, written where `result_size` is written today, from the count the result store already tracks — no extra table reads. Visualization (`SINGLE_SNAPSHOT`) ports skip that path and keep a null count; they are never paged. Schema change: `sql/updates/52.sql` (idempotent), `texera_ddl.sql`, and a `changelog.xml` entry. Existing rows keep both columns null. Nothing reads the columns yet; that is #8995. ### Any related issues, documentation, discussions? Closes #8994. Part of #5363, proposed in #8945. ### How was this PR tested? - `ExecutionResultServiceSpec`: the mode carried by the event is persisted; every output mode maps to its stored form and an unrecognized one to null; the result store's count is recorded for a table port, and no count for a `SINGLE_SNAPSHOT` port. - `WorkflowExecutionsResourceSpec`: `updateResultCount` sets the column on the matching row. - Removed the mode and count writes and confirmed exactly the two corresponding tests fail. - Applied `52.sql` twice to a local database (the second run is a no-op), and ran the full `texera_ddl.sql` into a scratch database. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-5-5) -- 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]
