Repository navigation
Open
Description
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 readstable-name) - Hive: accept
iceberg.hive.lock-check-min-wait-ms/iceberg.hive.lock-check-max-wait-ms(Python readslock-check-min-wait-time/lock-check-max-wait-timein seconds) - Hive: accept
hive.metastore.table.owner/hive.metastore.database.owner(Python reads the table propertyowner) - SQL: accept
jdbc.init-catalog-tables/jdbc.schema-version(Python readsinit_catalog_tables/schema_version) - Glue / DynamoDB: fall back to
client.regionandclient.*credentials (Python readsglue.*/dynamodb.*)
REST
- Accept
rest.auth.type(none/basic/oauth2/sigv4/google) as well as the nestedauth.typeconfig (Python usesnoop, Java usesnone) - Accept
rest.auth.basic.username/rest.auth.basic.password - Accept
rest.auth.type=sigv4as well asrest.sigv4-enabled=true - Accept
rest.remote-signing.endpointands3.remote-signing-enabled(Python readss3.signer.uri/s3.signer.endpoint/s3.signer)
S3
- Accept
s3.sse.type/s3.sse.key(Python readss3.server-side-encryption/s3.sse-kms-key-id) - Accept
client.assume-role.arn/client.assume-role.session-name(Python readss3.role-arn,client.role-arn,*.role-session-name) - Accept
s3.path-style-access(inverse of Python'ss3.force-virtual-addressing) - Accept
http-client.proxy-endpoint(Python readss3.proxy-uri) - Accept
http-client.*.connection-timeout-ms(Python readss3.connect-timeoutin seconds)
ADLS / GCS
- ADLS: accept
adls.auth.shared-key.account.name/adls.auth.shared-key.account.key(Python readsadls.account-name/adls.account-key) - ADLS: accept
adls.connection-string.<account>per account (Python reads only a singleadls.connection-string) - GCS: accept
gcs.user-project(closest Python equivalent:gcs.requester-pays)
Metadata
Metadata
Assignees
Labels
No labels
Activity
Ankitraj-builds commentedon Oct 26, 2026
+1, I think matching Java is useful, since one catalog config can then work across clients. Keeping the current Python names as fallbacks would avoid breaking existing users.
Note that s3.remote-signing-enabled from the REST list is already in my open PR #4134.
If this is agreed, I would like to take the SQL catalog items (jdbc.init-catalog-tables / jdbc.schema-version with the current names kept as fallbacks).