[GitHub] [shardingsphere-elastic-job-lite] xlofhappy opened a new issue #753: Library Upgrade

xlofhappy opened a new issue #753: URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/753 the Google-Guava Library is too old, please upgrade it This is an automated message from the Apache Git Service.

[GitHub] [shardingsphere-elastic-job-lite] lovepoem commented on pull request #745: Rename groupId to asf

lovepoem commented on pull request #745: URL: https://github.com/apache/shardingsphere-elastic-job-lite/pull/745#issuecomment-640371055 Good job This is an automated message from the Apache Git Service. To respond to the

[GitHub] [shardingsphere-elastic-job-cloud] terrymanu merged pull request #12: Merge docs

terrymanu merged pull request #12: URL: https://github.com/apache/shardingsphere-elastic-job-cloud/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [shardingsphere-elastic-job-lite] terrymanu merged pull request #752: Merge examples

terrymanu merged pull request #752: URL: https://github.com/apache/shardingsphere-elastic-job-lite/pull/752 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [shardingsphere-elastic-job-cloud] terrymanu merged pull request #11: Merge examples

terrymanu merged pull request #11: URL: https://github.com/apache/shardingsphere-elastic-job-cloud/pull/11 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [shardingsphere-elastic-job-lite] terrymanu merged pull request #751: Merge docs

terrymanu merged pull request #751: URL: https://github.com/apache/shardingsphere-elastic-job-lite/pull/751 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [shardingsphere-elastic-job-lite] terrymanu closed issue #750: 依赖库更新

terrymanu closed issue #750: URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/750 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [shardingsphere-elastic-job-lite] terrymanu commented on issue #750: 依赖库更新

terrymanu commented on issue #750: URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/750#issuecomment-640370326 **For English only**, other languages will not accept. This is an automated message

[GitHub] [shardingsphere-elastic-job-cloud] tuohai666 opened a new pull request #12: Merge docs

tuohai666 opened a new pull request #12: URL: https://github.com/apache/shardingsphere-elastic-job-cloud/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [shardingsphere-elastic-job-cloud] tuohai666 opened a new pull request #11: Merge examples

tuohai666 opened a new pull request #11: URL: https://github.com/apache/shardingsphere-elastic-job-cloud/pull/11 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [shardingsphere-elastic-job-lite] tuohai666 opened a new pull request #752: Merge examples

tuohai666 opened a new pull request #752: URL: https://github.com/apache/shardingsphere-elastic-job-lite/pull/752 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re:Could someone move the notification mail from dev?

+1 | | Lee | | lisufan...@126.com | 签名由网易邮箱大师定制 On 06/8/2020 11:36，Sheng Wu wrote： Hi As new repos have been added, there are many notification mails in the mail list again. Could some one remove them? Sheng Wu 吴晟 Twitter, wusheng1108

Could someone move the notification mail from dev?

Hi As new repos have been added, there are many notification mails in the mail list again. Could some one remove them? Sheng Wu 吴晟 Twitter, wusheng1108

[GitHub] [shardingsphere-elastic-job-lite] tuohai666 opened a new pull request #751: Merge docs

tuohai666 opened a new pull request #751: URL: https://github.com/apache/shardingsphere-elastic-job-lite/pull/751 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [VOTE] Release Apache ShardingSphere 4.1.1

+1， I checked: [x] Download links are valid. [x] Checksums and GPG signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each ShardingSphere repo. [x] All files have license headers if necessary. [x]

[GitHub] [shardingsphere-elastic-job-lite] xlofhappy opened a new issue #750: 依赖库更新

xlofhappy opened a new issue #750: URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/750 项目依赖的 guava 库， 版本太过陈旧，何时可以更新一下版本 This is an automated message from the Apache Git Service. To respond to the

Re: [New API] Automatic Sharding Strategies for Databases and Tables

Hi Sheng, I know your concern, and it will simplify the user's work at the configuration, I believe. I would like to consider giving it a plan, but I also want to listen to others' ideas about it. :) Juan Pan (Trista) Senior DBA & PPMC of Apache ShardingSphere

Re: [New API] Automatic Sharding Strategies for Databases and Tables

Does shardingsphere consider to support wildcard of table name this time? Which is still the biggest block for SkyWalking recommending ShardingSphere as the best-practice solution to medium size users. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年6月7日周日 下午3:00写道： > Thanks for your reply, I

Re: [New API] Automatic Sharding Strategies for Databases and Tables

Thanks for your reply, I will consider your suggestion. Juan Pan (Trista) Senior DBA & PPMC of Apache ShardingSphere E-mail: panj...@apache.org On 06/7/2020 14:47，zhangli...@apache.org wrote： Hi Trista, It is a excellent improvement! I have a little suggestion,

Re: [New API] Automatic Sharding Strategies for Databases and Tables

Hi Trista, It is a excellent improvement! I have a little suggestion, how about separate the table rule configuration to automatic_tables and manual_tables? It may better to create the new concepts about `at_table` and `mt_table`. User should to know what they configure actually.