kevinjqliu opened a new issue, #14632: URL: https://github.com/apache/iceberg/issues/14632
### Apache Iceberg version main (development) ### Query engine None ### Please describe the bug 🐞 Thanks to #14480 and a lot of other great efforts, I was able to try out the scan planning apis that is now in the `iceberg-rest-fixture`. I provided LLM with the scan planning openapi spec so that I can quickly generate a rest client to interact with the apis and found this discrepancy. #### Description The OpenAPI specification indicates that the response field for planning status should be `status`, but the server implementation currently returns `plan-status` instead. `status` * https://github.com/apache/iceberg/blob/bec6793af822cb791fa5975b41b8936631556c46/open-api/rest-catalog-open-api.yaml#L3370-L3381 `plan-status` * https://github.com/apache/iceberg/blob/bec6793af822cb791fa5975b41b8936631556c46/core/src/main/java/org/apache/iceberg/rest/responses/PlanTableScanResponseParser.java#L36 * https://github.com/apache/iceberg/blob/bec6793af822cb791fa5975b41b8936631556c46/core/src/main/java/org/apache/iceberg/rest/responses/FetchPlanningResultResponseParser.java#L36 #### Suggested Fix 1. **Update the implementation** to align with the OpenAPI spec by returning `status` instead of `plan-status`. 2. **Update the OpenAPI spec** to align with implementation and use `plan-status` instead of `status` ### Willingness to contribute - [x] I can contribute a fix for this bug independently - [x] I would be willing to contribute a fix for this bug with guidance from the Iceberg community - [ ] I cannot contribute a fix for this bug at this time -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
