parthshyara opened a new issue, #14003:
URL: https://github.com/apache/iceberg/issues/14003

   ### Feature Request / Improvement
   
   **Description:**
   In `JdbcClientPool.java`, the `properties` field is currently defined as a 
`Map<String, String>`. This design restricts the ability to specify non-string 
properties when configuring JDBC connections.
   
   Many JDBC drivers, including the Snowflake JDBC driver, require properties 
that are not string values. For example, Snowflake supports key-pair 
authentication, where the `privateKey` property must be set as a `PrivateKey` 
object rather than a string. See the Snowflake documentation for reference: 
[Using key pair authentication and key 
rotation](https://docs.snowflake.com/en/developer-guide/jdbc/jdbc-configure#privatekey-property-in-connection-properties).
   
   <br>
   
   **Proposed Improvement:**
   Allow `JdbcClientPool` to support Map<String, Object> or otherwise accept 
non-string values for connection properties. This would enable compatibility 
with drivers that require object-typed properties, such as Snowflake.
   
   <br>
   
   **Use Case:**
   * Enable Snowflake JDBC connections using private key authentication.
   * Broader support for JDBC drivers that depend on non-string property values.
   
   ### Query engine
   
   None
   
   ### Willingness to contribute
   
   - [x] I can contribute this improvement/feature independently
   - [ ] I would be willing to contribute this improvement/feature with 
guidance from the Iceberg community
   - [ ] I cannot contribute this improvement/feature at this time


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to