kz930 opened a new pull request, #9054: URL: https://github.com/apache/texera/pull/9054
### What changes were proposed in this PR? Every external output port of an operator that keeps its result is stored, but result pages were always read from the first port, so a Split's second output or an If's True branch could not be shown. A pagination request can now name the output port to read, with the first port as the default, so current requests are unchanged. The reply carries the port it read and that port's total row count, since the live result updates follow only the first port and a client paging another port needs the count from the reply. The frontend's reply type declares the two new fields; nothing in the frontend reads them yet. ### Any related issues, documentation, discussions? Closes #9053. Part of #9052. ### How was this PR tested? A new case in `ExecutionResultServiceSpec` stores different rows on an operator's two ports and checks that a request for each port returns that port's rows and row count, and that a request without a port reads the first. `PaginatedResultEventSpec` checks that the reply echoes the port and carries the count, and that it serializes to exactly the fields the frontend declares. The other websocket and result specs pass, and so do the frontend specs whose hand-built replies gained the two fields. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
