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
Currently, ConnectionConfig#getHikariConfig bootstraps a MetricsRegistry via SharedMetricRegistries#getOrCreate (see .here However, some users may have their own MetricRegistry that they wish to bootstrap into the config. We can use HikariConfig#setMetricRegistry after the ConnectionConfig has returned the HikariConfig, but in doing so we leave the redundant MetricRegistry hanging in SharedMetricRegistries. We should provide a means for ConnectionConfig to be provided the MetricRegistry directly when creating the HikariConfig.
The text was updated successfully, but these errors were encountered:
Currently,
ConnectionConfig#getHikariConfig
bootstraps a MetricsRegistry viaSharedMetricRegistries#getOrCreate
(see .here However, some users may have their ownMetricRegistry
that they wish to bootstrap into the config. We can useHikariConfig#setMetricRegistry
after theConnectionConfig
has returned theHikariConfig
, but in doing so we leave the redundantMetricRegistry
hanging inSharedMetricRegistries
. We should provide a means forConnectionConfig
to be provided theMetricRegistry
directly when creating theHikariConfig
.The text was updated successfully, but these errors were encountered: