Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

s3 enpoint url in table.io.properties is different than that of catalog.properties

Open
#3,163 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data-engineering

Research direction

Start with the catalog and table IO property handling used by load_catalog and load_table, then reproduce the mismatch with the provided minimal example and pyiceberg.yaml configuration. Done means table.io.properties["s3.endpoint"] preserves the configured http://192.168.0.72:9008 value and matches catalog.properties["s3.endpoint"].

Written by the indexing model from the issue text.

Description

stale
Apache Iceberg version

0.11.0 (latest release)

Please describe the bug 🐞

I am using polaris as rest catalog and RustFS as S3 client. My problem is that the s3 endpoint that i set in the pyiceberg.yaml file is not being used by the table.io (although catalog has it correctly)

The url is changed from http://192.168.0.72:9008 to localhost:9008 for the table.io.properties.get("s3.endpoint") property.

Here is a minimal example for it:

catalog = load_catalog("default", **catalog_conf)
catalog.create_namespace("Dummy")
schema = pa.schema([
    pa.field("a", pa.int32()),
    pa.field("b", pa.int32()),
    ])
catalog.create_table("Dummy.new_table", schema)
table = catalog.load_table("Dummy.new_table")
table.io.properties["s3.endpoint"] == catalog.properties["s3.endpoint"]
Willingness to contribute
  • I can contribute a fix for this bug independently
  • I would be willing to contribute a fix for this bug with guidance from the Iceberg community
  • I cannot contribute a fix for this bug at this time
Dominant language
Python
Stars
1.1k
Forks
589
Avg merge
2d 4h
Merged PRs (30d)
72

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/iceberg-python

All issues in apache/iceberg-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.