why not support set Hikari poolName ?
Feature Request
For English only, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Is your feature request related to a problem?
Describe the feature you would like.

the poolName was added in latest version
Hi, the poolName are suddenly, I think we needn't care it. May I ask what you need to do with it?
ShardingSphere has some scenarios for refreshing metadata, and the connection pool will also be rebuilt. By default, different poolNames will be generated at this time, but if the user specifies a poolName, two pools before and after may have the same name, which may confuse monitoring indicators.
ShardingSphere has some scenarios for refreshing metadata, and the connection pool will also be rebuilt. By default, different poolNames will be generated at this time, but if the user specifies a poolName, two pools before and after may have the same name, which may confuse monitoring indicators.
If use the custome poolName as the prefix, can it be solved?
If use the custome poolName as the prefix, can it be solved?
So how to do with that, do you hava any idea?
ShardingSphere has some scenarios for refreshing metadata, and the connection pool will also be rebuilt. By default, different poolNames will be generated at this time, but if the user specifies a poolName, two pools before and after may have the same name, which may confuse monitoring indicators.
If the user specifies duplicates, it is the user's problem Not currently supported. Let's take a look at the monitoring. How can we match the name of the connection pool with the specific data source?
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.