CLI flag for REST catalog's {prefix}

Feature Request / Improvement

IIUC the pyiceberg CLI only supports configuration of a REST catalog's {prefix} path parameter via configuration file or environment variable PYICEBERG_CATALOG__DEFAULT__PREFIX. It would be great to have a flag for that (similar to --uri).

I could probably contribute this myself.

sounds like a great idea! thanks!

feat(cli): add --prefix option for REST catalog (apache#3059)

Add `--prefix` option for REST catalog (apache#3061)

Taking another look at this, i think we might want to change this to --warehouse. The REST spec handshake expects a warehouse parameter for v1/config, https://github.com/apache/iceberg/blob/d06e6c22fecf00be81f2eb399f090fae320560a4/open-api/rest-catalog-open-api.yaml#L64-L78

iceberg-python/pyiceberg/catalog/rest/__init__.py

Lines 617 to 620 in ec0a451

    
           def _fetch_config(self) -> None: 
        
               params = {} 
        
               if warehouse_location := self.properties.get(WAREHOUSE_LOCATION): 
        
                   params[WAREHOUSE_LOCATION] = warehouse_location

for which the server then customize the prefix

@DerGut

cc @DerGut @mrutunjay-kinagi @Fokko

@kevinjqliu

cc @DerGut @mrutunjay-kinagi @Fokko

@kevinjqliu Does this need a PR ?

I just started to wonder the same thing, but I'm still a bit torn:
Doesn't the config response from the server still use the "prefix" configuration key to tell the client which {prefix} to use (via default or overrides)?

EDIT: from that point of view, we may need to distinguish between two configurations

prefix which is used to build the endpoints, but can be overridden from a catalog's /v1/config response
warehouse which can be used to influence the catalog's /v1/config response

Yea it is confusing. I realized this when looking at my .pyiceberg.yaml config file. We allow warehouse param to be configurable for IRC https://py.iceberg.apache.org/configuration/#rest-catalog

The flow / "handshake" is:

client (pyiceberg) calls IRC's /v1/config endpoint with warehouse parameter
IRC returns the prefix in the /v1/config response
client uses the prefix for all subsequent requests to IRC

The main point here is that the client (pyiceberg) doesn't specify prefix directly, the server to configures the prefix for the client.

We technically could let the client (pyiceberg) to override prefix but doing so might be error prone

Ah, I misunderstood the PR. I agree that passing in the prefix is less valuable. Often the prefix is used to distinguish between different workspaces/organisations, but not sure if that's valuable for users to pass in by hand.

i also got confused until i saw the warehouse param in my .pyiceberg.yaml file 😄

I think warehouse makes more sense, but not in a REST context. In Hive/Hadoop this actually points to the location where the data lives. Yay for re-using parameter names :D

@DerGut

Opened #3080 to replace prefix with warehouse.

@DerGut double checking that this still works for your use case

Navigation Menu

Repository navigation

CLI flag for REST catalog's `{prefix}` #3059

Feature Request / Improvement

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	def _fetch_config(self) -> None:
	params = {}
	if warehouse_location := self.properties.get(WAREHOUSE_LOCATION):
	params[WAREHOUSE_LOCATION] = warehouse_location

CLI flag for REST catalog's {prefix} #3059

Description

Feature Request / Improvement

Activity

kevinjqliu commented on Feb 17, 2026

kevinjqliu commented on Feb 18, 2026

kevinjqliu commented on Feb 18, 2026

mrutunjay-kinagi commented on Feb 18, 2026

DerGut commented on Feb 18, 2026

kevinjqliu commented on Feb 18, 2026

Fokko commented on Feb 18, 2026

kevinjqliu commented on Feb 18, 2026

Fokko commented on Feb 18, 2026

kevinjqliu commented on Feb 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

CLI flag for REST catalog's `{prefix}` #3059