mengw15 opened a new issue, #4126:
URL: https://github.com/apache/texera/issues/4126
### Feature Summary
### Background
Currently, computing units are responsible for writing execution results and
execution records directly to PostgreSQL / Iceberg, and execution result files
are stored inside the computing units. This leads to several issues:
- Result persistence logic lives inside the computing units.
- Computing units need direct DB access and JDBC configuration.
To improve isolation, we want to move execution-result handling out of the
computing units into a dedicated microservice.
### Proposed Solution or Design
### Proposal: Execution Result Service
Introduce a new **Execution Result Service** microservice and move
execution-result handling from computing units into this service.
**Responsibilities**
- Manage JDBC connections to PostgreSQL.
- Own JDBC configuration.
- Expose a REST API for:
- Writing workflow execution results.
- Querying / reading execution results.
- Writing execution records.
- Store execution result files outside of computing unit pods (e.g., global
volume).
**High-level data flow**
1. Computing Unit → Execution Result Service (HTTP API calls for result
writes/reads).
2. Execution Result Service → Access Control Service (authorization checks).
3. Execution Result Service → PostgreSQL / Iceberg.
### Impact / Priority
(P2)Medium – useful enhancement
### Affected Area
Storage / Metadata, Workflow Engine (Amber)
--
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]
