bobbai00 opened a new pull request, #6314:
URL: https://github.com/apache/texera/pull/6314

   ### What changes were proposed in this PR?
   
   This is PR 1 of the split from #6009. It migrates the sync-execution backend 
and agent-service internals to the new execution summary contract while keeping 
the current frontend response shape compatible.
   
   Core changes:
   - Replace the sync-execution result model with `WorkflowExecutionSummary`, 
`OperatorExecutionSummary`, and `OperatorResultSummary`.
   - Represent sampled rows as `[rowIndex, Tuple]` pairs instead of embedding 
row metadata into JSON result records.
   - Reuse the shared `WorkflowFatalError` shape for execution and 
compilation-style failures.
   - Update agent-service execution formatting, result cache, server paths, and 
tests to consume the new model.
   - Keep `GET /agents/:id/operator-results` legacy-compatible through a 
temporary adapter, so the existing frontend continues to work until the 
follow-up frontend PR lands.
   
   Main review files:
   - 
`amber/src/main/scala/org/apache/texera/web/resource/SyncExecutionResource.scala`
   - `agent-service/src/types/execution.ts`
   - `agent-service/src/server.ts`
   
   ### Any related issues, documentation, discussions?
   
   Part of #5750.
   Part of #5747.
   Split from #6009.
   
   A follow-up PR will migrate the frontend to consume the new summary shape 
directly and remove the temporary compatibility adapter.
   
   ### How was this PR tested?
   
   - `cd agent-service && bun test src/server.spec.ts 
src/agent/tools/result-formatting.spec.ts src/agent/tools/tools-utility.spec.ts 
src/agent/tools/workflow-execution-tools.spec.ts 
src/agent/workflow-result-state.spec.ts`
   - `cd agent-service && bun run format:check`
   - `cd agent-service && bun run typecheck`
   - `sbt scalafmtCheckAll`
   
   Attempted but did not complete locally:
   
   - `sbt "WorkflowExecutionService / testOnly 
org.apache.texera.web.resource.SyncExecutionResourceSpec"`
   
   The command failed before reaching the spec because local JOOQ generation 
could not authenticate to Postgres, then existing generated Java deprecation 
warnings hit `-Werror` during `DAO / Compile`.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Codex
   


-- 
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]

Reply via email to