bobbai00 opened a new pull request, #5298: URL: https://github.com/apache/texera/pull/5298
### What changes were proposed in this PR? The computing unit (which runs user-defined functions) no longer needs direct Postgres access. Execution-metadata operations route to the Dashboard Service (`TexeraWebApplication`) via a new `/api/internal/execution-metadata/*` API (`InternalExecutionMetadataResource`) and an HTTP client (`RemoteExecutionMetadata`); dataset-path resolution routes to file-service's new `GET /api/dataset/resolve` (`RemoteDatasetResolver` + a one-line dispatch in `FileResolver`). Routing engages when `SqlServer` is uninitialized (the CU) and the forwarded user JWT is present; `ComputingUnitMaster` skips `SqlServer.initConnection` and DB cleanup when `EXECUTION_METADATA_REMOTE=true`. No behavior change with the flag off — the Dashboard Service keeps the direct-DB path. Also adds `SqlServer.isInitialized` and the new env-var names. ### Any related issues, documentation, discussions? Part of #5011 ### How was this PR tested? Unit tests for both HTTP clients (`RemoteDatasetResolverSpec`, `RemoteExecutionMetadataSpec`) using in-process HTTP servers — positive, 404→None, and error-status paths. Manually end-to-end: launched the full stack with the CU master in `EXECUTION_METADATA_REMOTE=true` mode (no `STORAGE_JDBC_*`; verified no Hikari/`SqlServer` init) against a Lakekeeper REST catalog; the IMDB example workflows (Movies, Iris) and workflow 2568 ran to completion with every execution-metadata and dataset-resolution call served over HTTP (confirmed in the Dashboard Service / file-service request logs). ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.8 (1M context) -- 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]
