Skip to content

feat: Make some REST methods public #922

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

Closed
wants to merge 3 commits into from

Conversation

peasee
Copy link

@peasee peasee commented Jan 29, 2025

  • Makes ErrorResponse, OK, and HttpClient public to support escape-hatching for REST catalogs that don't 100% support the iceberg catalog response formats.

I'd like to use iceberg-rust for some Iceberg-like clients that return partial TableMetadata responses, so I need to be able to access the underlying HTTP client to set my own response types. This enables that use case, and lets me re-use all of the nice work around endpoints, HTTP clients, etc.

@Xuanwo
Copy link
Member

Xuanwo commented Feb 8, 2025

  • Makes ErrorResponse, OK, and HttpClient public to support escape-hatching for REST catalogs that don't 100% support the iceberg catalog response formats.

Hi, I'm a bit concerned about this since it's really an internal implementation detail that we don't want to expose.

I'd like to use iceberg-rust for some Iceberg-like clients that return partial TableMetadata responses

Does it make more sense to allow table metadata to be partially parsed? I'm happy to discuss this direction if you are willing to establish an issue for it.

@peasee
Copy link
Author

peasee commented Feb 11, 2025

Thanks for your response! I ended up taking a different direction that does not use Iceberg, so I'll be closing this PR.

@peasee peasee closed this Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants