stackabletech / stackabletech/trino-operator
Add Iceberg REST catalog support to TrinoCatalog
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
Part of https://github.com/stackabletech/internal-issues/issues/156
Currently we only offer Hive metastore, we also want to offer an Iceberg REST catalog.
A working example can be found here
Implementation note: We want an enum of either metastore or restCatalog. https://github.com/stackabletech/trino-operator/pull/841 made the TrinoCatalog.spec.connector.iceberg.metastore field optional, so changing this to an enum is technically a breaking change, but given 1.) It was only recently made optional and 2.) setups without an metastore can currently not work it's IMHO safe to assume that we can make this breaking change
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the TrinoCatalog.spec.connector.iceberg.metastore field and compare the working configuration in tests/templates/kuttl/iceberg-rest/31_trino.yaml.j2. Trace how the catalog connector is represented and rendered, then update the model and deployment configuration so the enum supports metastore and restCatalog. Done means an Iceberg REST catalog can be configured and the existing metastore path remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- data-engineering, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100