You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "mengw15 (via GitHub)" <gi...@apache.org> on 2026/10/15 13:21:32 UTC
Re: [I] Workflow results become inaccessible after CU termination — retrieval path is bound to CU lifetime even though storage outlives it [texera]
mengw15 commented on issue #5363:
URL: https://github.com/apache/texera/issues/5363#issuecomment-6193081812
Proposed in #8945, no objections. Tracking the work here in two phases.
**Phase 1 — read finished results without a computing unit**
- #8994 Persist each result port's output mode and row count
- #8995 Add a result-service that reads finished executions' results
- #8996 Read finished results from result-service in the result panel
Runtime statistics and result export move to result-service in follow-ups within this phase.
**Phase 2 — results' lifetime no longer follows the computing unit**
Opened once phase 1 lands: stop deleting results when the last user leaves a workflow, replace the CU-side deletion with a retention policy in result-service, and move user-initiated deletion there.
--
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: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org