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

Express REST server capabilities #10462

Open
1 of 6 tasks
nastra opened this issue Jun 8, 2024 · 0 comments
Open
1 of 6 tasks

Express REST server capabilities #10462

nastra opened this issue Jun 8, 2024 · 0 comments
Labels
OPENAPI proposal Iceberg Improvement Proposal (spec/major changes/etc)

Comments

@nastra
Copy link
Contributor

nastra commented Jun 8, 2024

Proposed Change

When introducing Views to the REST catalog it was clear that we need a way in the REST spec to signal which endpoints are being supported by a REST server. The idea of the proposal is to introduce and express server capabilities via the /config endpoint, so that clients know that it is safe to call a particular endpoint on a given REST server.

Capabilities that currently come to mind are:

  • views
  • vended-credentials
  • remote-signing
  • multi-table-commit

#9940 adds the required REST spec changes to introduce capabilities.

Proposal document

https://docs.google.com/document/d/1F1xh6SJhS-opgWRe1pPvWh01j8VHNHRocfCCFttKNf0/edit?usp=sharing

Specifications

  • Table
  • View
  • REST
  • Puffin
  • Encryption
  • Other
@nastra nastra added the proposal Iceberg Improvement Proposal (spec/major changes/etc) label Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OPENAPI proposal Iceberg Improvement Proposal (spec/major changes/etc)
Projects
None yet
Development

No branches or pull requests

2 participants