You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
+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).
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).