jerryshao opened a new issue, #12667: URL: https://github.com/apache/gravitino/issues/12667
### Describe the proposal Follow-up hardening for the job system (`api/.../job`, `core/.../job`, `core/.../storage/relational/service/JobMetaService.java`) covering three independent tracks: 1. **Job output log support** — `JobExecutor` (`core/src/main/java/org/apache/gravitino/connector/job/JobExecutor.java`) currently only exposes `submitJob`/`getJobStatus`/`cancelJob`; there is no way to retrieve a job's stdout/stderr. Add a way for `JobExecutor` implementations (local runner, Airflow, etc.) to surface job output, and expose it through `JobHandle` and the REST/client APIs, following the same pattern used for `queuedAt`/`startedAt`/`finishedAt` (default method throwing `UnsupportedOperationException` for backward compatibility). 2. **Runtime job template on `JobHandle`** — today `JobTemplate` placeholders are resolved before being handed to `JobExecutor#submitJob`, but the resolved (runtime) template isn't returned anywhere; callers only ever see the original template. Expose the actual runtime template that was submitted via `JobHandle`. 3. **DB logic optimizations** — review `JobMetaService`/`JobTemplateMetaService` and their SQL providers for the same class of issues recently fixed in the fileset OCC work (e.g. #12656): unnecessary round trips, soft-delete/cleanup logic (`JobMetaBaseSQLProvider.softDeleteJobMetasByLegacyTimeline`), and any missing optimistic-concurrency protection on job/job-template updates. ### Task list - [ ] Support output log retrieval for job handler (`JobExecutor`, `JobHandle`, REST + Java/Python clients) - [ ] Expose the runtime (placeholder-resolved) job template via `JobHandle` - [ ] Audit and optimize `JobMetaService` / `JobTemplateMetaService` DB access patterns -- 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]
