Hi everyone, Regarding this page:
https://cwiki.apache.org/confluence/display/hive/configuration+properties#ConfigurationProperties-HiveMetastoreConnectionPoolingConfiguration It states that the metastore's Hikari connection pool can be configured by specifying properties prefixed as "hikari". This is not quite correct. In HIVE-17317, there was a bug fix made to the Hikari integration such that the proper prefix is "hikaricp". For example: <property> <name>hikaricp.minimumIdle</name> <value>4</value> <final>false</final> <source>Dataproc Cluster Properties</source> </property> Could you please grant access to me (cnaur...@apache.org) to update the page? If you prefer not to grant access, could a Hive committer make the change for me? BTW, the reason I discovered this is that I recently upgraded a cluster from Hive 2.x (default BoneCP) to Hive 3.x (default HikariCP). After the upgrade, I found that HiveMetaStore was generating far more database connections at baseline, putting extra burden on the database. It appears that BoneCP default behavior (4 idle connections) is different from HikariCP default behavior (idle connections equal to max connections which is 10). This put me down the path of wanting to control Hikari's minimumIdle setting and then finding this discrepancy in the documentation. Passing on this information in case others are seeing unusually high connection counts after an upgrade to 3.x. Chris Nauroth
