You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the REST API yaml specification 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), 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.
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
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
The text was updated successfully, but these errors were encountered:
Apache Iceberg version
1.8.0 (latest release)
Query engine
Spark
Please describe the bug 🐞
In the REST API yaml specification 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), it seems to return status code 200 instead of 204. This seems to be the case for the
dropTable
anddropNamespace
variants as well, as well asrenameTable
. There may be others, but I haven't tested them.(As context I am trying to refactor the Rust bindings 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
The text was updated successfully, but these errors were encountered: