laserninja opened a new issue, #11583:
URL: https://github.com/apache/gravitino/issues/11583
### What would you like to be improved?
Only the scan-plan submit endpoint (`planTableScan`) is implemented. The
async lifecycle defined by the Iceberg REST spec is incomplete: when
`planTableScan` returns a `submitted` status with a plan id, clients have no
way to poll the result via `GET .../plan/{plan-id}` or cancel it via `DELETE
.../plan/{plan-id}`. The sibling `POST .../tasks` endpoint is already tracked
in #11284.
### How should we improve?
Implement `fetchPlanningResult` (`GET
/v1/{prefix}/namespaces/{namespace}/tables/{table}/plan/{plan-id}`) and
`cancelPlanning` (`DELETE .../plan/{plan-id}`), wiring them through the table
operation dispatcher and `IcebergExceptionMapper`. Advertise the corresponding
endpoints in `/v1/config` and add tests.
Related: scan-planning epic #7668 / #7261; sibling endpoint #11284;
spec-compliance epic #10547.
--
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]
