Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST API responses with Spark return status code 200 instead of 204 #12283

Open
1 of 3 tasks
connortsui20 opened this issue Feb 16, 2025 · 0 comments
Open
1 of 3 tasks
Labels
bug Something isn't working

Comments

@connortsui20
Copy link

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 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 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
  • 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
@connortsui20 connortsui20 added the bug Something isn't working label Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant