[New API] Add new API to check table metadata or not at startup of ShardingSphere
Hi, all To add an API for configuring whether ShardingSphere checks the metadata consistancy of all the tables at startup is in progress Many users will pay more attention on performance at startup, and do not want to check the metadata consistancy of all the tables in database, but others want. Therefore we need to add API to make user decide to check it or not. Please refer to #1688 <https://github.com/sharding-sphere/sharding-sphere/issues/1688> for more detail. - Juan Pan (Trista) Apache ShardingSphere
Module refactoring of merging the data generated by `DISTINCT` syntax
Hi, all New year, new start. The code refactoring of merging the data generated by `DISTINCT` syntax is also on the way. I decided to do this for i got some new ideas about this module implementation so as to make its implementation easier to extend in the next stage and clearer to understand. This work does not take up too much time, so it will be done before next release. - Juan Pan (Trista) Apache ShardingSphere
Re: [apache/incubator-shardingsphere] #1754 failed to get string sharding value (#1760)
Thanks for your proposal, i have checked my name in gitHub already. Juan Pan (Trista) Apache ShardingSphere Craig Russell 于2019年1月16日周三 上午11:19写道： > Can everyone in shardingsphere community please change your name in github > to include your Latin-character name? Having only the Chinese name is > distracting. > > Thanks, > > Craig > > Begin forwarded message: > > *From: *张亮 > *Subject: **Re: [apache/incubator-shardingsphere] #1754 failed to get > string sharding value (#1760)* > *Date: *January 15, 2019 at 7:06:27 PM PST > *To: *apache/incubator-shardingsphere < > incubator-shardingsph...@noreply.github.com> > *Cc: *Subscribed > *Reply-To: *apache/incubator-shardingsphere < > reply+00f8cf44750bbafde2f251df9763fed9e7132cab898464ea92cf0001185661b392a169ce17d1b...@reply.github.com > > > > Merged #1760 > <https://github.com/apache/incubator-shardingsphere/pull/1760> into dev. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-shardingsphere/pull/1760#event-2076330323>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/APjPRFLcyQC1QHJaZozt987Qq0Vv0o5Pks5vDpczgaJpZM4aCMRk> > . > > > Craig L Russell > c...@apache.org > >
[Plan] Enhancement for parsing and rewriting modules of Sharding-Core
To make Sharding-Core stable and reliable, it is necessary to go through current parsing and rewriting modules of Sharding-Core. Here are main tasks: 1. Consider consistent values and names e.g. StartIndex, StopIndex to define token index for rewriting 2. Sort out all of the segments, and consider to define tokenSegment 3. Instead of original literals, use StartIndex, StopIndex to rewrite SQL. 4. Review all of tokens, plese specially notice IndexToken 5. Consider whether statements could be made of segments and tokens. What is your opinion? Welcome to see your reply. - Juan Pan (Trista) Apache ShardingSphere
Re: Discuss for new mentor required of ShardingSphere
+1 for this zhangli...@apache.org 于2018年12月12日周三 上午4:03写道： > Hi all, > > ShardingSphere needs more mentors to help us to create a diverse community > and best practice of Apache way. > So I want to discuss about inviting Von Gosling(apache id is vongosling) as > our mentor. Any suggestions? > > -- > > Liang Zhang (John) > Apache Sharding-Sphere & Dubbo >
Re: Discuss include Elastic-Job as a part of ShardingSphere
Considering the elastic data migration, maybe it is better to use it as an ETL tool, for John is familiar with it. But we also need to spend more time and effort on it, do we have extra energy to take good care of it? zhangli...@apache.org 于2018年12月17日周一 下午3:16写道： > Hi, > > ShardingSphere need a distributed job framework to async execute > retrying and compensation for Saga transaction. > And in future, ShardingSphere also need a job framework as an ETL tool for > elastic data migration. > I plan including elastic-job[1] as a sub project of ShardingSphere or > could use directly. > > Because elastic-job need more works to do, for example: > > 1. Upgrade quartz for elastic-job's dependency, quartz 2.1.1 is use c3p0 > which is LGPL license. > 2. New features, like sharding rule with elastic-job > > So, I prefer make elastic-job as a sub project of ShardingSphere, If the > idea is fine, I can communicate with company, and begin to prepare SGA, any > suggestion? > > [1] https://github.com/elasticjob/elastic-job-lite > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > -- Juan Pan (Trista) Apache ShardingSphere
Re: Discuss for new mentor required of ShardingSphere
Welcome~ -- Juan Pan (Trista) Apache ShardingSphere Gosling Von 于2018年12月14日周五 下午3:11写道： > Hi, > > I would like to help shardingsphere community to be podling. Consider my > personal tech. Interest, I am vey happy to help to build a prosper > Database Middleware in Apache Technology Ecosystem. > > > Best Regards, > Von Gosling > > > 在 2018年12月13日，上午11:06，Willem Jiang 写道： > > > > I think we need the confirmation from Von Gosling. > > > > Gosling Could you reply this mail? > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Dec 13, 2018 at 10:37 AM zhangli...@apache.org > > wrote: > >> > >> Welcome Von Gosling as Apache ShardingSphere's mentor. > >> > >> Hi, Craig and Willem, could you add Von Gosling as mentor to > >> ShardingSphere's whimsy? > >> > >> -- > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> 彭勇升 Peng Yongsheng <8082...@qq.com> 于2018年12月13日周四 上午12:14写道： > >> > >>> +1 > >>> > >>> — > >>> Yongsheng Peng > >>> Apache SkyWalking & ShardingSphere > >>> > >>> > >>> > >>> > >>>> 在 2018年12月12日，11:19，zhangli...@apache.org 写道： > >>>> > >>>> Sorry, I forget to introduce Von Gosling. > >>>> He is initial committer of Apache RocketMQ and Apache Dubbo, he also > is > >>>> mentor of Apache brpc. > >>>> I would like invite Von Gosling sincerely as a mentor of Apache > >>>> ShardingSphere. > >>>> > >>>> -- > >>>> > >>>> Liang Zhang (John) > >>>> Apache ShardingSphere & Dubbo > >>>> > >>>> > >>>> zhaojun 于2018年12月12日周三 上午11:08写道： > >>>> > >>>>> +1 > >>>>> > >>>>> -- > >>>>> Zhao Jun > >>>>> Apache Sharding-Sphere & ServiceComb > >>>>> > >>>>>> On Dec 12, 2018, at 10:11 AM, Willem Jiang > >>>>> wrote: > >>>>>> > >>>>>> Hi Zhangliang, > >>>>>> > >>>>>> I think you may introduce Von Gosling first even I know him a lot. > >>>>>> > >>>>>> Willem Jiang > >>>>>> > >>>>>> Twitter: willemjiang > >>>>>> Weibo: 姜宁willem > >>>>>> > >>>>>> On Wed, Dec 12, 2018 at 4:03 AM zhangli...@apache.org > >>>>>> wrote: > >>>>>>> > >>>>>>> Hi all, > >>>>>>> > >>>>>>> ShardingSphere needs more mentors to help us to create a diverse > >>>>> community > >>>>>>> and best practice of Apache way. > >>>>>>> So I want to discuss about inviting Von Gosling(apache id is > >>>>> vongosling) as > >>>>>>> our mentor. Any suggestions? > >>>>>>> > >>>>>>> -- > >>>>>>> > >>>>>>> Liang Zhang (John) > >>>>>>> Apache Sharding-Sphere & Dubbo > >>>>> > >>>>> > >>> > >>> > >
Re: Release document ref from SkyWalking community
That is just what we need, thanks for your kindness. - Juan Pan (Trista) Apache ShardingSphere 吴晟 Sheng Wu 于2018年12月22日周六 下午9:56写道： > Hi ShardingSphere > > > We are going to move repositories to Apache org soon, plan says Jan. Then > we will face preparing and organizing our Apache release, > beside feature requirements, such as PostgreSQL DB support is the key, we > need to know how to do Apache release. > > > SkyWalking has a long document, lists all steps when SkyWalking release > manager does that. I think you could learn from it. > > https://github.com/apache/incubator-skywalking/blob/master/docs/en/guides/How-to-release.md > > > Also, attention, Apache release requires you prepare LICENSE/NOTICE for > source and distribution packages, which are not same. > There is an Apache license catagory list, you should learn and follow > https://www.apache.org/legal/resolved.html > > > First release is hard, usually take 3-4 votes and more than 1 months to > prepare. Since I am in the project, I hope to assist you move easier. > > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108
New plan for supporting `DISTINCT` syntax
Hi, all As a distributed database middleware, ShardingSphere is on the way to support all the SQL syntax as possible as we can. This current supporting detail of `DISTINCT` syntax is as follows, *Available SQL Of ShardingSphere* SELECT DISTINCT * FROM tbl_name WHERE col1 = ? SELECT DISTINCT col1 FROM tbl_name SELECT DISTINCT col1, col2, col3 FROM tbl_name SELECT COUNT(DISTINCT col1) FROM tbl_name SELECT SUM(DISTINCT col1) FROM tbl_name SELECT DISTINCT col1 FROM tbl_name ORDER BY col1 SELECT DISTINCT col1 FROM tbl_name ORDER BY col2 SELECT COUNT(DISTINCT col1) FROM tbl_name GROUP BY col1 SELECT COUNT(DISTINCT col1), col1 FROM tbl_name GROUP BY col1 *Unavailable SQL Of ShardingSphere* SELECT DISTINCT(col1) FROM tbl_name SELECT COUNT(DISTINCT col1 + col2) FROM tbl_name SELECT AVG(DISTINCT col1) FROM tbl_name SELECT COUNT(DISTINCT col1), SUM(DISTINCT col1) FROM tbl_name SELECT col1, COUNT(DISTINCT col2) FROM tbl_name GROUP BY col1 SELECT SUM(DISTINCT col1), SUM(col1) FROM tbl_name The next step planned is to support 1st, 2nd, 3rd, 5th, 6th of *Unavailable SQL*, and add unit cases for them as well. The expected end time of this task is about before January 4, 2019. More details will be presented on the issues and Prs on gitHub, and any progress will also be updated afterward here. Welcome your suggestions, and wish you *merry **Christmas* - Juan Pan (Trista) Apache ShardingSphere
Re: New feature for Sharding-orchestration
Thanks for your efforts. if so, maybe we can mark this task done. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2018年12月25日周二 下午12:29写道： > I've tried this feature last night. This really can provide good experience > to users. > > juan pan 于2018年12月25日周二 下午12:01写道： > > > Hi all, > > > > This task is moving ahead, here is The lastest status > > <https://github.com/sharding-sphere/sharding-sphere/pull/1665> > > > > On this special day, Merry Christmas to you and your family. > > ----- > > Juan Pan (Trista) > > Apache ShardingSphere > > > > > > juan pan 于2018年12月23日周日 上午9:59写道： > > > > > Hi everyone, > > > > > > Considering the suggestions from ShardingSphere community, I plan to > add > > a > > > new feather for Sharding-orchestration, which basically includes > > > 1. User can add or delete scheme configurations in registry, e.g. > > > zookeeper or etcd. > > > 2. Registry pushes those changed events to all of applications online. > > > 3. Applications online refresh their schema configurations to make > those > > > changes effective. > > > > > > Your voice is important for this feature, any suggestion, please tell > me. > > > > > > - > > > Juan Pan (Trista) > > > Apache ShardingSphere > > > > > > > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: New feature for Sharding-orchestration
Hi all, This task is moving ahead, here is The lastest status <https://github.com/sharding-sphere/sharding-sphere/pull/1665> On this special day, Merry Christmas to you and your family. - Juan Pan (Trista) Apache ShardingSphere juan pan 于2018年12月23日周日 上午9:59写道： > Hi everyone, > > Considering the suggestions from ShardingSphere community, I plan to add a > new feather for Sharding-orchestration, which basically includes > 1. User can add or delete scheme configurations in registry, e.g. > zookeeper or etcd. > 2. Registry pushes those changed events to all of applications online. > 3. Applications online refresh their schema configurations to make those > changes effective. > > Your voice is important for this feature, any suggestion, please tell me. > > - > Juan Pan (Trista) > Apache ShardingSphere >
New feature for Sharding-orchestration
Hi everyone, Considering the suggestions from ShardingSphere community, I plan to add a new feather for Sharding-orchestration, which basically includes 1. User can add or delete scheme configurations in registry, e.g. zookeeper or etcd. 2. Registry pushes those changed events to all of applications online. 3. Applications online refresh their schema configurations to make those changes effective. Your voice is important for this feature, any suggestion, please tell me. - Juan Pan (Trista) Apache ShardingSphere
Enhancement for generating globally unique ID for ShardingSphere
To modify API of generating gobally unique ID, and provide alternatives of gobally unique ID generator for users now is planned to start. Here are the main tasks of this plan: - 1. Modify the type of returned value of keyGenerator from Number to Comparable. - 2. Support to set or get properties for keyGenerator by all kinds of configuration files, e.g. yaml or springboot. - 3. Modify API of keyGenerator for Sharding-JDBC and Sharding-Proxy - 4. Besides Snowflake, implement other popular keyGenerator algorithms for ShardingSphere, e.g. Leaf[1] or UUID. [1] https://tech.meituan.com/MT_Leaf.html The first task has been done, please refer to https://github.com/sharding-sphere/sharding-sphere/pull/1724. Any suggestions, please reply to this email. - Juan Pan (Trista) Apache ShardingSphere
Re: Module refactoring of merging the data generated by `DISTINCT` syntax
Yep, there is no other better solutions except sorting result sets, but the important thing is how? Firstly how to rewrite those sytaxes, e.g. `AVG(DISTINCT col)`, rewrite it to `DISTINCT col` or not? Secondly how to sort those result sets to calcuate aggregation results of distinct columns, e.g. `SUM(DISTINCT col1 + col2)` row by row for each result set. Finally, how to make users get the resultset using original column labels or indexes, not the rewrited column labels or indexes. - Juan Pan (Trista) Apache ShardingSphere Hongtao Gao 于2019年1月3日周四 下午2:37写道： > Would you list some examples to share the "new ideas"? I couldn't find > other solutions besides sorting result sets. > > juan pan 于2019年1月2日周三 上午10:49写道： > > > Hi, all > > > > New year, new start. > > > > The code refactoring of merging the data generated by `DISTINCT` syntax > is > > also on the way. > > > > I decided to do this for i got some new ideas about this module > > implementation so as to make its implementation easier to extend in the > > next stage and clearer to understand. > > > > This work does not take up too much time, so it will be done before next > > release. > > > > - > > Juan Pan (Trista) > > Apache ShardingSphere > > > > > -- > Gao Hongtao > Apache SkyWalking & ShardingSphere >
Re: [Feature Enhancement] Provide Spring Configuration method to use the feature of Data Masking
Thanks for your reply. I just consider to provide different configuration modes for users to use data masking feature. Here[1] is the difference between Java code and spring configuration. - [1] https://shardingsphere.apache.org/document/current/en/manual/sharding-jdbc/usage/encrypt/ - Juan Pan (Trista) Apache ShardingSphere guangyuan wang 于2019年4月1日周一 下午8:36写道： > It is a good idea to provide another way to configure data masking. Could > you explain more clearly about the difference between Java code and spring > configuration. > Does spring configuration like class with @Configuration? > > juan pan 于2019年4月1日周一 下午7:00写道： > > > Hi, everyone. > > > > This email is to discuss to schedule to provide Spring configuration > method > > for the dataSource of Data masking. > > > > *Current Situation* > > > > * ShardingSphere can provide Java code and Yaml file for users to use the > > feature of data masking. > > * The feature of data masking is in the process of pressure test. > > > > *Plan* > > > > In 4.0.0-RC2-SNAPSHOT, it is necessary to provide Spring configuration > > method to use the feature of Data masking, for a lot of business projects > > start up by Spring framework. > > > > The main Spring frameworks needed to consider: > > > > - [ ] Spring Boot > > - [ ] Spring Namespace > > > > > > Now we are preparing for our first Apache version release which is very > > important for us. Hope everything goes well. > > > > If you have any suggestion, please let us know. > > > > Thanks. > > > > - > > Juan Pan (Trista) > > Apache ShardingSphere > > >
Re: Release votes
Hello, everyone Our release vote template has been updated already, please visit [1] to learn more. Thanks for your attention. - [1] https://shardingsphere.apache.org/community/en/contribute/release/ - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年4月5日周五 下午6:01写道： > +1 for Craig's suggestion. > > Right now the release guide is in [1], it include release vote template. > We can update our release vote template, and make sure every vote need > finish the checklist. > > [1] https://shardingsphere.apache.org/community/en/contribute/release/ > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > 吴晟 Sheng Wu 于2019年4月5日周五 上午11:18写道： > > > Hi > > > > > > +1 for Craig's suggestion. > > > > > > ShardingSphere community release vote should follow this way. > > In SkyWalking release vote, I think most PPMC provided their checked > list. > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "apache.clr"; > > Date: Fri, Apr 5, 2019 10:56 AM > > To: "dev"; > > > > Subject: Re: Release votes > > > > > > > > Sorry, totally forgot the link > > > > > > > https://lists.apache.org/thread.html/c891eb5543559d8894974ea39b11001e4302c1e3b0f11e47323af929@%3Cdev.openwhisk.apache.org%3E > > > > > > > On Apr 4, 2019, at 4:09 PM, Craig Russell > wrote: > > > > > > Hi, > > > > > > I'd like you to take a look at this release vote by OpenWhisk. In > > particular, the call for a vote has a checklist that the reviewers are > > expected to look at. > > > > > > The reviewers itemize which checklist items that they actually checked. > > > > > > This is a model for release votes in the podling community. Let's see > if > > we can do the same here. > > > > > > I've seen recent podling votes in which most of the votes were simple > > +1. Let's not do that. > > > > > > Craig > > > > > > Craig Russell > > > Member, Apache Incubator PMC > > > apache@gmail.com > > > > > > > > > > > > > Craig Russell > > Member, Apache Incubator PMC > > apache@gmail.com >
[Feature Enhancement] Provide Spring Configuration method to use the feature of Data Masking
Hi, everyone. This email is to discuss to schedule to provide Spring configuration method for the dataSource of Data masking. *Current Situation* * ShardingSphere can provide Java code and Yaml file for users to use the feature of data masking. * The feature of data masking is in the process of pressure test. *Plan* In 4.0.0-RC2-SNAPSHOT, it is necessary to provide Spring configuration method to use the feature of Data masking, for a lot of business projects start up by Spring framework. The main Spring frameworks needed to consider: - [ ] Spring Boot - [ ] Spring Namespace Now we are preparing for our first Apache version release which is very important for us. Hope everything goes well. If you have any suggestion, please let us know. Thanks. - Juan Pan (Trista) Apache ShardingSphere
Re: [DISCUSS] ShardingSphere 4.0.0-RC1 release [ROUND 2]
After my items-checking, i think it is time for our 4.0.0-RC1 release. Here are my checked items, Feature check 1. DISTINCT SQL syntax available. 2. Data encrypt available. 3. All SQL 100% compatible if route to single data node (MySQL Only). Release check 1. sha512 hash. 2. gpg Signature. 3. Items for source package. 4. Items for binary packages. - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年3月29日周五 下午2:58写道： > Hello ShardingSphere Community, > > This is a call for 2 round of discuss to release Apache ShardingSphere > (Incubating) version 4.0.0-RC1 > > Release notes: > * > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-a7276f4b3f5fb99f2c2b > < > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-a7276f4b3f5fb99f2c2b > >* > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1 > > Release Commit ID: > * > https://github.com/apache/incubator-shardingsphere/commit/709b5f58793be11e19309b59554ad5f7df19f9e0 > < > https://github.com/apache/incubator-shardingsphere/commit/709b5f58793be11e19309b59554ad5f7df19f9e0 > >* > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > Checklist: > https://shardingsphere.apache.org/community/en/contribute/release/ > > Every who inserted can be do acceptance test and discuss this version > should be release or not. > > The first discussion and result is in threads [1] and [2]. > [1] > > https://lists.apache.org/thread.html/953e8d42e7106d4d5dd29f61ece6c10c8210a9c48232c7fb90484851@%3Cdev.shardingsphere.apache.org%3E > [2] https://lists.apache.org/thread.html/2099ff699a427565f978b9f020ffa2 > < > https://lists.apache.org/thread.html/2099ff699a427565f978b9f020ffa289c001acea62642408b95b0203@%3Cdev.shardingsphere.apache.org%3E > > > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [Discuss] Acceptance test for ShardingSphere 4.0.0 [RC1] release
I give more attention to the following items, for i participated in developing those new features. 1. DISTINCT SQL syntax available. 2. Data encrypt available. After testing for those features, i think it is ok for this version release. - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年3月25日周一 上午11:02写道： > Hello ShardingSphere Community, > > This is a call for discuss to release Apache ShardingSphere (Incubating) > version 4.0.0-RC1 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-90bdf1e5cbba8422332f > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/90a17fd3ac5af99d0fe1bd8018ba1393b1864672 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > Every who inserted can be do acceptance test and discuss this version > should be release or not. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: Re: [Discuss] Acceptance test for ShardingSphere 4.0.0 [RC1] release
+1 I think we can do this version release, hope everything will go well. - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年3月27日周三 上午11:34写道： > I summarize the issues we received on this thread: > > 1. PR for [1], missing some licenses, already merged. > 2. Sharding-proxy can’t run for lacking of some jars, reason is from OS > file path setting, not ShardingSphere issue. > 3. Navicat premium 12 connect sharding-proxy using MySQL protocol, it > connected but no database. Fixed at PR[2]. > 4. Some DISTINCT SQL loses data, submit a issue[3] and make sure it is not > a blocking issue. > 5. Compile error by guangyuan wang, caused by his environment. Travis can > compile success, FYI[4] > > All blocking issues are resolved and some unblocking issue are recorded, > will fix next version. > So can we do release now? Any suggestion? > > [1] https://github.com/apache/incubator-shardingsphere/pull/2078 > [2] https://github.com/apache/incubator-shardingsphere/pull/2102 > [3] https://github.com/apache/incubator-shardingsphere/issues/2094 > [4]https://travis-ci.org/apache/incubator-shardingsphere > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > > zhangli...@apache.org 于2019年3月27日周三 上午11:24写道： > > > Hi guangyuan wang, > > > > This is caused by your environment. Please check travis : > > https://travis-ci.org/apache/incubator-shardingsphere get more details. > > > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > guangyuan wang 于2019年3月27日周三 上午11:19写道： > > > >> After executed "mvn clean install",it shows: > >> [ERROR] Failed to execute goal on project sharding-core-parse-mysql: > Could > >> not resolve dependencies for project > >> org.apache.shardingsphere:sharding-core-parse-mysql:jar:4.0.0-RC1: > Failed > >> to collect dependencies at > >> org.apache.shardingsphere:sharding-core-parse-spi:jar:4.0.0-RC1: Failed > to > >> read artifact descriptor for > >> org.apache.shardingsphere:sharding-core-parse-spi:jar:4.0.0-RC1: Failure > >> to > >> find org.apache.shardingsphere:sharding-core:pom:4.0.0-RC1 in > >> https://repo.maven.apache.org/maven2 was cached in the local > repository, > >> resolution will not be reattempted until the update interval of central > >> has > >> elapsed or updates are forced -> [Help 1] > >> > >> > >> duhongjun 于2019年3月26日周二 下午4:29写道： > >> > >> > use antlr parse SQL statement, Lexer and Parser class are generated by > >> > antlr maven plugin > >> > execute mvn clean install in sharding-core-parse-mysql project or > >> parent > >> > project > >> > after execute command successfully，the source code is generated in > >> > target/generated-sources/antlr4 directory > >> > > >> > > >> > > >> > > >> > > >> > -- > >> > > >> > - > >> > > >> > HongJun Du > >> > Apache ShardingSphere > >> > > >> > > >> > > >> > At 2019-03-26 14:14:07, "guangyuan wang" wrote: > >> > >Please see org.apache.shardingsphere.core.parse.H2ShardingParseEngine > >> > class > >> > >in 4.0.0 RC1 source code. > >> > > > >> > >In IntelliJ IDEA shows : Missing > >> > org.apache.shardingsphere.core.parse.antlr. > >> > >autogen.MySQLStatementLexer. > >> > > > >> > >After checked,I found MySQLStatementLexer.class does not exist in the > >> > >source code. > >> > > > >> > >On 2019/03/25 03:02:16, "z...@apache.org" wrote: > >> > >> Hello ShardingSphere Community,> > >> > >> > >> > >> This is a call for discuss to release Apache ShardingSphere > >> > (Incubating)> > >> > >> version 4.0.0-RC1> > >> > >> > >> > >> Release notes:> > >> > >> > >> > > > >> > > >> > https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-90bdf1e5cbba8422332f > >> > > > >> > > > >> > >> > >> > >> The release candidates:> > >> > >> > >> > > >> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ > >> > > > >> > > > >> > >> > >> > >> Maven 2 staging repository:> > >> > >> > >> > > > >> > > >> > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > >> > > > >> > > > >> > >> > >> > >> Git tag for the release:> > >> > >> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1> > >> > >> > >> > >> Release Commit ID:> > >> > >> > >> > > > >> > > >> > https://github.com/apache/incubator-shardingsphere/commit/90a17fd3ac5af99d0fe1bd8018ba1393b1864672 > >> > > > >> > > > >> > >> > >> > >> Keys to verify the Release Candidate:> > >> > >> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > >> > > >> > >> > >> > >> Every who inserted can be do acceptance test and discuss this > >> version> > >> > >> should be release or not.> > >> > >> > >> > >> --> > >> > >> > >> > >> Liang Zhang (John)> > >> > >> Apache ShardingSphere & Dubbo> > >> > >> > >> > > >> > > >
[New feature] Independent encryptedDataSource to decrypt or encrypt sensitive data.
Hi, everyone, This new feature development plan needs your advice. It is to create independent encrypted DataSource which can encrypt sensitive information, e.g, password or ID to store them in database, and decrypt ciphertext in database for queries. By using encrypted DataSource, you can encrypt or decrypt sensitive data in aboriginal JAVA coding way. Here are the main tasks: - [ ] SQL parsing for sensitive columns - [ ] SQL rewriting for sensitive columns - [ ] SQL executing with encrypt DataSource - [ ] SQL resultSet creating - [ ] JDBC interface implementation for EncryptedDataSource, EncryptedConnection, EncryptedPreparedStatement, EncryptedStatement, EncryptedResultSet. - [ ] Usage API for Yaml, Spring, Proxy Currently first task is assigned to hongJun Du, and i am doing the rest. Any suggestions, please let us know. Waiting for your reply. - Juan Pan (Trista) Apache ShardingSphere
Re: [New feature] Sharding Encryptor
Hi, everyone, This task has been done almostly. The rest of work is to parse SQL to fill necessary objects, which will be done by hongJun Du. You can get more details by this issue [1]. If any problems, please contact me. Hope everything will be ok with you. [1] https://github.com/apache/incubator-shardingsphere/issues/1844 - Juan Pan (Trista) Apache ShardingSphere 吴晟 Sheng Wu 于2019年1月30日周三 下午9:40写道： > If you are planning to use Apache common to do md5, I think it is safe. > Just be carefully, if someone tries to contribute new encrytor, you may > can't accept it. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: zhangli...@apache.org > Date: Wed,Jan 30,2019 9:07 PM > To: dev > Subject: Re: [New feature] Sharding Encryptor > > > > Use MD5 by default, and provide interface, can use SPI to adapter > customized encryption algorithm by user. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > 吴晟 Sheng Wu 于2019年1月30日周三 下午7:13写道： > > > What encryptor? Is there any encryption algorithm in it? > > > > > > Apache has some rules to make sure you are not breaking the IP related to > > this. > > > > > > > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > > > From Wu Sheng 's phone. > > > > > > -- Original -- > > From: juan pan > > Date: Wed,Jan 30,2019 7:10 PM > > To: dev > > Subject: Re: [New feature] Sharding Encryptor > > > > > > > > [New feature] Sharding Encryptor > > > > This new feature is to encode sensitive information, e.g, password or ID > to > > store them in databases, and decode ciphertext in databases for queries. > > Here are the main tasks: > > > > * SQL parsing for sensitive columns > > * SQL rewriting for sensitive columns > > * API of Sharding Encryptor > > - [ ] Design API of encryptor for ShardingRule > > - [ ] Design API of encryptRule > > - [ ] Design API of encryptor for Sharding SpringNameSpace > > - [ ] Design API of encryptor for Sharding SpringBoot > > - [ ] Add unit tests > > * JDBC interface implementation for Sharding Encryptor > > * Built-in Encryptor implementation > > > > This new feature is important and time-consuming, so each of tasks will > > take a plenty of time to finish.Currently first task is assigned to > Hongjun > > Du, and i am doing the thrid one, whose child tasks can be seen above. > > *@Hongjun > > Du*, can you list the child tasks of first one? > > > > I hope i can finish the third one before Spring Festival, therefore i can > > continue to do others. > > > > Any suggestions, please let us know. Waiting for youre reply. > > - > > Juan Pan (Trista) > > Apache ShardingSphere
[New API] Write configuration online into log files
To write configuration online into log files will make user get configuration online, so that users can check configs or troubleshoot. Therefore, we plan to add API to control ShardingSphere writes configuration online into log files. Development todo lists: - [ ] At start up, ShardingSphere writes configuration online into log files in the uniform format. - [ ] When configuration is refreshed, new configuration will be written into log files. - [ ] Move the module of yaml conversion from orchestration to sharding core. If you have any suggestion, please reply this email,thanks a lot. - Juan Pan (Trista) Apache ShardingSphere
Re: [VOTE]: Release Apache ShardingSphere (Incubating) 4.0.0-RC1 [ROUND 3]
+1 approve - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年4月13日周六 上午1:57写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0-RC1 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-d5d2dc137c82994bbaac > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/2c1d23f9569e5cbe74074a578931c77dfa800800 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: Talk about opportunity to upgrade Java version form 7 to 8 on ShardingSphere
We can enjoy the new feature of JDK 8, and as Sheng Wu said, updating to JDK 8 is not difficult. After we listen to voices of SharingSphere community, i think it is better to upgrade. My +1 to upgrade. - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年5月30日周四 下午2:48写道： > Hi, > > JDK 7 is deprecated for long time by official, more and more applications > are using JDK 8 as their Java compile environment. > > Some dependencies of ShardingSphere are using JDK 8 also, such as Etcd, > ServiceComb, Seata and new version of Guava, so I plan upgrade to JDK 8 > after 4.0.0 stable version released. > > For ShardingSphere 4.0.0, we are still using JDK7, and switch to JDK 8 for > 4.1.x version of ShardingSphere. > > Any suggestions? > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [DISCUSS] The scope of Sharding-Sphere 4.0.0-RC2 release
Here are some of important issues i solved, we can consider to add them to RC2 release note. New Feature 1.User can do data masking by using ShardingProxy(#2443). 2.User can use Leaf-segment generator to get distributed ID(#1775). API 1.Delete API and configuration item of sharding logicIndex(#2464). Optimization 1.Renew modified dataSources, not all the datasources to improve performance for configuration orchestration(#1427). Module Refactoring 1.The Refactoring of SQL rewriting module(#2275). Bug Fix 1.Fix wrong SQL rewriting for `Create/Alter/Drop index` with indexName quoted with quoteCharacters(#2312). 2.Fix NullPointerException when append generated-key value for `INSERT` statement(#2252). References: https://github.com/apache/incubator-shardingsphere/issues/2443 https://github.com/apache/incubator-shardingsphere/issues/1775 https://github.com/apache/incubator-shardingsphere/issues/2464 https://github.com/apache/incubator-shardingsphere/issues/1427 https://github.com/apache/incubator-shardingsphere/issues/2275 https://github.com/apache/incubator-shardingsphere/issues/2312 https://github.com/apache/incubator-shardingsphere/issues/2252 - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年6月13日周四 下午12:32写道： > [1] > > https://github.com/apache/incubator-shardingsphere/issues?q=is%3Aissue+is%3Aclosed+milestone%3A4.0.0.M2 > [2] https://github.com/seata/seata > > Zhang Yonglun 于2019年6月13日周四 下午12:30写道： > > > Hi, > > > > I'll be the release manager of Sharding-Sphere 4.0.0-RC2. So many > > issues[1] resolved after 4.0.0-RC1, it's not necessary to include them > all > > in release note. > > > > In my opinion, there are 4 main features which should be appear in the > > release note: > > 1. The parse engine upgrade from the 2nd generation to 3rd. > > 2. Integration of Seata[2] for distributed transaction. > > 3. OpenShardingUI administration console. > > 4. Support Skywalking plugin for application performance management. > > > > For now, the OpenShardingUI haven't been merged into ShardingSphere. I am > > not sure whether we should include it in the new release. Any > suggestions? > > > > -- > > Zhang Yonglun > > Apache ShardingSphere > > > > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: How the sharding works when no sharding key defined
Hi, Eric. Thanks for your attention. 1) Sharding is also applied on records update, insert, delete, truncate, etc. ShardingSphere will handle records by using the sharding rule. For example, when execute `UPDATE tableName SET...Where id =1`, ShardingSphere will only update the record of id = 1 in odd number database. 2) Firstly, On the condition that sharding rules defined on the primary key (although sharding key and primary key can be different), you can tell ShardingSphere by using settings that you want to have global automatically ID as primary key, then ShardingSphere will generate global ID and put it into INSERT SQL, then this record will be inserted into correct database and table. But for you, when write INSERT SQL, you can ignore to set primary key. Secondly, if you do not configure global automatically ID as primary key in sharding rule and want to use the key automatically generated by database, as you said, ShardingSphere can not know the key beforehand in the SQL, finally all the databases will have those records. 3) Firstly, If a table has not sharding rule defined but all databases have the complete records, we suggest you can configure this table as `broadcastTable` in configuration. As a table is broadcastTable, when `SELECT FROM broadcastTable`, this query will be executed in random one of databases; when `DELETE/UPDATE/INSERT` in broadcastTable, SQLs will be broadcasted and executed in all the databases. Secondly, If a table has not sharding rule defined, and is not a `broadcastTable`, but you configure a `default datasource`, ShardingSphere will send all SQLs of this table to default datasource. Finally, if a table has not sharding rule defined, and is not a `broadcastTable`, and there is no `default datasource`, it will throw a routing exception, for it does not know where this query should be sent. 4) One one hand, you can configure `default datasource` in sharding rule, so it will throw all SQLs to this default datasource, which is called sharding scenario. On the other hand, If you just want to load balance, please configure two or more databases, and tell ShardingSphere which one is master database and slave databases, and it will choose one database randomly to route your SQLs, which is called master-slave scenario. Two of scenarios are supported in ShardingSphere. - Juan Pan (Trista) Apache ShardingSphere Eric 于2019年6月29日周六 上午5:30写道： > Hi, > > I am exploring the Sharding Sphere. I may have misunderstanding on the > concepts. Very appreciated for your help on following questions. > > 1) Is sharding also applied on records update and insert? For example, the > table sharding rules define even and odd numbers records on two different > databases. When updating or inserting records, are these records updated > and inserted on both databases? > > 2) If sharding also applied on records update and insert, if there are > sharding rules defined on the primary key of a table but the key is > automatically generated by database, inserting a new record would not know > the key beforehand in the SQL Would this record inserted in all the > databases or the database defined by the table sharding rule? > > 3) If a table has not sharding rule defined but all databases have the > complete records, which database will execute the query on this table? > > 4) Can we define default rules when there is no sharding rule matched route > the query randomly to a database like simple load balancing? > > Best Regards, > Eric Poon >
Re: [DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 1]
I give more attention and tests to Sharding-JDBC, and i think main feature tests for this version is ok, so we can continue to do release. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年6月27日周四 下午3:54写道： > Hello ShardingSphere Community, > > This is a call for the 1th round of discussion to release Apache > ShardingSphere > (Incubating) version 4.0.0-RC2 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e > > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > < > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/7befe25afee89ab8408b8c8ed50384f1c94e2a4e > > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > GPG username: zhangyonglun > > Checklist: > https://shardingsphere.apache.org/community/en/contribute/release/ > > Anyone who is interested can do this acceptance test and discuss whether > this version should be released or not. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: Re:Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 4]
The issue[1] mentioned by Sion Yang has been fixed already, please check the Pr[2]. [1] https://github.com/apache/incubator-shardingsphere/issues/2883 [2] https://github.com/apache/incubator-shardingsphere/pull/2886 - Juan Pan (Trista) Apache ShardingSphere Sion Yang 于2019年8月16日周五 下午5:17写道： > These two issues can reproduce in > apache/incubator-shardingsphere-example[1]. > And I also open issue in GitHub[2][3]. > > > [1] https://github.com/apache/incubator-shardingsphere-example > [2] https://github.com/apache/incubator-shardingsphere/issues/2883 > [3] https://github.com/apache/incubator-shardingsphere/issues/2884 > > > -- > > Yi Yang(Sion) > Apache ShardingSphere > > > > At 2019-08-16 17:09:48, "Sion Yang" wrote: > >There are another issue[1] for encrypt in 4.0.0-RC2. > >Encrypt may replace table name with column so that the column in SQL > become `column.column`. > > > > > >[1] https://github.com/apache/incubator-shardingsphere/issues/2883 > > > > > >-- > > > >Yi Yang(Sion) > >Apache ShardingSphere > > > > > > > >At 2019-08-13 18:38:13, "Sion Yang" wrote: > >>I execute all examples. Most of examples execute successfully except > encrypt in JPA with SpringBoot. > >>The bug has marked `TODO` in example, and only affects part of encrypt. > >>So i think we can continue to prepare our version 4.0.0-RC2. > >> > >> > >>-- > >> > >>Yi Yang(Sion) > >>Apache ShardingSphere > >> > >> > >> > >>At 2019-08-09 18:46:33, "Zhang Yonglun" wrote: > >>>Hello ShardingSphere Community, > >>> > >>>This is a call for the 4th round of discussion to release Apache > >>>ShardingSphere (Incubating) version 4.0.0-RC2 > >>> > >>>Release notes: > >>> > https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-08931c6025e028ee428c > >>> > >>>Git branch for the release: > >>>The dev branch of ShardingSphere( > >>>https://github.com/apache/incubator-shardingsphere.git) > >>> > >>>We have fixed all know serious issues found during the integration > test. So > >>>the dev branch is ready for discussion. > >>> > >>>Anyone who is interested can do this acceptance test and discuss whether > >>>this version should be released or not. > >>> > >>>-- > >>>Zhang Yonglun > >>>Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2 [ROUND 4]
+1 The following checking items have been done. [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年8月17日周六 下午3:44写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0-RC2 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > GPG username: zhangyonglun > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: [DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 4]
Today, i ran some tests, and a bug of wrong rewritten SQL for `INSERT` in multiple threads appeared. Now this bug has been fixed already. It is not a big deal, so i think we can continue to prepare our version 4.0.0-RC2. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年8月9日周五 下午6:46写道： > Hello ShardingSphere Community, > > This is a call for the 4th round of discussion to release Apache > ShardingSphere (Incubating) version 4.0.0-RC2 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-08931c6025e028ee428c > > Git branch for the release: > The dev branch of ShardingSphere( > https://github.com/apache/incubator-shardingsphere.git) > > We have fixed all know serious issues found during the integration test. So > the dev branch is ready for discussion. > > Anyone who is interested can do this acceptance test and discuss whether > this version should be released or not. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: [DISCUSS] Do we have to resolve issue #2884 in 4.0.0-RC2
Ok, so that we can have more time to take care of it, and yesterday one volunteer also showed interest on it. So i think fixing it in our next version is better. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年8月21日周三 上午10:58写道： > Hi, > > I think this issue ( > https://github.com/apache/incubator-shardingsphere/issues/2884) is not a > serious or block bug. What's your opinion on this? I suggest to resolve > this problem in the next release. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: Create table returns error cannot find table rule
Yes, you’re right. The sharding rule is prerequisite before you execute any SQL. - Juan Pan (Trista) Apache ShardingSphere Eric 于2019年9月9日周一 上午5:53写道： > Hi Juan, > > Thank you. > > I think that makes sense because rules are need for the routing even though > the table can be created. Which means the rule has to be setup before > creating tables. > > Regards, > Eric Poon >
Re: [Event time] Do the two podling have interests to hold an eventtogether?
Hi William and LiDong, Thanks for your detailed schedule. And thanks for clickhouse's rich experience as well. :) We will consider this proposal seriously. How about this co-meetup, everybody of ShardingSphere? Best wishes, Trista | | Juan Pan | | panj...@apache.org Juan Pan(Trista), Apache ShardingSphere | Signature is customized by Netease Mail Master On 09/14/2019 17:57, Guo William wrote: Hi, We’d like to add more information about Dolphin Scheduler meetup for discussion: Dolphin Scheduler Meetup agenda is planed to be formed by 3 part: I Morning Close Door Meeting for core developer and committer: Mainly discuss roadmap, new feature, bugs, and let core team get to know each other face to face… (For this part we can hold 2 separated meeting for both DolphinScheduler and ShardingSphere in two office at the same time) II Afternoon Open Door Meeting Just as Lidong said, we has a roughly plan for Shanghai Meetup, mainly talk to users, encourage them to become contributor and committer. (From this part, two meetup can combine together for more influence) III Evening Salon Gathering Gathered the core developers, the speakers, the volunteers to know each other to activate the community in this city or area. (We can offer supper) This kind of meetup agenda (Part I,Part II, Part III) is validated for clickhouse community's 3-years running experience (According to the core team of CK, key users grew 3-4 times per year in China, till now more than 2000 enterprises is using CK. Core contributors in China was grown from 4 to more than 40). So this is a good form for open source meetup in China for now. We also suggest this agenda for both meetup. :) For now Dolphin Scheduler team has just confirmed the agenda for Shanghai Meetup on 2019，Oct, 26. And we are planning the second meetup on Nov, 10 in Beijing. The meetup time can be re-schedule according to the available time for both team. We are highly appreciated for the co-meetup, and we can offer the place and admin support. Dolphin Scheduler (Incubator) William Guo Wei 原始邮件 发件人: lidong dai 收件人: dev; d...@dolphinscheduler.apache.org 发送时间: 2019年9月14日(周六) 16:49 主题: Re: [Event time] Do the two podling have interests to hold an eventtogether? hi ： we are very willing to organize meetup together, we plan to hold two meetups in Shanghai and Beijing respectively. Here is the original plan meetup content of DolphinScheduler： “ Apache DolphinScheduler(incubator) User Meetup Date: 2019，Oct, 26 （2019年10月26日） Meetup Place: 3R20, No. 1107, Yuyuan Road, Changning District, Shanghai.（上海长宁区愚园路1107号创邑3R20） Agenda(议程): 1、Introduction/overview of DolphinScheduler (William-GuoWei). 2、DolphinScheduler internals, fairly technical: how DolphinScheduler works and so on (Zhanwei Qiao). 3、DolphinScheduler practice (拟定) 4、DolphinScheduler from Zero to One (拟定) 5、DolphinScheduler practice(拟定) 6、Recently released features and Roadmap (Lidong Dai) 7、Free discussion ” Currently, the meetup in Shanghai is recruiting lecturers. Perhaps the shardingsphere can also talk about several topics, which can be arranged together. haha. and We also plan to do a meetup in Beijing ，maybe in November. very glad to hear your opinions! --- Lidong Dai(DolphinScheduler) From: Sheng Wu mailto:wu.sheng.841...@gmail.com>> Sent: Friday, September 13, 2019 23:38 To: dev mailto:dev@shardingsphere.apache.org>>; d...@dolphinscheduler.apache.org<mailto:d...@dolphinscheduler.apache.org> mailto:d...@dolphinscheduler.apache.org>> Subject: [Event time] Do the two podling have interests to hold an event together? Hi DolphinScheduler and ShardingSphere I am being told there is an event of new DolphinScheduler meetup happens soon, 2 months later, I think. Due to these two young communities, do you have interests to host the event together? And set up the talks to attract more potential contributors, which are required at both sides. Pure my personal suggestion, considering I am at both sides. Sheng -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: Multiple SQL units scene
Sorry, i can not get your idea. But when Sharding and multiple tables are existed in one database, it is possible that a SQL is executed in multiple tables in one database. - Juan Pan (Trista) Apache ShardingSphere 厉忠 于2019年9月7日周六 下午2:10写道： > Ask, when executing sql, what scenario will a single data source correspond > to multiple SQL units? > Thank you. >
Re: Create table returns error cannot find table rule
Hi, Eric. DDL SQL will be routed to all the databases configured in setting file, please notice, not just all the instances. But the first thing is that you need to create a Sharding rule to tell ShardingSphere which databases tables are created. - Juan Pan (Trista) Apache ShardingSphere Eric 于2019年9月8日周日 上午12:42写道： > Hi, > > I tried following statement, it returned an error "Cannot find table rule > and default data source with logic table: 'test1'". I think ShardingSphere > route DDL statement to all database instances by default? > > Please help. > > create table test1 ( > field1 varchar(40)); > > Best Regards, > Eric Poon >
Re: Talk about how to set committer bar
Agree with William and Sheng. Dynamic and not tight rules will attract more participants to contribute. If he or she can show their commitment to community, we can invite them. Actually, after browsing the Issues and Prs currently in community, i think there are some participants who we can invite as commiters. Hope community will be more prosperous. - Juan Pan (Trista) Apache ShardingSphere zhangli...@apache.org 于2019年9月5日周四 下午9:29写道： > Hi ShardingSphere community, > > There are 64 contributors for ShardingSphere, I want discuss about elected > more committers. > > How to set committer bar? The previous rules can find here[1], they are: > > >1. Make contributions consistently during the past 6 months >2. Understand the core technology of ShardingSphere deeply >3. Obey the Code of Conduct >4. Submit high-quality content >5. Enable Google Two-factor authentication > > The committer bar perhaps too high for new committers, can we define some > new rule to elect more committers? > > [1] https://shardingsphere.apache.org/community/en/contribute/committer/ > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
new committer: Haisheng Sun
TheProjectManagementCommittee(PMC)forApache ShardingSphere hasinvited Haisheng Sun tobecomeacommitterandwearepleasedtoannouncethathehasaccepted. Haisheng Sun is active in ShardingSphere community, hope your further interactions with the community! Thanks for your contributions. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [Event time] Do the two podling have interests to hold an event together?
Hi Sheng, +1 from me. Thanks for your suggestion, i think it is great to hold meetup together for two young communities. And i'd like to learn the details more. | | Juan Pan | | panj...@apache.org Juan Pan(Trista), Apache ShardingSphere | Signature is customized by Netease Mail Master On 09/13/2019 23:38, Sheng Wu wrote: Hi DolphinScheduler and ShardingSphere I am being told there is an event of new DolphinScheduler meetup happens soon, 2 months later, I think. Due to these two young communities, do you have interests to host the event together? And set up the talks to attract more potential contributors, which are required at both sides. Pure my personal suggestion, considering I am at both sides. Sheng -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: [Event time] Do the two podling have interests to hold an event together?
I'd like to attend. See u in Shanghai. | | Juan Pan | | panj...@apache.org Juan Pan(Trista), Apache ShardingSphere | Signature is customized by Netease Mail Master On 09/14/2019 09:08, Willem Jiang wrote: +1 for Apache podling projects working together. I'm quite interesting about these kind of event. BTW, we'd like to hold an Apache committer meetup in Shanghai next saturday (21st, Sep)[1]. Please let me know if you want to attend the meetup next week in Shanghai. [1]https://lists.apache.org/thread.html/5feb266773d655aff9deaf4db8d9dda72ff62a57e91ac97051bd7391@%3Cdev.servicecomb.apache.org%3E Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Sep 13, 2019 at 11:38 PM Sheng Wu wrote: > > Hi DolphinScheduler and ShardingSphere > > I am being told there is an event of new DolphinScheduler meetup happens > soon, 2 months later, I think. > > Due to these two young communities, do you have interests to host the event > together? And set up the talks to attract more potential contributors, > which are required at both sides. > > Pure my personal suggestion, considering I am at both sides. > > Sheng > -- > Sheng Wu > SkyWalking, Shardingsphere and Zipkin
Re:[DISCUSS] Set up new work flow for ShardingSphere
Hi Sheng, Thanks for your suggestions for ShardingSphere community. After scanning your suggestions, some of pains brought up really exist now, i think. Moreover, sorry, i did. After ShardingSphere entering into incubator, it is growing up quickly, but its growth of community can not keep the same pace with its features, for we put more attention on its functions and features. If we want to make ShardingSphere become better and better, the strength of community is essential. We should become more open-minded and give more trust and time to all the contributors and committers. How and why we need to build an active, open and diverse community is always puzzling me, not just as PPMC of ShardingSphere, but a person who has interest and enthusiasm of Apache community. I think those items seriously, and it is time to take a change, i think. I regret not being able to attend ApacheConn, and communicating with some one of you. :( I also want to listen to others’ voice of setting up a new workflow for ShardingSphere. Best wishes, Trista | | Juan Pan | | panj...@apache.org Juan Pan(Trista), Apache ShardingSphere | 签名由网易邮箱大师定制 On 09/13/2019 13:02，Sheng Wu wrote： Hi ShardingSphere With the one whole week at ApacheCon NA, I finally got time to take with Liang Zhang for a long time(several days) about the community and workflow of ShardingSphere community. First of all, due to our discussion for lower the bar, we have more committers and will have more PPMC. This is a good sign for our community growth. But, I also hope we could do much better than now. It is about the open source workflow, I am aware of that, today most features of ShardingSphere still come from the initial committer team inside JD.com. This is not a bad thing, but I want to involve more contributors in, engage with them, encourage them, and make them feel being a part of the core team, rather than following the contribution guidelines, or do outside supports. (For the core team, I mean the ShardingSphere could trust the workflow, a contributor out of jd.com, could do a core feature change with clear path and accepted by the PPMC) For making the community more open, I suggest 1. Make sure all changes must through pull request, no commit(especially for initial committer) lands on master/dev branch directly. 2. All pull request must be reviewed by at least one committer, and get approvement. Also don't get `request change` from the committer 3. Pull request should be goal clear, small enough to be reviewed. Today, too many huge PR with over 40+ files change, even 1k+ lines. Those are impossible to be reviewed. 4. Pull request should be `squash and merge`, rather than today, the commit log is not controlled, it becomes unreadable and unreasonable. 5. All pull request must have a clear description of why do this change and how. If necessary, provide the design document. ShardingSphere hopes to move fast, it totally makes sense to me, but all actions need to follow open source culture. Being open, understandable and trackable. Not just for codes, but for Issue, Pull Request, Design, Proposal, Review. The core goal of all these suggestions is, make new contributors, existing contributors, and committer out of jd.com team, understand what is happening in the community. One of the most talking about issue is, people are keeping waiting for core team to fix or do a new release, then only use it than contributing to the upstream. The root cause is the path of development is unclear from an individual out of the team. Please feedback about what do you feel about this, and do we want to do this. This is my most wanted change to ShardingSphere before the graduation, in order to make it possible to become an active, open, diversity community. You don't need to agree to me, this is just my feeling. I am away from code contributions to ShardingSphere for a long time, even before joining the incubator and open source happens. So, maybe there is some pain I am not aware of, please bring it up, and talk. Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 3]
Moreover, now i have already finished the modification of new APIs and new features for Encryption module. Considering the modification of APIs, does anyone think it is better to add this modification to our 4.0.0.RC2? - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年7月24日周三 下午5:36写道： > Hello ShardingSphere Community, > > This is a call for the 3rd round of discussion to release Apache > ShardingSphere (Incubating) version 4.0.0-RC2 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/1014b760ec22419441fae1c26df36f813cf3026d > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > GPG username: zhangyonglun > > Checklist: > https://shardingsphere.apache.org/community/en/contribute/release/ > > Anyone who is interested can do this acceptance test and discuss whether > this version should be released or not. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2 [ROUND 2]
+1 approve, the following items are ok: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. - Juan Pan (Trista) Apache ShardingSphere Zhang Yonglun 于2019年7月15日周一 下午4:11写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0-RC2 > > Release notes: > > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/5b4fa38b9237e8885c823dd92b4b42d1285c4c48 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > GPG username: zhangyonglun > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > -- > Zhang Yonglun > Apache ShardingSphere >
Re: 加入dev邮件列表
Please refer to Subscribe Guide, i.e. https://shardingsphere.apache.org/community/en/contribute/subscribe/ - Juan Pan (Trista) Apache ShardingSphere kys sion <1409915...@qq.com> 于2019年7月16日周二 下午4:21写道： > 您好啊 > > 请问我可以加入dev邮件列表吗?大家一起讨论让这个框架变成apache顶级项目:-) > > > >
Re: Suggest to add team page to our website
Hi Guangyuan and Haisheng, Can u provide your name and Apache ID? It will help lzs to add your information to our team page. Thanks. Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 22:34, Juan Pan wrote: Thanks for your contribution, now we have ShardingSphere team page, it is great. But There are Chinese words on this page, so can u modify them? Moreover, two new committers joined in us last week, so i think their names should be on the committer list on this page as well. Can you add our two new committers to this page? Thinks a lot :) Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 13:45, lzs wrote: We added this team introduce page at https://shardingsphere.apache.org/community/en/team/ | | lzs | | geo...@163.com | 签名由网易邮箱大师定制 On 9/18/2019 14:44，lzs wrote： We're willing to do this.Thank you for your suggestion. | | lzs | | geo...@163.com | On 9/18/2019 14:29，zhangli...@apache.org wrote： Great, we should add this page -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2019年9月18日周三 下午1:55写道： Hi ShardingSphere As we have invited some new committers to the project, I suddenly noticed, we don't have a team page, like this. http://skywalking.apache.org/team/ Listing our PPMC, mentors, committers and all other contributors. I think we should add that page. Any thoughts? Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: Suggest to add team page to our website
Thanks for your contribution, now we have ShardingSphere team page, it is great. But There are Chinese words on this page, so can u modify them? Moreover, two new committers joined in us last week, so i think their names should be on the committer list on this page as well. Can you add our two new committers to this page? Thinks a lot :) Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 13:45, lzs wrote: We added this team introduce page at https://shardingsphere.apache.org/community/en/team/ | | lzs | | geo...@163.com | 签名由网易邮箱大师定制 On 9/18/2019 14:44，lzs wrote： We're willing to do this.Thank you for your suggestion. | | lzs | | geo...@163.com | On 9/18/2019 14:29，zhangli...@apache.org wrote： Great, we should add this page -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2019年9月18日周三 下午1:55写道： Hi ShardingSphere As we have invited some new committers to the project, I suddenly noticed, we don't have a team page, like this. http://skywalking.apache.org/team/ Listing our PPMC, mentors, committers and all other contributors. I think we should add that page. Any thoughts? Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
[ANNOUNCE] New committer: Guangyuan Wang
TheProjectManagementCommittee(PMC)forApache ShardingSphere hasinvited Guangyuan Wang tobecomeacommitterandwearepleasedtoannouncethathehasaccepted. Guangyuan did a lot of contributions for ShardingSphere community, thanks. Hope you can become more active in future, and enjoy it.:) Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [Discuss] What does ShardingSphere 4.0.0's final API look like?
Making feature independent and use them in mixed mood? It sounds great, but challenging. It will take a lot of time to do, i think... Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/28/2019 18:44, Sheng Wu wrote: Does making this change in 5 make more sense? And we provide v4 unchanged for user convenient. Sheng zhangli...@apache.org 于2019年9月28日 周六下午6:15写道： > The scope of ShardingSphere keep expanding. Sharding is not the unique and > core feature for ShardingSphere anymore. > > So we plan to create pluggable infrastructure for database proxy and JDBC > driver which to let users run it without any additional function, just > transparent transmission. ShardingSphere can add more features into `EMPTY` > infrastructure, such as sharding, master-slave, encrypt, > distributed-transaction, orchestration and so on. > > The API may look like: ShardingDataSource, MasterSlaveDataSource, > EncryDataSource, DistributedTransactionDataSource and > OrchestrationDataSource, the yaml and other configuration methods should > change to this way too. > > Every features are independent and can be work together which using > composited and append-able way. We can provide SSDataSourceFacade to manage > how to use them together. > > This is one of the reason to why we do not release for 4.0.0 stable version > soon, we want more discuss to make decision to change API before 4.0.0 > stable version release. > > Any suggestions? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re:Gitbox/github notifications are not threaded
Hi Craig,
It is really troublesome. I hope Infra can take some actions as well.
From my experiences, some Email clients, e.g, foxmail for mac, can aggregate
emails into one thread by topic. Maybe you can have a try if you want.
Currently, i am using a Chinese email client helping me do that.
In addition, creating rules to filter emails is a another solution, but not
very practical i think. :)
Regard,
Trista
Juan Pan
panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere
On 09/26/2019 18:36，Craig Russell wrote：
Hi Infra,
Every message from gitbox to notifications@shardingsphere is sent individually
and clogs my in-box.
I'm wondering if there is some configuration that we can use to automatically
thread messages.
In this case, how can we change the github/gitbox notifications to
Subject: issue #3121: can't use HintManager.getInstance().setMasterRouteOnly()
The notification would apply to all references to this issue: create, modify,
comment, change of status, close. The subject could allow my mail reader to
thread all the messages on the subject issue. As it is, this issue has created
three individual messages sent to notificati...@shardingsphere.apache.org and
one thread that contains three replies, sent to
incubator-shardingsph...@noreply.github.com
I'm hoping that there is a technical solution to allow all of these messages to
be aggregated into one thread.
Thanks,
Craig
Begin forwarded message:
From: GitBox
Subject: [GitHub] [incubator-shardingsphere] maxiaoxian opened a new issue
#3121: can't use HintManager.getInstance().setMasterRouteOnly()
Date: September 26, 2019 at 1:41:06 AM PDT
To: notificati...@shardingsphere.apache.org
Reply-To: dev@shardingsphere.apache.org
maxiaoxian opened a new issue #3121: can't use
HintManager.getInstance().setMasterRouteOnly()
URL: https://github.com/apache/incubator-shardingsphere/issues/3121
## 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/apache/incubator-shardingsphere/issues).
- Read documentation: [ShardingSphere
Doc](https://shardingsphere.apache.org/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?
4.0.0-RC2
### Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
### Expected behavior
route to master
### Actual behavior
throw a exception : HintManagerHolder has previous value, please clear first.
### Reason analyze (If you can)
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
// 读写分离配置
MasterSlaveRuleConfiguration masterSlaveRuleConfig =
new MasterSlaveRuleConfiguration("ds", "fcWriteDataSource",
Arrays.asList("fcRead1DataSource", "fcRead2DataSource"));
Set masterSlaveRuleConfigurationSet = new
HashSet<>();
masterSlaveRuleConfigurationSet.add(masterSlaveRuleConfig);
ShardingRuleConfiguration shardingRuleConfig = new ShardingRuleConfiguration();
shardingRuleConfig.setMasterSlaveRuleConfigs(masterSlaveRuleConfigurationSet);
...
### 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:
us...@infra.apache.org
With regards,
Apache Git Services
Craig L Russell
c...@apache.org
Re:Support scenarios where multiple database table structures are different??
Hi, Sorry i can not get the point for your question. You can go through the documents on Sharding[1] to learn more. [1] https://shardingsphere.apache.org/document/current/en/features/ Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/27/2019 11:24?? wrote?? hello,Ask the following questions:My two database tables have completely different structures,Can you use it for this scenario?If not??Can I do that by rewriting something? I want to write different data sources using different logic??3Q very much
Re: Suggest to add team page to our website
You're right, Sheng. When a new committer appears, we should tell him or her to add his or her name to this page. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 23:50, Sheng Wu wrote: I think new committer should update their name by themselves, it should be easy PR. Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 sunbufu 于2019年9月21日周六 下午10:52写道： > Hi, My name is Haisheng Sun(孙海生), My apache id and github id is sunbufu. > > Thank you. > > > On 09/21/2019 22:38, Juan Pan wrote: > Hi Guangyuan and Haisheng, > > Can u provide your name and Apache ID? It will help lzs to add your > information to our team page. > > Thanks. > > Regards, > Trista > > > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > On 09/21/2019 22:34, Juan Pan wrote: > Thanks for your contribution, now we have ShardingSphere team page, it is > great. But There are Chinese words on this page, so can u modify them? > > > Moreover, two new committers joined in us last week, so i think their > names should be on the committer list on this page as well. > > > Can you add our two new committers to this page? > > > Thinks a lot :) > > > Regards, > Trista > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > On 09/21/2019 13:45, lzs wrote: > > > We added this team introduce page at > https://shardingsphere.apache.org/community/en/team/ > | | > lzs > | > | > geo...@163.com > | > 签名由网易邮箱大师定制 > On 9/18/2019 14:44，lzs wrote： > We're willing to do this.Thank you for your suggestion. > > > | | > lzs > | > | > geo...@163.com > | > > > On 9/18/2019 14:29，zhangli...@apache.org wrote： > Great, we should add this page > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2019年9月18日周三 下午1:55写道： > > Hi ShardingSphere > > As we have invited some new committers to the project, I suddenly noticed, > we don't have a team page, like this. http://skywalking.apache.org/team/ > Listing our PPMC, mentors, committers and all other contributors. > > I think we should add that page. Any thoughts? > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > >
Re: [DISCUSS] Towards ShardingSphere 4.0.0-RC3
Hi, All necessary issues have been solved, it is time to move into release stage. Any problems, please reply ASAP. Thanks. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/29/2019 17:37，Juan Pan wrote： Hi folks, ISSUE#3264[1] has been fixed, and another one[2] concerning Sharding-UI is a big change and not necessary, so how about pushing it to our next release? Moreover, i have checked all licenses of Sharding-UI, and some defects will be modified by Qingyang later. At current, IMP, no other issues might hinder our coming release. If has, please tell me ASAP. - [1] https://github.com/apache/incubator-shardingsphere/issues/3264 - [2] https://github.com/apache/incubator-shardingsphere/issues/3265 Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/23/2019 15:56，Juan Pan wrote： Oh, it seems to make some headway. The remaining issues are related to ShardingSphere-UI, waiting for their good news. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/22/2019 14:44，zhangli...@apache.org wrote： Hi, all issues of encrypt have solved. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Juan Pan 于2019年10月15日周二 下午7:11写道： Hi Sharding-UI is one highlight of this release, which we need to pay more attention on. Two of items would be necessary for us to double check. 1. Licenses I checked all the files, mainly inculding *.js, *.vue, *.png, *.java, and others of sharding-ui child project[1], which all have the appropriate and acceptable licenses. Considering it is the first and most important issue, i hope others, especially PPMC and committers could check them carefully as well. 2.Features After my testing, i believe it is basically available for community users. Qingyang Chen and Qi Wang are dealing with UI issues[2][3], which are excepted to be solved before release. Other than that, [4][5] are not pressing, so does anyone think it is better to put them off until our next release? Looking forward to your suggestions. Regards, Trista - [1] https://github.com/apache/incubator-shardingsphere/tree/dev/sharding-ui - [2] https://github.com/apache/incubator-shardingsphere/issues/3264 - [3] https://github.com/apache/incubator-shardingsphere/issues/3265 - [4] https://github.com/apache/incubator-shardingsphere/issues/3266 - [5] https://github.com/apache/incubator-shardingsphere/issues/3267 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/11/2019 11:23，Juan Pan wrote： Hi ShardingSphere community, It's been around 2 months since the last release. There's been many of PRs merged into our dev branch, and issues solved. So I'd like to use this as an opportunity to discuss our next release. What's more, i am happy to be release manager for our next release. Up to now, 48 issues tagged 4.0.0-RC3 milestone are closed (solved), and only 1 issues[1] is open which is expected to be fixed before 4.0.0-RC3. After reviewing those issues, the major items in our next release note would be: - Sharding-UI, a management background for ShardingSphere comes online. - Through Bugfix, data masking feature becomes much stable and applicable. - Sharding-core-optimizer module is refactored as sharding-core-preprocessor. - Not only SQLs from MySQL, PostgreSQL, SQLServer, Oracle, but any SQL92 Syntax can be parsed correctly and used in ShardingSphere. - Nacos, an easy-to-use dynamic configuration and service management platform can be used for Sharding-Orchestraion. Note: This release note is just a draft, anyone would add on to it. Currently, we are being preparing our next release, i appreciate it if you could pick up more items for next release note, or give your suggestions about this release. Welcome to our release discussion. Best wishes, Trista - [1] https://github.com/apache/incubator-shardingsphere/issues/3202 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: proxy
Please treat proxy as a regular DB to use it. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/03/2019 09:34, 张宇波 wrote: Dear How do I use springboot2 to connect to proxy
Re: About key generated by built-in snowflake algorithm(Sharding-JDBC)
Here is the introduction of snowflake[1]. [1] https://shardingsphere.apache.org/document/current/en/features/sharding/other-features/key-generator/ Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/31/2019 17:17, 梁维伟 wrote: Hi. I found that the result of (the key mod 4) always is 0/1, to me, it is wierd. What I expected is, the result should be 0/1/2/3, and the key should evenly distributed to all the sharded tables. I am new to ShardingSphere and the snowflake algorithm. Hope I can get some help from you. Thanks.
[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Hi everyone, With the help and effort of our community, the previous issues were fixed already. I am glad to invite everyone to move on to check and vote for our 4.0.0-RC3 ROUND 4. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
回复：订阅
Welcome, but please interact with community in English. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere 在2019年11月9日 16:47，刘江涛 写道： 订阅
Re:[Proposal] ShardingScaling donation
Wow, it seems a big feather for ShardingSphere, Hope donation goes well. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/9/2019 09:06，Sion Yang wrote： ## Abstract ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere Incubator[2]. It is designed to help users migrate data from origin database to ShardingSphere or scale out ShardingSphere data node more easily. It provides ability of migrant data, scaling out data nodes, etc. ## Proposal The goal of this proposal is to bring the existing ShardingScaling codebase and existing developers and community into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. This project started in Open Source on Github nearly 2 months. ShardingScaling is submitting this proposal to donate it to the Apache ShardingSphere Incubator under the Apache License, Version 2.0, in order to provide a visual management tool for ShardingSphere. These artifacts are currently available on GitHub at [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Background ShardingSphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. It is also widely adopted by many companies and organizations as a solution to process their massive amounts of data. But users have long lacked an easy-to-use way to migrate their data from origin database when they first started using ShardingSphere. Moreover, users have also lacked easy-to-use ways to expand data nodes when they use ShardingSphere for a while. So Wen OuYang created a scaling out component for ShardingSphere -- ShardingScaling. ## Current status After we pushed ShardingScaling in Github in an open source way, many users and developers have shown strong intentions to this. Yi Yang and ZongLei Dong have contributed many features and codes. Current, ShardingScaling has implemented basic data migration and scaling out data nodes feature. ## Core developer Wen OuYang is an experienced open source developer. Yi Yang is an experienced open source developer and ShardingSphere PPMC. ZongLei Dong is an experienced open source developer. ## Donation source Github repo: [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Source and Intellectual Property Submission Plan ShardingScaling was opened in Github on 18 Sep 2019. The project major contributors are Wen OuYang, Yi Yang and ZongLei Dong. Yi Yang is ShardingSphere's PPMC, ICLA are submitted. Wen OuYang and ZongLei Dong will sign ICLA after ShardingScaling is accepted into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. ## External Dependencies ### Apache 2.0 licenses - sharding-core-common 4.0.0-RC2: [https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) - snakeyaml 1.16: [https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default) - guava 18.0: [https://github.com/google/guava](https://github.com/google/guava) - netty-all 4.1.16.Final: [https://github.com/netty/netty](https://github.com/netty/netty) - commons-dbcp2 2.7.0: [https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp) - commons-cli 1.4: [https://github.com/apache/commons-cli](https://github.com/apache/commons-cli) - log4j 1.2.17: [https://github.com/apache/log4j](https://github.com/apache/log4j) - gson 2.8.6: [https://github.com/google/gson](https://github.com/google/gson) ### MIT licenses - slf4j-api 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - slf4j-log4j12 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - lombok 1.18.4: [https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok) - mockito-core 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) - mockito-inline 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) ### EPL 1.0 licenses - junit 4.12(scope test): [https://github.com/junit-team/junit4](https://github.com/junit-team/junit4) ### BSD License - hamcrest-library 1.3(scope test): [https://github.com/hamcrest/JavaHamcrest](https://github.com/hamcrest/JavaHamcrest) ## Required Resources ### Git Repositories: - [https://github.com/avalon566/sharding-scaling.git](https://github.com/avalon566/sharding-scaling.git) ## Initial Committers - 杨翊, Yi Yang, yan...@apache.org - 欧阳文, Wen OuYang - 董宗磊, ZongLei Dong - [1] [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling) - [2] [https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) -- Yi Yang(Sion) Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
Kind suggestion, got it. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 15:34，Sheng Wu wrote： Juan Try GitHub action first, it is faster, and doesn't require INFRA to setup. Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 Juan Pan 于2019年11月8日周五 下午3:09写道： Yep, the feedback from three of folks convinced us that our release can not install well on window platform. I will handle this new issue ASAP, therefore i am sorry to tell everyone vote for this release is delayed by a new issue, i.e across platform exception, and please wait for next ROUND. Thanks, Sheng, appveyor is exactly what we need. :) Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 14:41，Sheng Wu wrote： Look like an across platforms test fails. A suggestions, SkyWalking is using appveyor[1] to do Windows compiling check today. I think GitHub action also supports windows. We should choose one. Because SkyWalking used to face the same issue, some codes/tests are not working in Windows. [1] https://ci.appveyor.com/project/ApacheSoftwareFoundation/skywalking/ Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 王海涛 于2019年11月8日周五 下午2:36写道： Me too. In window 7, when I install the whole project , the same error was occurred. "Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.667 s <<< FAILURE! - in org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest) Time elapsed: 0.512 s <<< FAILURE!" -邮件原件- 发件人: Zhang Yonglun [mailto:zhangyong...@apache.org] 发送时间: 2019年11月8日 14:27 收件人: dev 主题: Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3 OS: Windows7 JDK: 1.8.0_162" mvn install or run the single test case MySQLTimeServiceTest can cause that failure. Juan Pan 于2019年11月8日周五 下午1:41写道： Hi Yonglun, Thanks for your feedback. Actually, the exception you mentioned didn’t happened to me, either i run `MySQLTimeServiceTest` separately or installed the whole project. Can you provide more details about your runtime environment or test procedure? Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 13:25，Zhang Yonglun wrote： I have installed the source code and a unit test failed: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.48 s <<< FAILURE! - in org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLT imeServiceTest) Time elapsed: 0.329 s <<< FAILURE! java.lang.AssertionError at org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest.assert InitDataSource(MySQLTimeServiceTest.java:48) [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] MySQLTimeServiceTest.assertInitDataSource:48 The root cause is the inputStream is not close then leading to a file close failure. The source code: 55th line of MySQLTimeService.java linzesi 于2019年11月8日周五 上午10:32写道： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. On 11/8/2019 10:24，董。<598363...@qq.com> wrote： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. Best wishes. --原始邮件-- 发件人:"Sion Yang"https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NO TES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-N OTES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md> < https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NO TES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md> ; The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0- RC3/ <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/> <https://dist
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
Hi Yonglun, Thanks for your feedback. Actually, the exception you mentioned didn’t happened to me, either i run `MySQLTimeServiceTest` separately or installed the whole project. Can you provide more details about your runtime environment or test procedure? Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 13:25，Zhang Yonglun wrote： I have installed the source code and a unit test failed: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.48 s <<< FAILURE! - in org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest) Time elapsed: 0.329 s <<< FAILURE! java.lang.AssertionError at org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest.assertInitDataSource(MySQLTimeServiceTest.java:48) [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] MySQLTimeServiceTest.assertInitDataSource:48 The root cause is the inputStream is not close then leading to a file close failure. The source code: 55th line of MySQLTimeService.java linzesi 于2019年11月8日周五 上午10:32写道： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. On 11/8/2019 10:24，董。<598363...@qq.com> wrote： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. Best wishes. --原始邮件-- 发件人:"Sion Yang"https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md> ; The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/> ; Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1026/org/apache/shardingsphere/ <https://repository.apache.org/content/repositories/orgapacheshardingsphere-1026/org/apache/shardingsphere/> ; Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ <https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/> ; Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/ea05bb0ff693bde04b7e0742386fdcb94b93bd60 <https://github.com/apache/incubator-shardingsphere/commit/ea05bb0ff693bde04b7e0742386fdcb94b93bd60> ; Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS> ; Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ <https://shardingsphere.apache.org/community/en/contribute/release/> ; The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
Yep, the feedback from three of folks convinced us that our release can not install well on window platform. I will handle this new issue ASAP, therefore i am sorry to tell everyone vote for this release is delayed by a new issue, i.e across platform exception, and please wait for next ROUND. Thanks, Sheng, appveyor is exactly what we need. :) Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 14:41，Sheng Wu wrote： Look like an across platforms test fails. A suggestions, SkyWalking is using appveyor[1] to do Windows compiling check today. I think GitHub action also supports windows. We should choose one. Because SkyWalking used to face the same issue, some codes/tests are not working in Windows. [1] https://ci.appveyor.com/project/ApacheSoftwareFoundation/skywalking/ Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 王海涛 于2019年11月8日周五 下午2:36写道： Me too. In window 7, when I install the whole project , the same error was occurred. "Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.667 s <<< FAILURE! - in org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest) Time elapsed: 0.512 s <<< FAILURE!" -邮件原件- 发件人: Zhang Yonglun [mailto:zhangyong...@apache.org] 发送时间: 2019年11月8日 14:27 收件人: dev 主题: Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3 OS: Windows7 JDK: 1.8.0_162" mvn install or run the single test case MySQLTimeServiceTest can cause that failure. Juan Pan 于2019年11月8日周五 下午1:41写道： Hi Yonglun, Thanks for your feedback. Actually, the exception you mentioned didn’t happened to me, either i run `MySQLTimeServiceTest` separately or installed the whole project. Can you provide more details about your runtime environment or test procedure? Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/8/2019 13:25，Zhang Yonglun wrote： I have installed the source code and a unit test failed: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.48 s <<< FAILURE! - in org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest [ERROR] assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLT imeServiceTest) Time elapsed: 0.329 s <<< FAILURE! java.lang.AssertionError at org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest.assert InitDataSource(MySQLTimeServiceTest.java:48) [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] MySQLTimeServiceTest.assertInitDataSource:48 The root cause is the inputStream is not close then leading to a file close failure. The source code: 55th line of MySQLTimeService.java linzesi 于2019年11月8日周五 上午10:32写道： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. On 11/8/2019 10:24，董。<598363...@qq.com> wrote： +1. checked list: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts 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] No compiled archives bundled in source archive. Best wishes. --原始邮件-- 发件人:"Sion Yang"https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NO TES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-N OTES.md> < https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NO TES.md ; The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0- RC3/ <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0 -RC3/> < https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0- RC3/ ; Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsp here-1026/org/apache/shardingsphere/ <https://repository.apache.org/content/repositories/orgapacheshardings phere-1026/org/apache/shardingsphere/> < https://repository.apache.org/content/repositories/orgapacheshardingsp here-1026/org/apache/shardingsphere/ ; Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ <https://g
[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
Hi ShardingSphere Community, I tried my best to solve the issues you raised, and went through the check list twice to avoid the confusion, but your review and vote on this release is important to us. Look forward to your attention and interaction. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1026/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/ea05bb0ff693bde04b7e0742386fdcb94b93bd60 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Hi Liang, I am appreciated your prompt issue fix. It seems building and signing the source code package have to be done one more time, so i am sorry to inform other mentors and PPMCs that this release vote is suspended, after all problem solved, i will start a new round of release vote called ROUND 2. Sorry for the inconvenience, please wait for Release vote round 2. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/31/2019 23:02, zhangli...@apache.org wrote: Release notes issue and source release issue have fixed at https://github.com/apache/incubator-shardingsphere/pull/3428 After merge, we can release for round 2. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2019年10月31日周四 下午7:17写道： > One addition question, > Why our changelog[1] so simple? The answer must be NO, and big NO. From the > GitHub release page[2], 499 commit difference between current and last > release, but get just 5 lines of the update? > I think that is not the purpose of the release changelog. > > [1] > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > [2] https://github.com/apache/incubator-shardingsphere/releases > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Sheng Wu 于2019年10月31日周四 下午4:41写道： > > > Pan Juan > > > > -1 (binding from PPMC or IPMC perspective) > > > > Sorry to say so. > > > > You are shipping all UI dependency in the src tar. Is this really > > necessary? And if so, what is the meaning of source release of UI? > > Do you notice, your source tar is nearly 200M? It is mostly caused by UI > > frontend. > > Another one, why all releases are not signed by your Apache mail? > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 > > > > > > Juan Pan 于2019年10月31日周四 上午7:56写道： > > > >> > >> > >> Hello ShardingSphere Community, > >> > >> > >> This is a call for vote to release Apache ShardingSphere (Incubating) > >> version 4.0.0-RC3 > >> > >> > >> Release notes: > >> > >> > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > >> > >> > >> The release candidates: > >> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ > >> > >> > >> Maven 2 staging repository: > >> > >> > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1023/org/apache/shardingsphere/ > >> > >> > >> Git tag for the release: > >> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ > >> > >> > >> Release Commit ID: > >> > >> > https://github.com/apache/incubator-shardingsphere/commit/6885dcfc281eec7691636875e298287a0147f176 > >> > >> > >> Keys to verify the Release Candidate: > >> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > >> > >> > >> Look at here for how to verify this release candidate: > >> https://shardingsphere.apache.org/community/en/contribute/release/ > >> > >> > >> The vote will be open for at least 72 hours or until necessary number of > >> votes are reached. > >> > >> > >> Please vote accordingly: > >> > >> > >> [ ] +1 approve > >> > >> > >> [ ] +0 no opinion > >> > >> [ ] -1 disapprove with the reason > >> > >> > >> Checklist for reference: > >> > >> > >> [ ] Download links are valid. > >> > >> > >> [ ] Checksums and PGP signatures are valid. > >> > >> > >> [ ] DISCLAIMER is included. > >> > >> > >> [ ] Source code artifacts have correct names matching the current > release. > >> > >> > >> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > >> > >> > >> [ ] All files have license headers if necessary. > >> > >> > >> [ ] No compiled archives bundled in source archive. > >> > >> > >> Best wishes, > >> Trista > >> > >> > >> Juan Pan > >> > >> > >> panj...@apache.org > >> Juan Pan(Trista), Apache ShardingSphere > >> > >> >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Hi Sheng, Thanks for your sound advices. I will review the problems you mentioned. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/31/2019 19:17, Sheng Wu wrote: One addition question, Why our changelog[1] so simple? The answer must be NO, and big NO. From the GitHub release page[2], 499 commit difference between current and last release, but get just 5 lines of the update? I think that is not the purpose of the release changelog. [1] https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md [2] https://github.com/apache/incubator-shardingsphere/releases Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 Sheng Wu 于2019年10月31日周四 下午4:41写道： > Pan Juan > > -1 (binding from PPMC or IPMC perspective) > > Sorry to say so. > > You are shipping all UI dependency in the src tar. Is this really > necessary? And if so, what is the meaning of source release of UI? > Do you notice, your source tar is nearly 200M? It is mostly caused by UI > frontend. > Another one, why all releases are not signed by your Apache mail? > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Juan Pan 于2019年10月31日周四 上午7:56写道： > >> >> >> Hello ShardingSphere Community, >> >> >> This is a call for vote to release Apache ShardingSphere (Incubating) >> version 4.0.0-RC3 >> >> >> Release notes: >> >> https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md >> >> >> The release candidates: >> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ >> >> >> Maven 2 staging repository: >> >> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1023/org/apache/shardingsphere/ >> >> >> Git tag for the release: >> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ >> >> >> Release Commit ID: >> >> https://github.com/apache/incubator-shardingsphere/commit/6885dcfc281eec7691636875e298287a0147f176 >> >> >> Keys to verify the Release Candidate: >> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS >> >> >> Look at here for how to verify this release candidate: >> https://shardingsphere.apache.org/community/en/contribute/release/ >> >> >> The vote will be open for at least 72 hours or until necessary number of >> votes are reached. >> >> >> Please vote accordingly: >> >> >> [ ] +1 approve >> >> >> [ ] +0 no opinion >> >> [ ] -1 disapprove with the reason >> >> >> Checklist for reference: >> >> >> [ ] Download links are valid. >> >> >> [ ] Checksums and PGP signatures are valid. >> >> >> [ ] DISCLAIMER is included. >> >> >> [ ] Source code artifacts have correct names matching the current release. >> >> >> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. >> >> >> [ ] All files have license headers if necessary. >> >> >> [ ] No compiled archives bundled in source archive. >> >> >> Best wishes, >> Trista >> >> >> Juan Pan >> >> >> panj...@apache.org >> Juan Pan(Trista), Apache ShardingSphere >> >>
Re: [Event time] Do the two podling have interests to hold an eventtogether?
Look forward to our co-meetup. +1 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/30/2019 11:36，zhangli...@apache.org wrote： +1, really happy to hold a co-meetup with dolphinscheduler together, the time is fine for us. We can talk about the details of topics further. -- Liang Zhang (John) Apache ShardingSphere & Dubbo William-GuoWei 于2019年10月30日周三 上午11:24写道： Both Dev on ShardingSphere and DolphineScheduler, How about we hold a co-meetup on Dec. 8 in Beijing? We can offer a meetup place and handle the free register ticket system and process. Our plan is just a whole day meetup (just like what we just did in Shanghai ) as former e-mail. How about your idea? Dolphin Scheduler (Incubator) William Guo Wei 原始邮件 发件人:guowei20mguowei...@outlook.com 收件人:dev...@shardingsphere.apache.org; dev@dolphinscheduler.apache.orgdev@ dolphinscheduler.apache.org 发送时间:2019年9月14日(周六) 17:57 主题:Re: [Event time] Do the two podling have interests to hold an eventtogether? Hi, We’d like to add more information aboutDolphin Scheduler meetup for discussion: Dolphin Scheduler Meetup agenda is planed to be formed by 3 part: I Morning Close Door Meeting for core developer and committer: Mainly discuss roadmap, new feature, bugs, and let core team get to know each other face to face… (For this part we can hold 2separated meeting for bothDolphinScheduler and ShardingSphere in two office at the same time) II Afternoon Open Door Meeting Just as Lidong said, we has a roughly plan for Shanghai Meetup, mainly talk to users, encourage them to become contributor and committer. (From this part, two meetup can combine together for moreinfluence) III Evening Salon Gathering Gathered the core developers, the speakers, the volunteers to know each other to activate the community in this city or area. (We can offer supper) This kind of meetup agenda(Part I,Part II, Part III) is validated for clickhouse community's 3-years running experience (According to the core team of CK, key users grew 3-4 times per year in China, till now more than 2000 enterprises is using CK. Core contributors in China was grown from 4 to more than 40). So this is a good form for open source meetup in China for now. We also suggest this agenda for both meetup. :) For nowDolphin Scheduler team has just confirmed the agenda for Shanghai Meetup on 2019，Oct, 26. And we are planning the second meetup on Nov, 10 in Beijing. The meetup time can be re-schedule according to the available time for both team. We are highly appreciated for the co-meetup, and we can offer the place and admin support. Dolphin Scheduler (Incubator) William Guo Wei 原始邮件 发件人:lidong dailidong@outlook.com 收件人:dev...@shardingsphere.apache.org; dev@dolphinscheduler.apache.orgdev@ dolphinscheduler.apache.org 发送时间:2019年9月14日(周六) 16:49 主题:Re: [Event time] Do the two podling have interests to hold an eventtogether? hi ： we are very willing to organize meetup together, we plan to hold two meetups in Shanghai and Beijing respectively. Here is the original plan meetup content of DolphinScheduler： “ Apache DolphinScheduler(incubator) User Meetup Date: 2019，Oct, 26 （2019年10月26日） Meetup Place: 3R20, No. 1107, Yuyuan Road, Changning District, Shanghai.（上海长宁区愚园路1107号创邑3R20） Agenda(议程): 1、Introduction/overview of DolphinScheduler (William-GuoWei). 2、DolphinScheduler internals, fairly technical: how DolphinScheduler works and so on (Zhanwei Qiao). 3、DolphinScheduler practice (拟定) 4、DolphinScheduler from Zero to One (拟定) 5、DolphinScheduler practice(拟定) 6、Recently released features and Roadmap (Lidong Dai) 7、Free discussion ” Currently, the meetup in Shanghai is recruiting lecturers. Perhaps the shardingsphere can also talk about several topics, which can be arranged together. haha. and We also plan to do a meetup in Beijing ，maybe in November. very glad to hear your opinions! --- Lidong Dai(DolphinScheduler) From: Sheng Wu wu.sheng.841...@gmail.com Sent: Friday, September 13, 2019 23:38 To: dev dev@shardingsphere.apache.org; d...@dolphinscheduler.apache.org d...@dolphinscheduler.apache.org Subject: [Event time] Do the two podling have interests to hold an event together? Hi DolphinScheduler and ShardingSphere I am being told there is an event of new DolphinScheduler meetup happens soon, 2 months later, I think. Due to these two young communities, do you have interests to host the event together? And set up the talks to attract more potential contributors, which are required at both sides. Pure my personal suggestion, considering I am at both sides. Sheng -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Hello ShardingSphere Community, This is a call for vote to release Apache ShardingSphere (Incubating) version 4.0.0-RC3 Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1023/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/6885dcfc281eec7691636875e298287a0147f176 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Hi Liang, Thanks for your kind reminders. What you mentioned has been fixed already, and IMP other mentors and PPMCs can continue to go through checklist and cast your vote. Sorry for the inconvenience. Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/31/2019 11:16，zhangli...@apache.org wrote： -1. The release's signature validation is fail, and please make sure the public KEYS has already import to [1]. Because of problem of signature validation, the status of close the maven release is failed. We need to release it again. [1] https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS -- Liang Zhang (John) Apache ShardingSphere & Dubbo zhangli...@apache.org 于2019年10月31日周四 上午11:05写道： Hi Zonglei Dong, You can not only reply+1. Before vote, please make sure you check all checklist and check on the item you checked. -- Liang Zhang (John) Apache ShardingSphere & Dubbo 董。 <598363...@qq.com> 于2019年10月31日周四 上午10:55写道： Look forward to ShardingSphere 4.0.0-RC3's release ! +1 Best wishes, Zonglei Dong --原始邮件------ 发件人:"Juan Pan"https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1023/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/6885dcfc281eec7691636875e298287a0147f176 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:Oracle configuration way start time is too long
I thought it is related to this one[1], and some of the contributors are fixing it. Please refer to those PR[2][3] for more details. [1] https://github.com/apache/incubator-shardingsphere/issues/3370 [2] https://github.com/apache/incubator-shardingsphere/pull/3516 [3] https://github.com/apache/incubator-shardingsphere/pull/2949 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/13/2019 18:38??<313992...@qq.com> wrote?? Hello?? Oracle configuration way start time is too long application.properties mysql configuration is not this kind of phenomenon Best?? ChengZheng
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Thanks Willem, Mentor' vote gives us more confidence. Although 72 hours passed, i would like to give other mentors and PPMCs more time to check. Please notice, next Monday in Beijing time is the deadline for this vote, i plead your check and vote, so that we can move ahead well in incubator voting. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/15/2019 10:28, Willem Jiang wrote: +1. (binding) Checked the release candidate of source and binary, the signatures and sha are OK. License and Notice file looks good to me. DISCLAIMER are in the kits. There is on binary files in the source release kit. The release kits has incubating in the name . Can build the binary from source kit. Checked staging repo. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Nov 11, 2019 at 6:40 PM Juan Pan wrote: > > Hi everyone, > > With the help and effort of our community, the previous issues were fixed > already. I am glad to invite everyone to move on to check and vote for our > 4.0.0-RC3 ROUND 4. > > Release notes: > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ > > Maven 2 staging repository: > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ > > Release Commit ID: > https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > > Best wishes, > Trista > > Juan Pan > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Thanks Craig, Waiting for your good or bad news. :) Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/18/2019 11:07，Craig Russell wrote： The problem was using --recv-keys with the KEYS file instead of the correct option --import wrote: Craig I think that may be caused by Juan used to regenerate the KEY from last round, right? Juan. I manually re-import in every time recheck your new round. That should be the reason. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan mailto:panj...@apache.org>> 于2019年11月18日周一 上午10:24写道： Hi Craig, Thanks for your reply and checking. Firstly, PGP PUBLIC KEY BLOCK of key ID C8ADAD3A which exists in `KEYS-FILE`[1] is correct. Secondly, key ID C8ADAD3A is not https://keyserver.pgp.com/ <https://keyserver.pgp.com/>, for there is no search result of my email, i.e panj...@apache.org <mailto:panj...@apache.org> . How about trying again to load keys from `KEYS-FILE`[1] ? Does anyone have idea about this issue? [1] https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS> Juan Pan panj...@apache.org <mailto:panj...@apache.org> Juan Pan(Trista), Apache ShardingSphere On 11/18/2019 09:02，Craig Russellmailto:apache@gmail.com>> wrote： I'm having trouble downloading the public key from the KEYS file. Does this KEYS file look right? Craig gpg --verify apache-shardingsphere-incubating-4.0.0-RC3-src.zip.asc gpg: assuming signed data in 'apache-shardingsphere-incubating-4.0.0-RC3-src.zip' gpg: Signature made Sun Nov 10 22:43:40 2019 PST using RSA key ID C8ADAD3A gpg: requesting key C8ADAD3A from https server keyserver.pgp.com <http://keyserver.pgp.com/> gpgkeys: no key data found for https://keyserver.pgp.com/ <https://keyserver.pgp.com/> gpg: no valid OpenPGP data found. gpg: Total number processed: 0 gpg: keyserver communications error: Not found gpg: keyserver communications error: Bad public key gpg: Can't check signature: No public key [MacBook-Pro-10:~/Downloads] clr% gpg --recv-keys < KEYS-2.txt [MacBook-Pro-10:~/Downloads] clr% cat KEYS-2.txt -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQINBFyR/WgBEACuVDJ2aFMc+GvOcvBA2CpgIM5AwWo3ES2WxcWuNoBHugZvtmQ0 Rhq0HigPcXD7F7J6Xh6PCs80EJxvbczQ16wi9597s1rzHbHFxueX8GKNtVyg7+NG /INzhDEEvaVE0ChxOGpSgZ8vnGZe5ERbLaW9e+onFvah5/poWiHKUJAlsvbgV4tB mmBCxIeTjdxHsdCFQYKpK1MNToTvSvgLZBIcNZ1OTTQMRFRDkoEfU0HR19naqHtW Mv87as4nxlnI4Du85tYdv6DbzL7qqFUNWUh+SROCdzReyWZiVrHzaP+zywtCnbjO /ddVo+lnMEesoFEdVnhRqCrtpYJuvSeIt+YkojCJtL+hooqgDcmXxlwRKOftY5ic ISXnriT8OE1cuUi8ghyl9YefZmjlyz+S7kCNJV81ZCi1/Uxan+yXxx4mxRn3fL61 hm51NPEghA+plWLLXylRFlRXYuwnUvOIMk1p5gx7Il3xfmtQ+cLC2dclN85viaaC avbMUQDEp1qGn6K/tKIZSF+CAViCCNg2ZgHxgimLNFkvK6TfUsvBNj/oPC18+H4+ l6+0Ub8TXb9XzRL2CcJ/I6uuifkABOuAPE2ObK2+K/yL5sQX2/qZuZotClHHWBqE idwChmt52ygbLwiOxQGcy6Rbv3A72WCZmbW+7f7i7iRE3x8w5HAjdDYbpwARAQAB tDhaaGFuZyBMaWFuZyAoYXBhY2hlIHJlbGVhc2UgYXdzKSA8emhhbmdsaWFuZ0Bh cGFjaGUub3JnPokCOAQTAQIAIgUCXJH9aAIbAwYLCQgHAwIGFQgCCQoLBBYCAwEC HgECF4AACgkQWfbgE3AOYGVdMg//W+DeSXux1j7uTfpgZ/NpBL/GDQPmxDVfredC xBuFtyGhX4HszPHXaSHtBZ69PcfjEPXM0Cs3+U+FR6Idkh4dorxwt+vcgD1PIInm 4wQaT6WGwbWboBuYpNqd833lAkykz0J881JtoGSPLA2llV/edOYlHOGTqV+Hbyym o136xlp8BcjhiKFK8j8a1ayUN7OOijTVFVZVpjLXw5zekqaPjYz7BOVvYeNu/27F +sUWszEGzrrC0TsM1pm48fGVClVy4x9UX9uMYjuWUL1sSepOfE8JMvDo2F4JyePw yS5KCqM5/hSSAh2NzlhgsBi997idNaKobCyQhbmCBgWW27KiOPMEmpk7hOCw5piT cVznTwlLAip4Jm7X2feEltlSWIrgPmuEliLdEPzTaNz6DLHaLRApvv1vmgcg42cn sckVq4zlXO7Ia3xP3H7gxxtM4i4MdkThbVF+iUd8wWmUOdA0iWg5eyrSoxfDJ2kE K68vZIxwKvEiXG7Eei2UNRka7/CzSj/rH8IIgcSV2bvxin/c/01/xf0dJj7vUSqF MNXkDkij2U2kX5r27bPZLQXqIqigga/ytqxWluvTIitXaiXgY2vEqWd/AMWYY07Y ZdX0fXoJIvLXndi4Y2M1YWCsB9T4gqzr2PP55c7/L2lrxa6gYK1Tg9vY20GhmdSh WbF24c65Ag0EXJH9aAEQANhKpqL/X6w32ud4/Y4COZtnfn7W8tDwNl5v37aez98w jm+WK+/QukKno0wlcSdAhKwg5vTJUiDqRse5Uo8auLVInFCHOyYknpE6bbiz/b8k NmXKGYsM3UGLDVuoBDXqH0ThFCEAiNCud+bcuOspIbLiYLWeI7732C3lbXUZJnsR XgybO4+SBYlB4lm9XfcdSFBss9mdLikqJsLAkB+2nRBZKcvamJqML3pjAr/Ps7Te gW7KvPedPHY/0CV1iqSTPB5KE1WelYm6hOmjL8MfnlXna8rgO/9Oh2D2pKydYbhs kY0JmURQuP/KnIiJt2th096JWftQAWZvmF7XYwBS82ZReQzqj/VGPZQgO1UBUR3v ZIHXzfm/fuA9UtT8BZCUJSgkDL3nkVuHWTVt+HkealBxqjGZj5Y+S6XXwhfNnqYA U0oADAoB3rqnmRyhP8A266NxA+2MkZ8YERHG9GY0FIa3Oe2U6AWXMfxB2NwGx/5X X4iKTSD2uvk5QFw8F7/F8aovh0D0kttCxGR8G6ZMY5HxMNSVyWiK257QNWkTl4xO xHmLUvECwKlpCwfzCL/N8A6xv4iux+PO8SzYRcKKx41wvS13AN0N3YFA8OPe0HNH cJM9xgQ1pksxAjxM4z/7xh4NU1v2XlpG5trbIYmDMHQR77bPpkXLe/c4xiTVU4dP ABEBAAGJAh8EGAECAAkFAlyR/WgCGwwACgkQWfbgE3AOYGUnNQ/8CAleXdzC8dkx 20Ph8vQvXn3poURZMftFeL8nnPp0Rx5KlBYe5Fvkldbv4lz7p6XTEDUfzy7fpZAC PjHVCuT4RUIsDMUPqjruhQuo7dFJqT9Pe692msk0PkqjvkXvW/TwfGNrGd6IYjpz /GY7xtTzxrnrzYk0E/s+E0Zr0nA7VZYwbQtVT2+jYn4TKYWJ/CXP87BoE05IrY2Q DEQn1zCapjdiyo/5UlyXKp4LrqQqoaFhNvGUa5teZ6wOwX/T/uM0ijLemvGq3mAd 8v1elh7gHnxQJ1qLGStXS/CrsR6JO9QE0/AfI18wLs7tDZoAL+tThmBy9CyfSAko F6YBKaCNc9zZyoutFAkBQClUZXRof2PkYMGKcNDeoHpA9o5AXJPA
Re: [Questionnaire] Questionnaire about Dolphin Scheduler Meetup inBeijing on December
Hi Sheng, We’d like to attend and jointly host this meet-up. Although some of rough schedule were talked in Shanghai, more detailed plan is not clear for us now. Did we miss anything important? Wechat or other channels are ok for us, besides can we get more details of current progress and future schedule? Very appreciated. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/18/2019 13:44，Sheng Wu wrote： As this is a co-meetup, what is the feedback from ShardingSphere? Sheng Wu 吴晟 Twitter, wusheng1108 William-GuoWei 于2019年11月18日周一 下午1:25写道： Not very good. Few people answer it, and we will push it to wechat group to gether more feedback. Now the meetup speaker is invited and we will make a register webpage for co-meetup Dolphin Scheduler (Incubator) PPMC Member William Guo Wei 原始邮件 发件人:Sheng wuwu.sheng.841...@gmail.com 收件人:dev...@dolphinscheduler.apache.org 发送时间:2019年11月15日(周五) 17:00 主题:Re: [Questionnaire] Questionnaire about Dolphin Scheduler Meetup inBeijing on December Any feedback from other channels about this? What is the plan now? Sheng Wu 吴晟 Twitter, wusheng1108 William-GuoWei william-guo...@qq.com 于2019年10月30日周三 上午11:12写道： Dear all developers and Users,We are planning a meetup in Beijing with ShardingShere in November in Beijing. Here is some question for your better experience:1. Which part do you hear most? (Mutiple choice) A. User Case B. Roadmap C. Internal architecture D. How to become a committer?2. Which kind of media do you like to learn the knowledge of Dolphin Scheduler (Mutiple choice) A. Blog and artical B. Recorded video C. Offine meetup , face to face D. Online meetup3. Which cities do you want to hold meetup beside Beijing in China? (Mutiple choice) A. Shanghai B. Shenzhen C. Nanjing D. Hangzhou E. Chengdu F. Xian G. US H. Europe I. Others4. How about co-meetup with other Apache project in China(One choice) A. Great! B. OK. C. Em… D. NoYou answser could like this: 1. AB 2. CD 3. A 4. AWe are glad to hear your feedback and also welcome to ask questions to us by e-mail. Dolphin Scheduler (Incubator) PPMC Member William Guo Wei
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Hi Craig, Very appreciated your checking and voting which help this release move ahead. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/18/2019 15:01，Craig Russell wrote： +1 I checked: [ x] Download links are valid. [x ] Checksums and PGP signatures are valid. [ x] DISCLAIMER is included. [ x] Source code artifacts have correct names matching the current release. [x ] Built mvn clean install from source Craig On Nov 11, 2019, at 2:40 AM, Juan Pan wrote: Hi everyone, With the help and effort of our community, the previous issues were fixed already. I am glad to invite everyone to move on to check and vote for our 4.0.0-RC3 ROUND 4. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md> The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/> Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ <https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/> Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ <https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/> Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d <https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d> Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS> Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ <https://shardingsphere.apache.org/community/en/contribute/release/> The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org <mailto:panj...@apache.org> Juan Pan(Trista), Apache ShardingSphere Craig L Russell c...@apache.org
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Hi Craig, Thanks for your reply and checking. Firstly, PGP PUBLIC KEY BLOCK of key ID C8ADAD3A which exists in `KEYS-FILE`[1] is correct. Secondly, key ID C8ADAD3A is not https://keyserver.pgp.com/, for there is no search result of my email, i.e panj...@apache.org . How about trying again to load keys from `KEYS-FILE`[1] ? Does anyone have idea about this issue? [1] https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/18/2019 09:02，Craig Russell wrote： I'm having trouble downloading the public key from the KEYS file. Does this KEYS file look right? Craig gpg --verify apache-shardingsphere-incubating-4.0.0-RC3-src.zip.asc gpg: assuming signed data in 'apache-shardingsphere-incubating-4.0.0-RC3-src.zip' gpg: Signature made Sun Nov 10 22:43:40 2019 PST using RSA key ID C8ADAD3A gpg: requesting key C8ADAD3A from https server keyserver.pgp.com gpgkeys: no key data found for https://keyserver.pgp.com/ gpg: no valid OpenPGP data found. gpg: Total number processed: 0 gpg: keyserver communications error: Not found gpg: keyserver communications error: Bad public key gpg: Can't check signature: No public key [MacBook-Pro-10:~/Downloads] clr% gpg --recv-keys < KEYS-2.txt [MacBook-Pro-10:~/Downloads] clr% cat KEYS-2.txt -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQINBFyR/WgBEACuVDJ2aFMc+GvOcvBA2CpgIM5AwWo3ES2WxcWuNoBHugZvtmQ0 Rhq0HigPcXD7F7J6Xh6PCs80EJxvbczQ16wi9597s1rzHbHFxueX8GKNtVyg7+NG /INzhDEEvaVE0ChxOGpSgZ8vnGZe5ERbLaW9e+onFvah5/poWiHKUJAlsvbgV4tB mmBCxIeTjdxHsdCFQYKpK1MNToTvSvgLZBIcNZ1OTTQMRFRDkoEfU0HR19naqHtW Mv87as4nxlnI4Du85tYdv6DbzL7qqFUNWUh+SROCdzReyWZiVrHzaP+zywtCnbjO /ddVo+lnMEesoFEdVnhRqCrtpYJuvSeIt+YkojCJtL+hooqgDcmXxlwRKOftY5ic ISXnriT8OE1cuUi8ghyl9YefZmjlyz+S7kCNJV81ZCi1/Uxan+yXxx4mxRn3fL61 hm51NPEghA+plWLLXylRFlRXYuwnUvOIMk1p5gx7Il3xfmtQ+cLC2dclN85viaaC avbMUQDEp1qGn6K/tKIZSF+CAViCCNg2ZgHxgimLNFkvK6TfUsvBNj/oPC18+H4+ l6+0Ub8TXb9XzRL2CcJ/I6uuifkABOuAPE2ObK2+K/yL5sQX2/qZuZotClHHWBqE idwChmt52ygbLwiOxQGcy6Rbv3A72WCZmbW+7f7i7iRE3x8w5HAjdDYbpwARAQAB tDhaaGFuZyBMaWFuZyAoYXBhY2hlIHJlbGVhc2UgYXdzKSA8emhhbmdsaWFuZ0Bh cGFjaGUub3JnPokCOAQTAQIAIgUCXJH9aAIbAwYLCQgHAwIGFQgCCQoLBBYCAwEC HgECF4AACgkQWfbgE3AOYGVdMg//W+DeSXux1j7uTfpgZ/NpBL/GDQPmxDVfredC xBuFtyGhX4HszPHXaSHtBZ69PcfjEPXM0Cs3+U+FR6Idkh4dorxwt+vcgD1PIInm 4wQaT6WGwbWboBuYpNqd833lAkykz0J881JtoGSPLA2llV/edOYlHOGTqV+Hbyym o136xlp8BcjhiKFK8j8a1ayUN7OOijTVFVZVpjLXw5zekqaPjYz7BOVvYeNu/27F +sUWszEGzrrC0TsM1pm48fGVClVy4x9UX9uMYjuWUL1sSepOfE8JMvDo2F4JyePw yS5KCqM5/hSSAh2NzlhgsBi997idNaKobCyQhbmCBgWW27KiOPMEmpk7hOCw5piT cVznTwlLAip4Jm7X2feEltlSWIrgPmuEliLdEPzTaNz6DLHaLRApvv1vmgcg42cn sckVq4zlXO7Ia3xP3H7gxxtM4i4MdkThbVF+iUd8wWmUOdA0iWg5eyrSoxfDJ2kE K68vZIxwKvEiXG7Eei2UNRka7/CzSj/rH8IIgcSV2bvxin/c/01/xf0dJj7vUSqF MNXkDkij2U2kX5r27bPZLQXqIqigga/ytqxWluvTIitXaiXgY2vEqWd/AMWYY07Y ZdX0fXoJIvLXndi4Y2M1YWCsB9T4gqzr2PP55c7/L2lrxa6gYK1Tg9vY20GhmdSh WbF24c65Ag0EXJH9aAEQANhKpqL/X6w32ud4/Y4COZtnfn7W8tDwNl5v37aez98w jm+WK+/QukKno0wlcSdAhKwg5vTJUiDqRse5Uo8auLVInFCHOyYknpE6bbiz/b8k NmXKGYsM3UGLDVuoBDXqH0ThFCEAiNCud+bcuOspIbLiYLWeI7732C3lbXUZJnsR XgybO4+SBYlB4lm9XfcdSFBss9mdLikqJsLAkB+2nRBZKcvamJqML3pjAr/Ps7Te gW7KvPedPHY/0CV1iqSTPB5KE1WelYm6hOmjL8MfnlXna8rgO/9Oh2D2pKydYbhs kY0JmURQuP/KnIiJt2th096JWftQAWZvmF7XYwBS82ZReQzqj/VGPZQgO1UBUR3v ZIHXzfm/fuA9UtT8BZCUJSgkDL3nkVuHWTVt+HkealBxqjGZj5Y+S6XXwhfNnqYA U0oADAoB3rqnmRyhP8A266NxA+2MkZ8YERHG9GY0FIa3Oe2U6AWXMfxB2NwGx/5X X4iKTSD2uvk5QFw8F7/F8aovh0D0kttCxGR8G6ZMY5HxMNSVyWiK257QNWkTl4xO xHmLUvECwKlpCwfzCL/N8A6xv4iux+PO8SzYRcKKx41wvS13AN0N3YFA8OPe0HNH cJM9xgQ1pksxAjxM4z/7xh4NU1v2XlpG5trbIYmDMHQR77bPpkXLe/c4xiTVU4dP ABEBAAGJAh8EGAECAAkFAlyR/WgCGwwACgkQWfbgE3AOYGUnNQ/8CAleXdzC8dkx 20Ph8vQvXn3poURZMftFeL8nnPp0Rx5KlBYe5Fvkldbv4lz7p6XTEDUfzy7fpZAC PjHVCuT4RUIsDMUPqjruhQuo7dFJqT9Pe692msk0PkqjvkXvW/TwfGNrGd6IYjpz /GY7xtTzxrnrzYk0E/s+E0Zr0nA7VZYwbQtVT2+jYn4TKYWJ/CXP87BoE05IrY2Q DEQn1zCapjdiyo/5UlyXKp4LrqQqoaFhNvGUa5teZ6wOwX/T/uM0ijLemvGq3mAd 8v1elh7gHnxQJ1qLGStXS/CrsR6JO9QE0/AfI18wLs7tDZoAL+tThmBy9CyfSAko F6YBKaCNc9zZyoutFAkBQClUZXRof2PkYMGKcNDeoHpA9o5AXJPAO9iOkU+JRb+a j4YRM1iGiG83wLIhvuI8d3HiczaRKp2LWu7MOK+0FfOdfswzXl1UHLphSWcKlbwJ mDkhcE/7k84Fd2EHSfravtUcfpcauL2+2f+H3x3FQqYxYbP9yQusmB8Bq4x+Ukcs YSzWnELUjHxXlI+fCgOOc7DF90ffPlg8LVo24O436HF1Cyl7izX2pIWnENmLVh8H 33W6DBs1QGh293phN+CBYInxYjn8X12RuCOvQeFAJVXlJSK58SLSKvf81DWmAbu/ iX3+DXBQeKKl6cZZOAKjhVtG7X0SDjE= =89x7 -END PGP PUBLIC KEY BLOCK- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQINBFyFx0kBEADHUr5MvL2qZKxcIeN31OoMhbOipk131IFzp+k4wob1GwGTai+t n18pEkWKXACWTdBgk+QggAb78uh0Z1+otlB3x6W9IoFf4rxc6xAKKlveYEF2lnaw r/hvIzNYcleR3watbnMls0zHTQm0VsF7ZeDZ2UAWBZFy5+O9UZMgTvSiSOumNrFp pq6u8mrC/8p+WbcqYZLuB5t5aHkMuWgLFEpnlbCU5vlOohl0XNyvg8iu/uR+KT7P kzUu8KtUgyYcC0vywlBeCe3FE7vQ3MEg5VkiNd7jArkDmiWmQQyJbeMbLXHUXQhN uXk/UvIZ9QUKiW50A+iSCdiHPVxxpJS5bRflvdTiUMmW8bnnPqnw1ELoHcVDKNra aykuOQtLJxMpRfHgtzA1Si9bkXeDvRNmUyqbmXcq/UjHfGjg6UOKJvXrHQ20f
Re:Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4 DataConversionException: Cannot determine value type from string 'NO'
Yes, as Li said, you image is not attached well. But more important point here is that this thread is for voting and checking release 4.0.0-RC3. Did those exceptions throw up when you went through check list? If your issue is about how to upgrade your program with the latest version of ShardingSphere, please open a new thread or topic. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/12/2019 17:37??Brian You got this<2714510...@qq.com> wrote?? Hi Juan, The cause is in TableMetaDataLoader.class. That's my analysis result, Please confirm it. -- -- ??????: "Juan Pan"; : 2019??11??12??(??) 1:03 ??: "dev@shardingsphere.apache.org"; : "dev"; : Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4 Hi Brian, This thread is for checking and voting for Release 4.0.0-RC3, you need to go through the check list and cast your vote. Notice: 4.0.0-RC3 has not been released until now. Did the exception you mentioned happen when you did checking? Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/12/2019 10:09??Brian You got this<2714510...@qq.com> wrote?? Hi: Thanks foryour reply. But I got a exception When Iswitched to4.0.0-RC3. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthIndicatorRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory method 'healthIndicatorRegistry' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.actuate.autoconfigure.jdbc.DataSourceHealthIndicatorAutoConfiguration': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'encryptDataSource' defined in class path resource [org/apache/shardingsphere/shardingjdbc/spring/boot/SpringBootConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.sql.DataSource]: Factory method 'encryptDataSource' threw exception; nested exception is java.sql.SQLDataException: Cannot determine value type from string 'NO' at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:627) at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:607) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1305) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1144) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515) at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:277) at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1247) at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1167) at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:857) at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:760) ... 105 common frames omitted Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory method 'healthIndicatorRegistry' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependenc
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
Yep, there are many issues fixed and features developed, some of which are trivial. Based on that, we’d like to summarize, thus it seems to `ignore` some change log, does anyone have some suggestions? Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/13/2019 11:38，zhangli...@apache.org wrote： The release notes has all change logs in milestone[1] which in the end of each release version, because change logs in milestone is too big, so we just summary some important issues. [1] https://github.com/apache/incubator-shardingsphere/milestone/8 -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2019年11月13日周三 上午9:19写道： +1 The issues mentioned before have been fixed. asc sign checked and based on apache mail. NOTICE, LICENSE, and DISCLAIMER exist. sha512 is there compiling works A tiny issue, The changelog seems to ignore many fixes and code changes. Such as bugfix #3401[1] never shows up in a changelog. The principle of changelog contents seems not clear to me. This is not a release block, but I feel it should be discussed. [1] https://github.com/apache/incubator-shardingsphere/pull/3401 Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 Juan Pan 于2019年11月11日周一 下午6:40写道： Hi everyone, With the help and effort of our community, the previous issues were fixed already. I am glad to invite everyone to move on to check and vote for our 4.0.0-RC3 ROUND 4. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
[ANNOUNCE] New committer: Zhiyi Yan
Hi folks, TheProjectManagementCommittee(PMC)forApache ShardingSphere hasinvited Zhiyi Yan tobecomeacommitterandwearepleasedtoannouncethat she hasaccepted. Welcome Zhiyi and Look forward to continued interaction. please join me in congratulating Zhiyi. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:[VOTE] Accept ShardingScaling Donation ROUND2
Sound great +1 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/13/2019 09:57，Sion Yang wrote： Dear Apache ShardingSphere Incubator Community , With the help and effort of our community, the previous issues were fixed already. I am glad to invite everyone to start a vote on accepting ShardingScaling into the Apache Incubator as ShardingSphere's sub-project ROUND 2. Discussion in ML https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%3Cdev.shardingsphere.apache.org%3E https://lists.apache.org/thread.html/a1ef4b44abe8f11273983e69c12becda12302aee852f7569c99a34d1@%3Cdev.shardingsphere.apache.org%3E Please accept the ShardingScaling podling into the Apache Incubator. The proposal can be found at https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal Here is the text of it: ## Abstract ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere Incubator[2]. It is designed to help users migrate data from origin database to ShardingSphere or scale out ShardingSphere data node more easily. It provides ability of migrant data, scaling out data nodes, etc. ## Proposal The goal of this proposal is to bring the existing ShardingScaling codebase and existing developers and community into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. This project started in Open Source on Github nearly 2 months. ShardingScaling is submitting this proposal to donate it to the Apache ShardingSphere Incubator under the Apache License, Version 2.0, in order to provide a visual management tool for ShardingSphere. These artifacts are currently available on GitHub at [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Background ShardingSphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. It is also widely adopted by many companies and organizations as a solution to process their massive amounts of data. But users have long lacked an easy-to-use way to migrate their data from origin database when they first started using ShardingSphere. Moreover, users have also lacked easy-to-use ways to expand data nodes when they use ShardingSphere for a while. So Wen OuYang created a scaling out component for ShardingSphere -- ShardingScaling. ## Current status After we pushed ShardingScaling in Github in an open source way, many users and developers have shown strong intentions to this. Yi Yang, ZongLei Dong and ssxlulu have contributed many features and codes. Current, ShardingScaling has implemented basic data migration and scaling out data nodes feature. ## Core developer Wen OuYang is an experienced open source developer. Yi Yang is an experienced open source developer and ShardingSphere PPMC. ## Donation source Github repo: [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Source and Intellectual Property Submission Plan ShardingScaling was opened in Github on 18 Sep 2019. The project major contributors are Wen OuYang, Yi Yang. Yi Yang is ShardingSphere's PPMC, ICLA are submitted. Wen OuYang will sign ICLA and become Apache committer if vote be accepted after ShardingScaling is accepted into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. ## External Dependencies ### Apache 2.0 licenses - sharding-core-common 4.0.0-RC2: [https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) - snakeyaml 1.16: [https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default) - guava 18.0: [https://github.com/google/guava](https://github.com/google/guava) - netty-all 4.1.16.Final: [https://github.com/netty/netty](https://github.com/netty/netty) - commons-dbcp2 2.7.0: [https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp) - commons-cli 1.4: [https://github.com/apache/commons-cli](https://github.com/apache/commons-cli) - log4j 1.2.17: [https://github.com/apache/log4j](https://github.com/apache/log4j) - gson 2.8.6: [https://github.com/google/gson](https://github.com/google/gson) ### MIT licenses - slf4j-api 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - slf4j-log4j12 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - lombok 1.18.4: [https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok) - mockito-core 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) - mockito-inline 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) ### EPL 1.0 licenses - junit 4.12(scope test): [https://github.com/junit-team/junit4](https://github.com/junit-team/junit4
[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 2
Hi ShardingSphere Community, All issues in ROUND 1 have been fixed already, we now kindly request ShardingSphere community to review and vote on this release, i.e Apache ShardingSphere (Incubating) version 4.0.0-RC3. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1024/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/bbeedec206d2e7317159cccff9ce4cafa90f598a Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 2
Thanks, i will review it now. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/5/2019 17:32，Sheng Wu wrote： Sorry, still -1. The source code compiles failures. [*ERROR*] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile *(default-compile)* on project sharding-orchestration-core: *Compilation failure*: Compilation failure: [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/AuthenticationChangedListener.java:[24,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/service/StateService.java:[21,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/service/StateService.java:[32,19] 找不到符号 [*ERROR*] 符号: 类 StateNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.state.service.StateService [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/service/ConfigurationService.java:[39,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/service/ConfigurationService.java:[57,19] 找不到符号 [*ERROR*] 符号: 类 ConfigurationNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.config.service.ConfigurationService [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/SchemaChangedListener.java:[40,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/PropertiesChangedListener.java:[22,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/SchemaChangedListener.java:[63,19] 找不到符号 [*ERROR*] 符号: 类 ConfigurationNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.config.listener.SchemaChangedListener [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/InstanceStateChangedListener.java:[23,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/InstanceStateChangedListener.java:[24,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/DataSourceStateChangedListener.java:[22,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/DataSourceStateChangedListener.java:[23,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/DataSourceStateChangedListener.java:[37,19] 找不到符号
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 2
Hi, sorry for that. `node` package is excluded to solve the problem of oversized source package in ROUND 1. Therefore you got that exception. `source-distribution.xml` will be modified again for this correction. Consequently, I am sorry to tell the community that ROUND 3 is coming soon, please wait for it and continue to check and review. Thanks for Sheng's prompt reply to avoid worse result, i will try my best to make ROUND 3 go well. :) Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/5/2019 17:32，Sheng Wu wrote： Sorry, still -1. The source code compiles failures. [*ERROR*] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile *(default-compile)* on project sharding-orchestration-core: *Compilation failure*: Compilation failure: [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/AuthenticationChangedListener.java:[24,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/service/StateService.java:[21,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/service/StateService.java:[32,19] 找不到符号 [*ERROR*] 符号: 类 StateNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.state.service.StateService [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/service/ConfigurationService.java:[39,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/service/ConfigurationService.java:[57,19] 找不到符号 [*ERROR*] 符号: 类 ConfigurationNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.config.service.ConfigurationService [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/SchemaChangedListener.java:[40,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/PropertiesChangedListener.java:[22,77] 程序包org.apache.shardingsphere.orchestration.internal.registry.config.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/config/listener/SchemaChangedListener.java:[63,19] 找不到符号 [*ERROR*] 符号: 类 ConfigurationNode [*ERROR*] 位置: 类 org.apache.shardingsphere.orchestration.internal.registry.config.listener.SchemaChangedListener [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/InstanceStateChangedListener.java:[23,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/InstanceStateChangedListener.java:[24,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/registry/state/listener/DataSourceStateChangedListener.java:[22,76] 程序包org.apache.shardingsphere.orchestration.internal.registry.state.node不存在 [*ERROR*] /Users/wusheng/Downloads/apache-shardingsphere-incubating-4.0.0-RC3-src-release/sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere
Re:Fwd: [RESULT] [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Thanks Craig, I got your point, and this suggestion would be appended to our release guide later to help the following release managers. [1] https://shardingsphere.apache.org/community/en/contribute/release/ Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/22/2019 01:57，Craig Russell wrote： Hi Juan, I'd like to suggest a small change in the voting reporting process for releases. When the release manager tallies the dev@ vote, everyone who votes should be named. When the vote is forwarded to incubator general, the dev@ votes should also be forwarded. So in the incubator vote, the binding and non-binding votes from the dev@ vote should have been included. And in this announcement, my vote from the dev@ list should have been included in the result. Regards, Craig Begin forwarded message: From: "Juan Pan" Subject: [RESULT] [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 Date: November 21, 2019 at 4:53:22 AM PST To: "gene...@incubator.apache.org" Reply-To: gene...@incubator.apache.org Hi All, Release vote for Release Apache ShardingSphere (Incubating) 4.0.0-RC3 has PASSED and closed now. The results are as follows: [4] +1 Binded votes - Jean-Baptiste Onofré - Justin Mclean - Gosling Von - Sheng Wu [ 0 ] +0 Binded Votes [ 0 ] -1 Binded Votes Thanks for everyone, especially for IPMCs who checked and voted to help this version released. I will process to publish the release andsend ANNOUNCE later. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere Craig L Russell c...@apache.org
Re: Podling Shardingsphere Report Reminder - December 2019
Hi Justin, Thanks for your feedback and suggestion. You’re right, it seems not a proper expression, and maybe it is a better one that "Individuals from different companies and communities provided some patches to feed back ShardingSphere community”. We will pay more attention on it and try our best to make our community diverse and active. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/3/2019 05:07，Justin Mclean wrote： Hi, Looking at the report again I noticed this "some companies has already provided patches to feedback the community.". You might want to reword that, companies don't provide patches people do, people contribute to the project as individuals not who they work for. While it nice to know the project is being used by many companies, care needs to taken to make sure it's recognised that individuals are making the contributions. Thanks, Justin
Re: Discussion of pluggable platform of ShardingSphere
Agree with Liang, Maybe there is no feature benefit apparently, however we make its architecture become…a structured plaza with many rooms. Consequently, more contributors could fill in specific implements for those rooms with less harms to this plaza, i.e our project. Oh, i have a great imagination, don’t you think so? :) Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/9/2019 14:13，Nicholas wrote： Hi guys, What features will be planned in pluggable platform? And how to assign features splits from sharding-core? Based on user concept，what does user benefit from this pluggable platform? Thanks, Nicholas Jiang On 2019/12/09 05:29:47, "zhangli...@apache.org" wrote: Hi, ShardingSphere community, More and more features are added into ShardingSphere now, as you know, the scope of ShardingSphere is no longer for sharding only. There are more and more features related with sharding, such as distributed transaction, distributed orchestration, observability and so on; and there are couple of features did not relate with sharding obviously, for example: encrypt, shadow data source, SQL audit and so on. I'd like to discuss about establishing a pluggable platform of ShardingSphere. The proposal of pluggable platform is decoupling all features and technical implementations, the benefits are: 1. Flexible for add new feature. 2. Reduce the negative effects if problem occur on one feature. 3. Provide a platform to make more contributors work together without interact on each other. I plan split all features from sharding-core first, and then use SPI to introduce features into the pluggable platform(same thing with sharding, sharding can be remove from main process too). The pluggable platform is a blank JDBC and database protocol finally, and provide assist technical features such as SQL parser and SQL rewrite. Any advice? -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re: 4.0.0 stable version release plan
Finishing Acceptance-test framework is better, but not a block, IMO. As Liang said, a detailed schedule is necessary to makes everyone review all the tasks and their time costs. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/8/2019 22:50，Sheng Wu wrote： zhaojun 于2019年12月8日周日 下午9:50写道： Acceptance-test framework will make release workflow more smoothly. We will spend a lot of time (maybe months) to verify the function manually on every release time. Several months? Are you saying ShardingSphere will have no stable release in over 1.5 years? Are PPMC serious sure about this? Sheng Wu 吴晟 Twitter, wusheng1108 In fact, we could not release a version ASAP now. -- Zhao Jun (cherrylzhao) Apache ShardingSphere & ServiceComb On Dec 7, 2019, at 6:54 PM, Sheng Wu wrote: Make sense to me. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2019年12月7日周六 下午6:47写道： How about get the result of performance test at last? It is a good way to confirm there are no performance issue for the stable version. It should be ok soon, maybe next week. We can list a scheduler for the detail of performance test. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Juan Pan 于2019年12月7日周六 下午6:09写道： Hi Sheng, Thanks for your clarification, i get your point. Juan Pan panj...@apache.org Juan Pan(T-rista), Apache ShardingSphere On 12/7/2019 17:59，Sheng Wu wrote： Hi Actually, my point is those two even not source release :) Those are test frameworks. The user would feel they exist. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2019年12月7日周六 下午5:50写道： Hi Sheng and Liang, I totally agree to release a stable version for community ASAP, however i am curious about the release note and the intending date of it. Is there any new for this release, or just hot bugfix? As Sheng said, ISSUE[1] and [2] seems not block, so Liang, would you like to include them into this release? What’s the estimated time of completion? Thanks, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/7/2019 17:23，Sheng Wu wrote： zhangli...@apache.org 于2019年12月7日周六 下午5:18写道： Hi, ShardingSphere community, I'd like to talk about the release plan of 4.0.0 stable version. As you know, after enter Apache incubator, ShardingSphere had released 3 RC versions during the past year. The features are stable more and more, it is the time to talk about task details before 4.0.0 release. I just list some tasks that I knew, please add if I missing something: 1. Performance test display. The current result is in [1], we still need to do some adjust to make it better. 2. Acceptance test. The repo is in [2], we still need docker and shell to make it run automatically. And we will transfer it to apache repo[3] soon. I think these two are not blocks for the stable release. :) 3. Remain bugs hot fix. I don't find any high priority bug to be fixed now. If no high priority bug, I think this is a good time to do the official release now. ShardingSphere has no stable release in the whole of 2019. We should do this ASAP. What do other PPMC think? Sheng Wu 吴晟 Twitter, wusheng1108 Any other tasks missing here? [1] https://shardingsphere.apache.org/benchmark/#/overview [2] https://github.com/OpenSharding/shardingsphere-acceptance-test [3] https://github.com/apache/incubator-shardingsphere-acceptance-test -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re:Sharding-Proxy-mysql8.0.18-BUG
Hi English communication is prerequisite. Could you use 4.0.0-RC3 to test? Juan Pan (Trista) Senior DBA & PPMC of Apache ShardingSphere(Incubating) email: panj...@apache.org On 12/12/2019 16:05，文光临 wrote： 您好！ Sharding-Proxy 连接 mysql8.0.18 报错，读取元数据出错。 报错信息如下（配置和报错日志 在附件。多谢了） [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 30 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 1 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 5 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 30 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 127.0.1.1.tm [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 8640 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 1 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099 [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false [INFO ] 15:36:31.679 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 30 [INFO ] 15:36:31.680 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery... [INFO ] 15:36:31.701 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource [INFO ] 15:36:31.720 [main] c.a.d.xa.XATransactionalResource - resource-2-ds_1: refreshed XAResource Exception in thread "main" java.sql.SQLDataException: Cannot determine value type from string 'NO' at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:114) at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97) at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89) at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63) at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73) at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:96) at com.mysql.cj.jdbc.result.ResultSetImpl.getObject(ResultSetImpl.java:1382) at com.mysql.cj.jdbc.result.ResultSetImpl.getBoolean(ResultSetImpl.java:663) at com.mysql.cj.jdbc.result.ResultSetImpl.getBoolean(ResultSetImpl.java:669) at org.apache.shardingsphere.core.execute.metadata.TableMetaDataLoader.getColumnMetaDataList(TableMetaDataLoader.java:169) at org.apache.shardingsphere.core.execute.metadata.TableMetaDataLoader.createTableMetaData(TableMetaDataLoader.java:147) at org.apache.shardingsphere.core.execute.metadata.TableMetaDataLoader.load(TableMetaDataLoader.java:112) at org.apache.shardingsphere.core.execute.metadata.TableMetaDataLoader.access$100(TableMetaDataLoader.java:56) at org.apache.shardingsphere.core.execute.metadata.TableMetaDataLoader$1.execute(TableMetaDataLoader.java:101) at org.apache.shardingsphere.core.execute.ShardingExecuteEngine.syncGroupExecute(ShardingExecuteEngine.java:125) at org.apache.shardingsphere.core.execute.ShardingExecuteEngine.parallelExecute(ShardingExecuteE
Re:[Discuss] sharding-orchestration module reconstruction
Hi Yuan, I’d like to join in discussion, however i have no idea about what is going now, could you draft a workflow or schedule to give us a basic understanding about it. Based on that, maybe others could give some great suggestion or idea. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 14:28，guangyuan wang wrote： Hello everyone I'd like to reconstruct the sharding-orchestration module. So far as, we have develop a new sharding-orchestration-center module and sharding-orchestration-core-new module. I'd like to use them to replace the old ones. But It's really huge engineering. So I'd like to discuss the workflow of the reconstruction. Do you have any good suggestions?
Re:Using mybatis, the parameter is list and null pointer error is reported
Hi thanks for your detailed log. What’s your sharding rule? Looking at log, i found the actual SQL is same with the logic one, and there is no difference. Does table named `cv_task_mark_user ` is a sharding table? Have you ever referred to sharding-examples[1], which provides several configuration examples for different situations ? - [1] https://github.com/apache/incubator-shardingsphere-example Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/6/2019 17:47，xu wrote： Using mybatis, the parameter is list to report null pointer error. The version of mybatis is 3.2.0，the version of sharding is 4.0.0-RC3 ,The specific log is as follows： Fetched SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@9d7c7b] from current transaction ooo Using Connection [org.apache.shardingsphere.shardingjdbc.jdbc.core.connection.ShardingConnection@121f239] ==> Preparing: INSERT INTO cv_task_mark_user ( team_id , task_id , pin, creator, created, deleted ) VALUES (?,?,?,?,now(),0) ==> Parameters: 122(Long), 2446(Long), xukaiwei1(String), xukaiwei1(String) [2019-12-06 17:39:12] INFO ShardingSphere-SQL(http-nio-8088-exec-8); :Rule Type: sharding [2019-12-06 17:39:12] INFO ShardingSphere-SQL(http-nio-8088-exec-8); :Logic SQL: INSERT INTO cv_task_mark_user ( team_id , task_id , pin, creator, created, deleted ) VALUES (?,?,?,?,now(),0) [2019-12-06 17:39:12] INFO ShardingSphere-SQL(http-nio-8088-exec-8); :SQLStatement: InsertSQLStatementContext(super=CommonSQLStatementContext(sqlStatement=org.apache.shardingsphere.core.parse.sql.statement.dml.InsertStatement@115c689, tablesContext=TablesContext(tables=[Table(name=cv_task_mark_user, alias=Optional.absent())], schema=Optional.absent())), columnNames=[team_id, task_id, pin, creator, created, deleted], insertValueContexts=[InsertValueContext(parametersCount=4, valueExpressions=[ParameterMarkerExpressionSegment(startIndex=180, stopIndex=180, parameterMarkerIndex=0), ParameterMarkerExpressionSegment(startIndex=182, stopIndex=182, parameterMarkerIndex=1), ParameterMarkerExpressionSegment(startIndex=184, stopIndex=184, parameterMarkerIndex=2), ParameterMarkerExpressionSegment(startIndex=186, stopIndex=186, parameterMarkerIndex=3), CommonExpressionSegment(startIndex=188, stopIndex=192, text=now()), LiteralExpressionSegment(startIndex=194, stopIndex=194, literals=0)], parameters=[122, 2446, xukaiwei1, xukaiwei1])]) [2019-12-06 17:39:12] INFO ShardingSphere-SQL(http-nio-8088-exec-8); :Actual SQL: cv_dataSource ::: INSERT INTO cv_task_mark_user ( team_id , task_id , pin, creator, created, deleted ) VALUES (?, ?, ?, ?, now(), 0) ::: [122, 2446, xukaiwei1, xukaiwei1] Releasing transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@9d7c7b] Transaction synchronization rolling back SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@9d7c7b] Transaction synchronization closing SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@9d7c7b] [2019-12-06 17:39:19] DEBUG org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver(http-nio-8088-exec-8); :Resolving exception from handler [public net.sf.json.JSONObject com.jd.bdp.cv.web.controller.CvTaskController.save(com.jd.bdp.cv.domain.CvUser,com.jd.bdp.cv.domain.CvTask,org.springframework.web.multipart.MultipartFile,javax.servlet.http.HttpServletRequest) throws java.lang.Exception]: org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.exceptions.PersistenceException: ### Error querying database. Cause: java.lang.NullPointerException ### The error may exist in URL [jar:file:/D:/workspace_bdp/bdp_cv_inter/cv-web/target/cv-web/WEB-INF/lib/cv-dao-1.0-SNAPSHOT.jar!/com/jd/bdp/cv/dao/CvTaskMarkUser.xml] ### The error may involve com.jd.bdp.cv.dao.CvTaskMarkUserDao.insertByMarkPins-Inline ### The error occurred while setting parameters ### SQL: INSERT INTO cv_task_mark_user ( team_id , task_id , pin, creator, created, deleted ) VALUES(?,?,?,?,now(),0) ### Cause: java.lang.NullPointerException [2019-12-06 17:39:19] DEBUG org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver(http-nio-8088-exec-8); :Resolving exception from handler [public net.sf.json.JSONObject com.jd.bdp.cv.web.controller.CvTaskController.save(com.jd.bdp.cv.domain.CvUser,com.jd.bdp.cv.domain.CvTask,org.springframework.web.multipart.MultipartFile,javax.servlet.http.HttpServletRequest) throws java.lang.Exception]: org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.exceptions.PersistenceException: ### Error querying database. Cause: java.lang.NullPointerException ### The error may exist in URL [jar:file:/D:/workspace_bdp/bdp_cv_inter/cv-web/target/cv-web/WEB-INF/lib/cv-dao-1.0-SNAPSHOT.jar!/com/jd/bdp/cv/dao/CvTaskMarkUser.xml] ### The err
回复：sharding在springboot2的环境下，对jpa与mybatis同时生效
Hi English for communication only. Beside, i have no clear idea about your problem, can you give more details of your issue? Thanks Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere 在2019年12月7日 16:29，石 写道： 你好，问题如标题； 我的项目为了开发便捷，同时使用了mybatis注解方式与Jpa注解方式；使用的是默认的一个datasource（hikarCPi）, 现在引入pom,添加sharding的配置文件内容后 io.shardingsphere sharding-jdbc-spring-boot-starter 3.1.0 只有mybatis相关的数据库操作生效
Re: 4.0.0 stable version release plan
Hi Sheng, Thanks for your clarification, i get your point. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/7/2019 17:59，Sheng Wu wrote： Hi Actually, my point is those two even not source release :) Those are test frameworks. The user would feel they exist. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2019年12月7日周六 下午5:50写道： Hi Sheng and Liang, I totally agree to release a stable version for community ASAP, however i am curious about the release note and the intending date of it. Is there any new for this release, or just hot bugfix? As Sheng said, ISSUE[1] and [2] seems not block, so Liang, would you like to include them into this release? What’s the estimated time of completion? Thanks, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/7/2019 17:23，Sheng Wu wrote： zhangli...@apache.org 于2019年12月7日周六 下午5:18写道： Hi, ShardingSphere community, I'd like to talk about the release plan of 4.0.0 stable version. As you know, after enter Apache incubator, ShardingSphere had released 3 RC versions during the past year. The features are stable more and more, it is the time to talk about task details before 4.0.0 release. I just list some tasks that I knew, please add if I missing something: 1. Performance test display. The current result is in [1], we still need to do some adjust to make it better. 2. Acceptance test. The repo is in [2], we still need docker and shell to make it run automatically. And we will transfer it to apache repo[3] soon. I think these two are not blocks for the stable release. :) 3. Remain bugs hot fix. I don't find any high priority bug to be fixed now. If no high priority bug, I think this is a good time to do the official release now. ShardingSphere has no stable release in the whole of 2019. We should do this ASAP. What do other PPMC think? Sheng Wu 吴晟 Twitter, wusheng1108 Any other tasks missing here? [1] https://shardingsphere.apache.org/benchmark/#/overview [2] https://github.com/OpenSharding/shardingsphere-acceptance-test [3] https://github.com/apache/incubator-shardingsphere-acceptance-test -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re: 4.0.0 stable version release plan
Hi Sheng and Liang, I totally agree to release a stable version for community ASAP, however i am curious about the release note and the intending date of it. Is there any new for this release, or just hot bugfix? As Sheng said, ISSUE[1] and [2] seems not block, so Liang, would you like to include them into this release? What’s the estimated time of completion? Thanks, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/7/2019 17:23，Sheng Wu wrote： zhangli...@apache.org 于2019年12月7日周六 下午5:18写道： Hi, ShardingSphere community, I'd like to talk about the release plan of 4.0.0 stable version. As you know, after enter Apache incubator, ShardingSphere had released 3 RC versions during the past year. The features are stable more and more, it is the time to talk about task details before 4.0.0 release. I just list some tasks that I knew, please add if I missing something: 1. Performance test display. The current result is in [1], we still need to do some adjust to make it better. 2. Acceptance test. The repo is in [2], we still need docker and shell to make it run automatically. And we will transfer it to apache repo[3] soon. I think these two are not blocks for the stable release. :) 3. Remain bugs hot fix. I don't find any high priority bug to be fixed now. If no high priority bug, I think this is a good time to do the official release now. ShardingSphere has no stable release in the whole of 2019. We should do this ASAP. What do other PPMC think? Sheng Wu 吴晟 Twitter, wusheng1108 Any other tasks missing here? [1] https://shardingsphere.apache.org/benchmark/#/overview [2] https://github.com/OpenSharding/shardingsphere-acceptance-test [3] https://github.com/apache/incubator-shardingsphere-acceptance-test -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re: [Discuss] sharding-orchestration module reconstruction
Take it easy. And FYI, maybe we could modify the internal of orchestration without changing API of orchestration. When the refactoring of orchestration finishes, API changes and behavior changes of callers comes. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 20:32，sunbufu wrote： I think this maybe not so hard, we can do this like follow. 1. Remove the old modules. 2. Rename the new modules. 3. Modify references we can easy find. 4.Follow the error lead. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/11/2019 16:14，guangyuan wang wrote： The modifications in sharding-orchestration are: 1. The RegistryCenter is changed to split into 3 interfaces: ConfigCenter, Registry Center, DistributedLockManagement. 2. The related implementation class is changed and initialization is changed. These changes mean the sharding-orchestration module will be totally changed. So we create two modules in the sharding-orchestration to replace old modules in the sharding-orchestration. And now I wanna make the replacing. But it's huge task, because many classes of the sharding-orchestration are called by other modules. I'd like to discuss the workflow of the replacing, to make this action safely be done without any unit test failure. Juan Pan 于2019年12月11日周三 下午4:02写道： Hi Yuan, I’d like to join in discussion, however i have no idea about what is going now, could you draft a workflow or schedule to give us a basic understanding about it. Based on that, maybe others could give some great suggestion or idea. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 14:28，guangyuan wang wrote： Hello everyone I'd like to reconstruct the sharding-orchestration module. So far as, we have develop a new sharding-orchestration-center module and sharding-orchestration-core-new module. I'd like to use them to replace the old ones. But It's really huge engineering. So I'd like to discuss the workflow of the reconstruction. Do you have any good suggestions?
Re: [Congrats] Happy to see the diversity is being established.
Yep, attending Apache Conn, and communicating with Justin, Craig and you made a positive effect on the growth of ShardingSphere community. Thanks for your help. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/21/2019 08:57，Willem Jiang wrote： Yeah, it's import for us to grow a diversity community for the long live of the project. I also want to mention the traffic[1] of the dev mail list last month looks good to me too. Last month, there are 91 emails sent by 31 people, divided into 27 topics. Keep up the good work, we are heading to the TLP :) [1]https://lists.apache.org/list.html?dev@shardingsphere.apache.org Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Oct 20, 2019 at 11:10 PM Sheng Wu wrote: Hi As I am keeping watching the diversity of the community, I notice the chemical reactions are happening. I am keeping my eye on this page, https://github.com/apache/incubator-shardingsphere/pulse/monthly 29 authors have pushed 95 commits to dev and 95 commits to all branches. On dev, 651 files have changed and there have been 18,014 additions and 11,105 deletions. This seems super healthy to me. In this mail, I just want to simply say, congrats. And hope this keeps going. I think we are moving to be at the TLP level. Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
??????sharding-JDBC????springdataJPA??????????
ShardingSphere examples[1] will help you, i think. Again, please in english for communication. Thanks. - [1] https://github.com/apache/incubator-shardingsphere-example Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere ??2019??10??19?? 11:09<314794...@qq.com> ?? ?? ------ ??: ""
Re: Draft of Podling Maturity Assessment for ShardingSphere
ShardingSphere has been in Apache incubator for nearly a year, we grew up quickly with mentors’ and community’s help. I thought ShardingSphere basically meets the requirement of maturity assessment, but not enough.Hope its community become more active. :) Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/16/2019 00:24，zhangli...@apache.org wrote： QU30 has finished now, we can check on page[1]. https://shardingsphere.apache.org/community/en/security/ -- Liang Zhang (John) Apache ShardingSphere & Dubbo zhangli...@apache.org 于2019年10月15日周二 下午6:43写道： Hi ShardingSphere community, I just do Podling Maturity Assessment for ShardingSphere, it is a draft only. The proposal of this email is we consensus for the assessment first, and then I will post it into the GitHub repository, and to guide the community more and more maturity. The Apache Project Maturity Model is in [1] Here is the Podling Maturity Assessment for ShardingSphere, please check and discuss. __ Code CD10 The project produces Open Source software, for distribution to the public at no charge. YES. The project source code is licensed under the Apache License, version 2.0. CD20 The project's code is easily discoverable and publicly accessible. YES. The website(https://shardingsphere.apache.org/) includes 'SCM' link can access GitHub. CD30 The code can be built in a reproducible way using widely available standard tools. YES. The build uses Apache Maven and Jenkins as the continuous integration tool, please find the `How to Build`(in GitHub's README.md) for more information. CD40 The full history of the project's code is available via a source code control system, in a way that allows any released version to be recreated. YES. The project use git to manage source code, example, document and website, all releases are tagged. CD50 The provenance of each line of code is established via the source code control system, in a reliable way based on strong authentication of the committer. When third-party contributions are committed, commit messages provide reliable information about the code provenance. YES. The project uses the GitHub which managed by Apache Infra, ensuring provenance of each line of code to a committer. The third-party contributions are accepted in accordance with the code submit guide only. Licenses and Copyright LC10 The code is released under the Apache License, version 2.0. YES. LICENSE file are in GitHub repository ( https://github.com/apache/incubator-shardingsphere/blob/dev/LICENSE). LC20 Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. YES. The list of dependencies for binary release ( https://github.com/apache/incubator-shardingsphere/tree/dev/sharding-distribution/sharding-proxy-distribution/src/main/release-docs/licenses) and ui( https://github.com/apache/incubator-shardingsphere/tree/dev/sharding-distribution/sharding-ui-distribution/src/main/release-docs/licenses) have been reviewed to contain compatible licenses only. LC30 The libraries mentioned in LC20 are available as Open Source software. YES. See LC20's dependencies list. LC40 Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they are allowed to commit and how they need to identify code that is not their own. YES. All committers have iCLAs on file before they have apache account. LC50 The copyright ownership of everything that the project produces is clearly defined and documented. YES. All files in the source code have appropriate headers and checked by Apache rat plugin when build. Releases RE10 Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. YES. Source release are distributed via dist.apache.org( https://dist.apache.org/repos/dist/release/incubator/shardingsphere/) and linked from website( https://shardingsphere.apache.org/document/current/en/downloads/). RE20 Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. YES. All releases have been voted by ShardingSphere community and incubator, which have least 3 (P)PMC votes. RE30 Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. YES. All releases are signed, and the KEYS file( https://dist.apache.org/repos/dist/release/incubator/shardingsphere/KEYS) is provided on dist.apache.org. RE40 Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. YES. Convenience binaries are distributed via Maven Central Repository( https://mvnrepository.com/artifact/org.apache.shardingsphere), DockerHub( https://hub.docker.com/r/apache/sharding-proxy/tags) and d
Re: [DISCUSS] Towards ShardingSphere 4.0.0-RC3
Ok, i will be part of that. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/14/2019 15:10，zhangli...@apache.org wrote： I just doing test framework on rewrite[1] and already find some problems. We need pass all test cases before release. [1] https://github.com/apache/incubator-shardingsphere/issues/1548 -- Liang Zhang (John) Apache ShardingSphere & Dubbo Juan Pan 于2019年10月14日周一 上午11:48写道： BTW, you can refer to this PR[1] to learn more about new registry center-Apollo. :) - [1] https://github.com/apache/incubator-shardingsphere/pull/3239 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/14/2019 11:29，Juan Pan wrote： Hi A good news for our community is that Apollo, a reliable configuration management system can be used as a registry center in Sharding-Orchestration. Thanks for dongzl’s contribution, which will be included in our next release, i.e, 4.0.0-RC3. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/11/2019 11:23，Juan Pan wrote： Hi ShardingSphere community, It's been around 2 months since the last release. There's been many of PRs merged into our dev branch, and issues solved. So I'd like to use this as an opportunity to discuss our next release. What's more, i am happy to be release manager for our next release. Up to now, 48 issues tagged 4.0.0-RC3 milestone are closed (solved), and only 1 issues[1] is open which is expected to be fixed before 4.0.0-RC3. After reviewing those issues, the major items in our next release note would be: - Sharding-UI, a management background for ShardingSphere comes online. - Through Bugfix, data masking feature becomes much stable and applicable. - Sharding-core-optimizer module is refactored as sharding-core-preprocessor. - Not only SQLs from MySQL, PostgreSQL, SQLServer, Oracle, but any SQL92 Syntax can be parsed correctly and used in ShardingSphere. - Nacos, an easy-to-use dynamic configuration and service management platform can be used for Sharding-Orchestraion. Note: This release note is just a draft, anyone would add on to it. Currently, we are being preparing our next release, i appreciate it if you could pick up more items for next release note, or give your suggestions about this release. Welcome to our release discussion. Best wishes, Trista - [1] https://github.com/apache/incubator-shardingsphere/issues/3202 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:[DISCUSS] Towards ShardingSphere 4.0.0-RC3
Hi Sharding-UI is one highlight of this release, which we need to pay more attention on. Two of items would be necessary for us to double check. 1. Licenses I checked all the files, mainly inculding *.js, *.vue, *.png, *.java, and others of sharding-ui child project[1], which all have the appropriate and acceptable licenses. Considering it is the first and most important issue, i hope others, especially PPMC and committers could check them carefully as well. 2.Features After my testing, i believe it is basically available for community users. Qingyang Chen and Qi Wang are dealing with UI issues[2][3], which are excepted to be solved before release. Other than that, [4][5] are not pressing, so does anyone think it is better to put them off until our next release? Looking forward to your suggestions. Regards, Trista - [1] https://github.com/apache/incubator-shardingsphere/tree/dev/sharding-ui - [2] https://github.com/apache/incubator-shardingsphere/issues/3264 - [3] https://github.com/apache/incubator-shardingsphere/issues/3265 - [4] https://github.com/apache/incubator-shardingsphere/issues/3266 - [5] https://github.com/apache/incubator-shardingsphere/issues/3267 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/11/2019 11:23，Juan Pan wrote： Hi ShardingSphere community, It's been around 2 months since the last release. There's been many of PRs merged into our dev branch, and issues solved. So I'd like to use this as an opportunity to discuss our next release. What's more, i am happy to be release manager for our next release. Up to now, 48 issues tagged 4.0.0-RC3 milestone are closed (solved), and only 1 issues[1] is open which is expected to be fixed before 4.0.0-RC3. After reviewing those issues, the major items in our next release note would be: - Sharding-UI, a management background for ShardingSphere comes online. - Through Bugfix, data masking feature becomes much stable and applicable. - Sharding-core-optimizer module is refactored as sharding-core-preprocessor. - Not only SQLs from MySQL, PostgreSQL, SQLServer, Oracle, but any SQL92 Syntax can be parsed correctly and used in ShardingSphere. - Nacos, an easy-to-use dynamic configuration and service management platform can be used for Sharding-Orchestraion. Note: This release note is just a draft, anyone would add on to it. Currently, we are being preparing our next release, i appreciate it if you could pick up more items for next release note, or give your suggestions about this release. Welcome to our release discussion. Best wishes, Trista - [1] https://github.com/apache/incubator-shardingsphere/issues/3202 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [DISCUSS] Towards ShardingSphere 4.0.0-RC3
Hi folks, ISSUE#3264[1] has been fixed, and another one[2] concerning Sharding-UI is a big change and not necessary, so how about pushing it to our next release? Moreover, i have checked all licenses of Sharding-UI, and some defects will be modified by Qingyang later. At current, IMP, no other issues might hinder our coming release. If has, please tell me ASAP. - [1] https://github.com/apache/incubator-shardingsphere/issues/3264 - [2] https://github.com/apache/incubator-shardingsphere/issues/3265 Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/23/2019 15:56，Juan Pan wrote： Oh, it seems to make some headway. The remaining issues are related to ShardingSphere-UI, waiting for their good news. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/22/2019 14:44，zhangli...@apache.org wrote： Hi, all issues of encrypt have solved. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Juan Pan 于2019年10月15日周二 下午7:11写道： Hi Sharding-UI is one highlight of this release, which we need to pay more attention on. Two of items would be necessary for us to double check. 1. Licenses I checked all the files, mainly inculding *.js, *.vue, *.png, *.java, and others of sharding-ui child project[1], which all have the appropriate and acceptable licenses. Considering it is the first and most important issue, i hope others, especially PPMC and committers could check them carefully as well. 2.Features After my testing, i believe it is basically available for community users. Qingyang Chen and Qi Wang are dealing with UI issues[2][3], which are excepted to be solved before release. Other than that, [4][5] are not pressing, so does anyone think it is better to put them off until our next release? Looking forward to your suggestions. Regards, Trista - [1] https://github.com/apache/incubator-shardingsphere/tree/dev/sharding-ui - [2] https://github.com/apache/incubator-shardingsphere/issues/3264 - [3] https://github.com/apache/incubator-shardingsphere/issues/3265 - [4] https://github.com/apache/incubator-shardingsphere/issues/3266 - [5] https://github.com/apache/incubator-shardingsphere/issues/3267 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 10/11/2019 11:23，Juan Pan wrote： Hi ShardingSphere community, It's been around 2 months since the last release. There's been many of PRs merged into our dev branch, and issues solved. So I'd like to use this as an opportunity to discuss our next release. What's more, i am happy to be release manager for our next release. Up to now, 48 issues tagged 4.0.0-RC3 milestone are closed (solved), and only 1 issues[1] is open which is expected to be fixed before 4.0.0-RC3. After reviewing those issues, the major items in our next release note would be: - Sharding-UI, a management background for ShardingSphere comes online. - Through Bugfix, data masking feature becomes much stable and applicable. - Sharding-core-optimizer module is refactored as sharding-core-preprocessor. - Not only SQLs from MySQL, PostgreSQL, SQLServer, Oracle, but any SQL92 Syntax can be parsed correctly and used in ShardingSphere. - Nacos, an easy-to-use dynamic configuration and service management platform can be used for Sharding-Orchestraion. Note: This release note is just a draft, anyone would add on to it. Currently, we are being preparing our next release, i appreciate it if you could pick up more items for next release note, or give your suggestions about this release. Welcome to our release discussion. Best wishes, Trista - [1] https://github.com/apache/incubator-shardingsphere/issues/3202 Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:How does shardingsphere handle queries about information_shema ?
Hi did you use MySQL?? Please add item of `defaultDataSource` to your shardingRule configuration. When ShardingSphere doesn??t find any sharding table named `column`, it will send query to default datasource, i.e `innformation_schema`. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/20/2019 13:47??sushixiang wrote?? How does shardingsphere handle queries about information_shema ? Now, when I query from tables in information_schema, exception like "Table 'information.column' doesn't exist"will cause. So, does shardingsphere deal with the information_shema query scene??
Re:How does shardingsphere handle queries about information_shema ?
Exactly true. ShardingSphere only returns the metadata of actual table currently. We expect someone who is interested in it can do some contributions to make it better. :) Welcome. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/20/2019 14:11??sushixiang wrote?? Thanks for replying. But, there are also some problems.If my sql is "select * from information_schema.columns where table_name = 't_order'", shardingsphere will not response the correct result while the t_oder is a sharding table, because the physical table name may be t_order_0. It may be not elegant for using the physical table name. --Original------ From:"Juan Pan"
Re:How does shardingsphere handle queries about information_shema ?
Sure, a further discussion, as the first step, is necessary. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/20/2019 14:23??sushixiang wrote?? Thank you, And I think this feature may need a further disscussion. --Original-- From:"Juan Pan"
[DISCUSS] Co-meetup of Apache DolphinScheduler and Apache ShardingSphere
Hi DolphinScheduler community and ShardingSphere community, This email is to give notice that our co-meetup is coming! After the further discussion between two communities yesterday, here is the draft schedule: Meetup date: 8th December Meetup place: Uncertain location in Beijing, depends on the number of participants and DS community will provide it later Meetup schedule: - Closed-table meetings respectively from 10AM-12AM (ahead of 10AM is ok). - Round-table meetings together from 2PM-6PM. - Dinner party after meeting over. This is the first time for two of Apache communities to host a co-meetup, i am glad to see our co-meetup run well. It is a draft, any problems, please follow this thread. Other than that, don’t be shy, please say hello to everyone. :) Welcome any question and suggestion here, but most of all, welcome you to come and join! Notice: For who receives the same email: Sorry, a new thread for further discussion is better, IMO. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
