Dear: Wechat group "Apache Linkis community Development group "chat records are as follows: 微信群"Apache Linkis 社区开发群"的聊天记录如下: ————— 2022-10-12 ————— peacewong@WDS 11:05 @ kongslove_ samoyeds _ Chen Wendong text east elder brother the JDBC cache size optimization, I think can be optimized, you see submit PR: https://github.com/apache/incubator-linkis/issues/3521 KevinWdong 11:07 I have talked with Brother Long Ping before. In the 1.3.1 version, the data source version is used instead of the url, so this situation can be avoided peacewong@WDS 11:08 Ok, Brother Wendong, close KevinWdong 11:08 OK Heisenberg 11:11 The key of the JDBC cache granularity is currently composed of the data source name and version number. However, when the jdbc URL, user name, and password are passed externally, the cache key is not unique enough Heisenberg and I guess we need to adjust peacewong@WDS 11:20 Yes, the way the console is configured feels like it needs to be optimized peacewong@WDS 11:05 @kongslove_萨摩耶_陈文东 文东兄 这个JDBC缓存粒度优化的，我觉得是可以优化的，你看提交PR下：https://github.com/apache/incubator-linkis/issues/3521 KevinWdong 11:07 之前和龙平兄聊过了，在1.3.1版本里面使用了数据源版本的方式，没有使用url的方式，是可以避免这种情况的 peacewong@WDS 11:08 好的，那文东兄close下 KevinWdong 11:08 OK 海森堡 11:11 这个 JDBC缓存粒度的key目前是数据源名称+版本号 构成的，但是jdbc URL、用户名、密码外部传参这种方式的话，这个缓存key还是有些问题，不够唯一 海森堡 11:12 估计还需要调整下 peacewong@WDS 11:20 是的，管理台配置的方式感觉还是得优化下 -- Best Regards ------ 康悦 ritakang GitHub：Ritakang0451 E-mail：rita0...@163.com
