GitHub user bharos added a comment to the discussion: Custom REST APIs in Gravitino
That's a good question. Custom catalogs are more complex than custom REST APIs. For a custom catalog of a new type, you'd need to: 1. Implement the catalog interface (BaseCatalog, CatalogOperations, etc.) 2. Extend the storage layer to persist your catalog's metadata 3. Potentially modify core components for entity management Currently, Gravitino's extension mechanism (gravitino.server.rest.extensionPackages) is designed for adding REST endpoints, not entire catalog implementations. Custom catalogs typically require deeper integration. What specific catalog type are you looking to add? If it's a standard system (e.g., a new database or lake format), I'd recommend opening a feature request so the community can discuss adding native support. If it's highly specialized, you might need to fork or contribute a plugin system enhancement. GitHub link: https://github.com/apache/gravitino/discussions/9940#discussioncomment-15837051 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
