connortsui20 opened a new issue, #12283: URL: https://github.com/apache/iceberg/issues/12283
### Apache Iceberg version 1.8.0 (latest release) ### Query engine Spark ### Please describe the bug 🐞 In the [REST API yaml specification](https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml) for Iceberg catalog, it states that the status code for checking if a table or namespace exists. However, when I run the spark implementation (detailed on this [quickstart guide](https://iceberg.apache.org/spark-quickstart/)), it seems to return status code **200** instead of 204. This seems to be the case for the `dropTable` and `dropNamespace` variants as well, as well as `renameTable`. There may be others, but I haven't tested them. (As context I am trying to [refactor the Rust bindings](https://github.com/apache/iceberg-rust/pull/965) for the REST catalog API) Is this intentional? My main question is what is the behavior supposed to be? It is always the case that both status code 200 and 204 should be considered success cases for every API call? If that is the case then I feel that should be documented in the `rest-catalog-open-api.yaml` file I linked above... ### Willingness to contribute - [ ] 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: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
