apache / apache/gravitino

[FEATURE] Support dynamic metalake config for Iceberg REST server

Open
#10,607 0 comments 2 reactions 0 assignees View on GitHub
feature
Dominant language
Java
Stars
3.2k
Forks
935
Avg merge
1d 16h
Merged PRs (30d)
298

Description

### Describe the feature

Iceberg REST server fetch catalog only under one metalake, metalake config is static configured in conf file for now.
REST APIs should support metalake in the request uri path.

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the Iceberg REST server request-routing entry points and the current static metalake configuration. Trace how the metalake is selected for catalog fetches, then verify that request URI paths can provide it and add coverage for the supported REST APIs; done means requests are no longer limited to the configured metalake.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.