[GitHub] [incubator-shardingsphere] joooohnli opened a new issue #2010: Do not support connectionInitSqls config of druid connection while using datasource orchestration

[GitBox <gi...@apache.org>]

joooohnli opened a new issue #2010: Do not support connectionInitSqls config of druid connection while using datasource orchestration
URL: https://github.com/apache/incubator-shardingsphere/issues/2010
 
 
   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub issues](https://github.com/sharding-sphere/sharding-sphere/issues).
   - Read documentation: [ShardingSphere Doc](http://shardingsphere.io/document/current/en/overview/).
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response **more than 7 days** and we cannot reproduce it on current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   3.1.0
   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
   Sharding-JDBC
   ### Expected behavior
   support     connectionInitSqls
   ### Actual behavior
   do not
   ### Reason analyze (If you can)
   connectionInitSqls config is a collection:
   
   com.alibaba.druid.pool.DruidAbstractDataSource
   ```
       public Collection<String> getConnectionInitSqls() {...}
   ```
   while uploading, only general types will be serialized, which do not include ```Collection```
   
   io.shardingsphere.core.config.DataSourceConfiguration
   ```
           GENERAL_CLASS_TYPE = Sets.<Class<?>>newHashSet(boolean.class, Boolean.class, int.class, Integer.class, long.class, Long.class, String.class);
   ```
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   
   ### Example codes for reproduce this issue (such as a github link).
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services