Matching Catalog Properties with Java

未关闭
  • 哪里不对？
#4,140 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Ankitraj-builds 已经在做这个了。

开始于 2026年10月26日。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

The issue lists configuration property differences across catalogs, REST, S3, ADLS, and GCS, but asks whether the community values compatibility before any implementation begins. Start by reading the configuration handling and tests for the listed integrations, then identify which properties should match Java. Done means the scope and expected behavior are agreed for each property; the issue does not identify files or tests.

由索引模型根据 Issue 内容生成。

描述

Feature Request / Improvement

I was doing some analysis of the accepted configuration properties in Python vs. Java. We have a number of them in Python that don't fully match with Java (list below, generated by Claude)

Before we start generating PRs for any of these, does the community find any value in making these properties match Java (where appropriate)?

--

Catalogs
  • DynamoDB: accept dynamodb.table-name (Python reads table-name)
  • Hive: accept iceberg.hive.lock-check-min-wait-ms / iceberg.hive.lock-check-max-wait-ms (Python reads lock-check-min-wait-time / lock-check-max-wait-time in seconds)
  • Hive: accept hive.metastore.table.owner / hive.metastore.database.owner (Python reads the table property owner)
  • SQL: accept jdbc.init-catalog-tables / jdbc.schema-version (Python reads init_catalog_tables / schema_version)
  • Glue / DynamoDB: fall back to client.region and client.* credentials (Python reads glue.* / dynamodb.*)
REST
  • Accept rest.auth.type (none / basic / oauth2 / sigv4 / google) as well as the nested auth.type config (Python uses noop, Java uses none)
  • Accept rest.auth.basic.username / rest.auth.basic.password
  • Accept rest.auth.type=sigv4 as well as rest.sigv4-enabled=true
  • Accept rest.remote-signing.endpoint and s3.remote-signing-enabled (Python reads s3.signer.uri / s3.signer.endpoint / s3.signer)
S3
  • Accept s3.sse.type / s3.sse.key (Python reads s3.server-side-encryption / s3.sse-kms-key-id)
  • Accept client.assume-role.arn / client.assume-role.session-name (Python reads s3.role-arn, client.role-arn, *.role-session-name)
  • Accept s3.path-style-access (inverse of Python's s3.force-virtual-addressing)
  • Accept http-client.proxy-endpoint (Python reads s3.proxy-uri)
  • Accept http-client.*.connection-timeout-ms (Python reads s3.connect-timeout in seconds)
ADLS / GCS
  • ADLS: accept adls.auth.shared-key.account.name / adls.auth.shared-key.account.key (Python reads adls.account-name / adls.account-key)
  • ADLS: accept adls.connection-string.<account> per account (Python reads only a single adls.connection-string)
  • GCS: accept gcs.user-project (closest Python equivalent: gcs.requester-pays)
主要语言
Python
星标
1.2k
派生
654
平均合并
2 天 11 小时
30 天内合并 PR
122

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apache/iceberg-python 的其他 Issue

查看 apache/iceberg-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。