feat: add Gravitino catalog namespace implementation #205
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Summary - Implements Apache Gravitino integration for Lance namespace management - Adds generic RestClient reuse for Gravitino REST API operations - Creates comprehensive Gravitino namespace documentation - Follows the same pattern as Unity Catalog implementation ## Changes ### New Gravitino Namespace Module (`lance-namespace-gravitino`) - Full implementation of Lance namespace interface for Apache Gravitino - Support for Gravitino's 4-level namespace hierarchy (metalake.catalog.schema.table) - Creates Lance tables with custom properties for identification - Authentication via bearer tokens ### RestClient Reuse (`lance-namespace-core`) - Leverages existing generic HTTP client for REST operations - Connection pooling and retry logic with exponential backoff - Comprehensive error handling for Gravitino API responses ### Documentation - Gravitino namespace specification (`docs/src/impls/gravitino.md`) - Configuration properties and authentication methods - Table definition requirements for Lance tables in Gravitino - Type mapping between Arrow and Gravitino schemas ## Key Features - Tables stored with `format=lance` property for identification - `provider` set to `lance` to specify the data provider - Storage location points to actual Lance table data - Support for schema CRUD operations within configured catalog - Support for table CRUD operations with proper type conversion - Compatible with Gravitino REST API v1 ## Test plan - [x] Unit tests with WireMock for API simulation - [ ] Integration tests with Gravitino deployment - [ ] Manual testing with Gravitino server - [ ] Verify table creation and metadata management 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
…entations - Remove unnecessary README.md from gravitino module - Simplify gravitino.md to be concise like other implementations - Remove gravitino. prefix from configuration properties - Focus only on namespace mapping, table definition, and configuration
- Remove metalake and catalog from configuration properties - Parse metalake.catalog.schema from namespace identifiers - Update all API paths to extract hierarchy levels from namespaces - Fix tests to use full 3-level namespace paths - Update gravitino.md to reflect the namespace mapping correctly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
New Gravitino Namespace Module (
lance-namespace-gravitino)RestClient Reuse (
lance-namespace-core)Documentation
docs/src/impls/gravitino.md)Key Features
format=lanceproperty for identificationproviderset tolanceto specify the data providerImplementation Details
The implementation follows the exact same pattern as the Unity Catalog integration (#201):
Test Plan
Related
🤖 Generated with Claude Code