Matching Catalog Properties with Java

Aperta
  • Qualcosa non va?
#4,140 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Ankitraj-builds ci sta già lavorando.

Dal 26/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)
Lingua principale
Python
Stelle
1.2k
Fork
654
Merge medio
2g 11h
PR unite (30g)
122

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/iceberg-python

Tutte le issue di apache/iceberg-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.