Re: [DISCUSS] Plan to drop support for JDK 8
Personally, I don't have concern about compiling JDK version. This is a more dev relative thing. Zheng Feng 于2023年1月13日 周五21:31写道： > OK, I can understand. Back to resolve antlr4 upgrading issue [1], I'm > trying to figure it out since this only impact generating some parsers at > build time. The only way is to use JDK11 to build the shardingsphere but > still target for JDK 8 by using > "8" [2]. So is it feasible > for the community to accept this solution? Just changing enforcer-plugin to > requireJavaVersion 11? > > [1] https://github.com/apache/shardingsphere/pull/20008 > [2] > > https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-release.html > > Sheng Wu 于2023年1月13日周五 21:16写道： > > > Zheng Feng 于2023年1月13日周五 21:04写道： > > > > > > I'm not pushing to drop JDK 8 now but I wonder if it is possible to > > > maintain two LTS versions of shardingsphere. e.g. 5.x for JDK 8 and 6.x > > for > > > JDK 11 above. > > > > New features end, from my understanding, this is the end of support of > > JDK8. > > Maintaining mode is only about high-priority bug fixing, and no > > enhancement, no new feature, no performance improvement. > > With time, many things can't cherry-pick back to the JDK 8. > > > > > > > > Sheng Wu 于2023年1月13日周五 20:58写道： > > > > > > > From my side, only if there are key improvements for JDK 11, we are > > > > worth taking that risk. Especially, whether these things are JDK 11 > > > > compiling only. > > > > SkyWalking chose to use ShardingSphere proxy, but we discussed the > > > > possibilities of ShardingJDBC, but if we made that choice(JDBC lib), > > > > this change would totally make SkyWalking no choice but to stay in > the > > > > old release or remove this feature. > > > > > > > > This will be many of our end users' position if we announce that. > > > > > > > > JDK 8 actually has a longer LTS than JDK 11. JDK 8 - At least Nov > > > > 2026, JDK 11 - At least Oct 2024 > > > > Source from Temurin(was, OpenJDK) https://adoptium.net/support/ > > > > > > > > It will surprise everyone, ShardingSphere community removed the > > > > primary and widely used JDK version, and move on to another > > > > dead-earlier version :( > > > > > > > > If this is a vote for the future, I would say -1. > > > > > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > Zheng Feng 于2023年1月13日周五 16:54写道： > > > > > > > > > > Yeah, I understand your concern for supporting the legacy > > applications > > > > > especially for such users who have been using it in the production > > > > > environment. But from the point of innovation, I think it would be > > great > > > > to > > > > > use the latest JDK which has many new impressive features. And > > sooner or > > > > > later, we still have to face the problem of dropping JDK 8. So why > > don't > > > > we > > > > > consider it for now? > > > > > > > > > > I don't think 200+ modules is a BIG problem for maintaining work. > > You can > > > > > see Apache camel which has 500+ modules but still supports 3 LTS > > > > versions. > > > > > > > > > > There could be some way to help us to do backporting work such as > > using a > > > > > github bot. > > > > > > > > > > Anway, I also think it would be an opportunity to think about the > > RoadMap > > > > > of shardingsphere. > > > > > > > > > > Thanks, > > > > > Zheng Feng > > > > > > > > > > zhangli...@apache.org 于2023年1月13日周五 > 14:42写道： > > > > > > > > > > > There are lots of legacy applications still using Java 8. > > > > > > ShardingSphere-JDBC is a java lib, not standalone process, the > LTS > > of > > > > Java > > > > > > 8 is necessary. > > > > > > > > > > > > But there are 200+ modules in ShardingSphere, so I am afraid > nobody > > > > > > can undertake the costs of maintain 2 different versions. > > > > > > > > > > > > -- > > > > > > > > > > > > Sincerely, > > >
Re: [DISCUSS] Plan to drop support for JDK 8
Zheng Feng 于2023年1月13日周五 21:04写道： > > I'm not pushing to drop JDK 8 now but I wonder if it is possible to > maintain two LTS versions of shardingsphere. e.g. 5.x for JDK 8 and 6.x for > JDK 11 above. New features end, from my understanding, this is the end of support of JDK8. Maintaining mode is only about high-priority bug fixing, and no enhancement, no new feature, no performance improvement. With time, many things can't cherry-pick back to the JDK 8. > > Sheng Wu 于2023年1月13日周五 20:58写道： > > > From my side, only if there are key improvements for JDK 11, we are > > worth taking that risk. Especially, whether these things are JDK 11 > > compiling only. > > SkyWalking chose to use ShardingSphere proxy, but we discussed the > > possibilities of ShardingJDBC, but if we made that choice(JDBC lib), > > this change would totally make SkyWalking no choice but to stay in the > > old release or remove this feature. > > > > This will be many of our end users' position if we announce that. > > > > JDK 8 actually has a longer LTS than JDK 11. JDK 8 - At least Nov > > 2026, JDK 11 - At least Oct 2024 > > Source from Temurin(was, OpenJDK) https://adoptium.net/support/ > > > > It will surprise everyone, ShardingSphere community removed the > > primary and widely used JDK version, and move on to another > > dead-earlier version :( > > > > If this is a vote for the future, I would say -1. > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Zheng Feng 于2023年1月13日周五 16:54写道： > > > > > > Yeah, I understand your concern for supporting the legacy applications > > > especially for such users who have been using it in the production > > > environment. But from the point of innovation, I think it would be great > > to > > > use the latest JDK which has many new impressive features. And sooner or > > > later, we still have to face the problem of dropping JDK 8. So why don't > > we > > > consider it for now? > > > > > > I don't think 200+ modules is a BIG problem for maintaining work. You can > > > see Apache camel which has 500+ modules but still supports 3 LTS > > versions. > > > > > > There could be some way to help us to do backporting work such as using a > > > github bot. > > > > > > Anway, I also think it would be an opportunity to think about the RoadMap > > > of shardingsphere. > > > > > > Thanks, > > > Zheng Feng > > > > > > zhangli...@apache.org 于2023年1月13日周五 14:42写道： > > > > > > > There are lots of legacy applications still using Java 8. > > > > ShardingSphere-JDBC is a java lib, not standalone process, the LTS of > > Java > > > > 8 is necessary. > > > > > > > > But there are 200+ modules in ShardingSphere, so I am afraid nobody > > > > can undertake the costs of maintain 2 different versions. > > > > > > > > -- > > > > > > > > Sincerely, > > > > Liang Zhang (John) > > > > Apache ShardingSphere > > > > > > > > > > > > 吴伟杰 于2023年1月12日周四 10:57写道： > > > > > > > > > I also want to use the Java 11 or 17. > > > > > We have had to do some special handling in codes to avoid performance > > > > > issues in Java 8 (such as JDK-8161372 [1]). > > > > > > > > > > [1] https://bugs.openjdk.java.net/browse/JDK-8161372 > > > > > > > > > > Regards, > > > > > Weijie > > > > > --- > > > > > > > > > > Wu Weijie 吴伟杰 > > > > > Apache ShardingSphere PMC > > > > > GitHub@TeslaCN > > > > > > > > > > Zheng Feng 于2023年1月11日周三 20:18写道： > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > This thought is coming from upgrading antlr to 4.10.1 [1] which is > > only > > > > > for > > > > > > Java 11 now. Currently it looks like that the Hibernate 6.0.x [2] > > and > > > > > > Quarkus 2.15.x [3] integrations has been blocked by this upgrading > > > > issue. > > > > > > > > > > > > I think it could be some other 3rd party libraries with this > > similar > > > > > issue > > > > > > sooner or later. So it is time to think about the plan to
Re: [DISCUSS] Plan to drop support for JDK 8
>From my side, only if there are key improvements for JDK 11, we are worth taking that risk. Especially, whether these things are JDK 11 compiling only. SkyWalking chose to use ShardingSphere proxy, but we discussed the possibilities of ShardingJDBC, but if we made that choice(JDBC lib), this change would totally make SkyWalking no choice but to stay in the old release or remove this feature. This will be many of our end users' position if we announce that. JDK 8 actually has a longer LTS than JDK 11. JDK 8 - At least Nov 2026, JDK 11 - At least Oct 2024 Source from Temurin(was, OpenJDK) https://adoptium.net/support/ It will surprise everyone, ShardingSphere community removed the primary and widely used JDK version, and move on to another dead-earlier version :( If this is a vote for the future, I would say -1. Sheng Wu 吴晟 Twitter, wusheng1108 Zheng Feng 于2023年1月13日周五 16:54写道： > > Yeah, I understand your concern for supporting the legacy applications > especially for such users who have been using it in the production > environment. But from the point of innovation, I think it would be great to > use the latest JDK which has many new impressive features. And sooner or > later, we still have to face the problem of dropping JDK 8. So why don't we > consider it for now? > > I don't think 200+ modules is a BIG problem for maintaining work. You can > see Apache camel which has 500+ modules but still supports 3 LTS versions. > > There could be some way to help us to do backporting work such as using a > github bot. > > Anway, I also think it would be an opportunity to think about the RoadMap > of shardingsphere. > > Thanks, > Zheng Feng > > zhangli...@apache.org 于2023年1月13日周五 14:42写道： > > > There are lots of legacy applications still using Java 8. > > ShardingSphere-JDBC is a java lib, not standalone process, the LTS of Java > > 8 is necessary. > > > > But there are 200+ modules in ShardingSphere, so I am afraid nobody > > can undertake the costs of maintain 2 different versions. > > > > -- > > > > Sincerely, > > Liang Zhang (John) > > Apache ShardingSphere > > > > > > 吴伟杰 于2023年1月12日周四 10:57写道： > > > > > I also want to use the Java 11 or 17. > > > We have had to do some special handling in codes to avoid performance > > > issues in Java 8 (such as JDK-8161372 [1]). > > > > > > [1] https://bugs.openjdk.java.net/browse/JDK-8161372 > > > > > > Regards, > > > Weijie > > > --- > > > > > > Wu Weijie 吴伟杰 > > > Apache ShardingSphere PMC > > > GitHub@TeslaCN > > > > > > Zheng Feng 于2023年1月11日周三 20:18写道： > > > > > > > > > > > Hi all, > > > > > > > > This thought is coming from upgrading antlr to 4.10.1 [1] which is only > > > for > > > > Java 11 now. Currently it looks like that the Hibernate 6.0.x [2] and > > > > Quarkus 2.15.x [3] integrations has been blocked by this upgrading > > issue. > > > > > > > > I think it could be some other 3rd party libraries with this similar > > > issue > > > > sooner or later. So it is time to think about the plan to drop JDK 8 in > > > > shardingsphere now. > > > > > > > > I know this is BIG breaking change that could impact a lot of people > > who > > > > use the shardingsphere. Also it is not very clear in current roadmap > > [4] > > > > and the document for support JDKs. > > > > > > > > So my plan is to keep 5.x branch which sticks to JDK 8 and should be a > > > LTS > > > > version (I'm not sure how long we will be like to support it?). Then > > bump > > > > the master branch to 6.0 to drop JDK 8 support as soon as possible. > > There > > > > will be a little bit much more maintenance works with 5.x and master > > > > branches. > > > > > > > > What the others think? and we definitely need a formal voting process > > for > > > > this plan after this discussion. > > > > > > > > Regards, > > > > Zheng Feng > > > > > > > > [1] https://github.com/antlr/antlr4/releases/tag/4.10.1 > > > > [2] https://github.com/apache/shardingsphere/pull/20119 > > > > [3] > > https://github.com/quarkiverse/quarkus-shardingsphere-jdbc/issues/84 > > > > [4] > > > https://shardingsphere.apache.org/document/current/en/overview/#roadmap > > > > >
Re: [VOTE] Release Apache ShardingSphere 5.3.1
+1 binding. SkyWalking side integration tests passed. Zheng Feng 于2023年1月7日 周六11:49写道： > +1 (non-binding) and thanks for releasing! > > I checked: > [X] Download links are valid. > > [X] Checksums and PGP signatures are valid. > > [X] Source code distributions have correct names matching the current > release. > > [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [X] All files have license headers if necessary. > > [X] No compiled archives bundled in source archive. > > Also I checked it with quarkus-shardingsphere-jdbc [1] and it works. > > [1] https://github.com/quarkiverse/quarkus-shardingsphere-jdbc > > > Hongsheng Zhong 于2023年1月7日周六 01:08写道： > > > Hello ShardingSphere Community, > > > > This is a call for vote to release Apache ShardingSphere version 5.3.1. > > > > Release notes: > > https://github.com/apache/shardingsphere/blob/5.3.1/RELEASE-NOTES.md > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/shardingsphere/5.3.1/ > > > > Maven 2 staging repository: > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1125/org/apache/shardingsphere/ > > > > Git tag for the release: > > https://github.com/apache/shardingsphere/tree/5.3.1/ > > > > Release Commit ID: > > > > > https://github.com/apache/shardingsphere/commit/024c4d33b5098a644346c079104247ce614e5078 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > > > Look here for how to verify this release candidate: > > > > > https://shardingsphere.apache.org/community/en/involved/release/shardingsphere/ > > > > GPG key ID: > > 02FDCD6B8F94787A > > > > The vote will be open for at least 72 hours or until the necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > PMC vote is +1 binding, all others are +1 non-binding. > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] Source code distributions 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. > > > > Regards, > > Hongsheng > > > > > > > > > > Hongsheng Zhong > > Apache ShardingSphere Committer GitHub@sandynz > > > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Release Plan of ShardingSphere 5.3.1
I think Longtao is working on that. The last update from today morning is, there is a performance impact when updating metadata. The attachment is the profiling result. Sheng Wu 吴晟 Twitter, wusheng1108 吴伟杰 于2023年1月5日周四 09:40写道： > > Hi Sheng > > Is there any details about the performance impact? How could we reproduce it? > > Regards, > Weijie > --- > > Wu Weijie 吴伟杰 > Apache ShardingSphere PMC > GitHub@TeslaCN > > Sheng Wu 于2023年1月4日周三 18:42写道： > > > > There is under doing about bumping version of ShardingSphere in SkyWalking > > storage. > > From last sync, there are some unclear performance impact. > > > > I want to check whether that could be located and fixed before the release? > > > > Hongsheng Zhong 于2023年1月4日 周三18:28写道： > > > > > Hi community, > > > > > > > > > > > > > > > After the release of 5.3.0 version, we have received a lot of feedback > > > > > > from users and developers. Now we plan to release the ShardingSphere 5.3.1 > > > > > > version these days, which has made a lot of optimization and improvement > > > for > > > > > > these feedback. > > > > > > > > > > > > > > > Please refer to this release notes[1] to confirm whether it contains the > > > > > > features you expect. If I missed anything, please remind me ASAP. If there > > > > > > are any suggestions, please feel free to tell us. > > > > > > > > > > > > > > > [1] https://github.com/apache/shardingsphere/discussions/23328 > > > > > > > > > > > > > > > Best regards, > > > > > > Hongsheng > > > > > > > > > > > > > > > -- > > > > > > Hongsheng Zhong (zhonghongsh...@apache.org) > > > Apache ShardingSphere Committer > > > GitHub@sandynz > > > > -- > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108
Re: [DISCUSS] Release Plan of ShardingSphere 5.3.1
There is under doing about bumping version of ShardingSphere in SkyWalking storage. >From last sync, there are some unclear performance impact. I want to check whether that could be located and fixed before the release? Hongsheng Zhong 于2023年1月4日 周三18:28写道： > Hi community, > > > > > After the release of 5.3.0 version, we have received a lot of feedback > > from users and developers. Now we plan to release the ShardingSphere 5.3.1 > > version these days, which has made a lot of optimization and improvement > for > > these feedback. > > > > > Please refer to this release notes[1] to confirm whether it contains the > > features you expect. If I missed anything, please remind me ASAP. If there > > are any suggestions, please feel free to tell us. > > > > > [1] https://github.com/apache/shardingsphere/discussions/23328 > > > > > Best regards, > > Hongsheng > > > > > -- > > Hongsheng Zhong (zhonghongsh...@apache.org) > Apache ShardingSphere Committer > GitHub@sandynz -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Could someone move the GitHub notification of ShardingSphere-on-cloud out of dev maillist?
Hi I am keeping receiving GitHub notification emails on the dev mail list, it is a kind of annoying, Could someone lead that project change the setup? Sheng Wu 吴晟 Twitter, wusheng1108
Re: In January 2022，Apache APISIX Community want to online meetup with Apache ShardingSphere
Exciting to see this joint event :) Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2021年11月17日周三 下午2:14写道： > Hello Yeliang and APISIX community, > > > Nice to meet you. ;-) > This proposal sounds cool, we’d like to be part of this co-meetup. > Plus, if we like, we still can involve other communities. > @Liye could you have a look this event invitation? > > > Best, > Trista > > -- > Juan Pan(Trista), Twitter: @tristaZero > > > On 11/17/2021 13:49，yeliang wang wrote： > Hi, community, > > My name is Yeliang Wang, and I am Apache APISIX Committer. > > i want to have the Apache APISIX Online Meetup on January 15, 2022, and I > hope to invite ShardingSphere to participate. > > Participation content: > 1、Two keynote, One topic for 45 minutes. > > Thanks, > Yeliang Wang, Apache APISIX Committer > Github: wang-yeliang >
Re: [VOTE] Release Apache ShardingSphere 5.0.0
+1 binding 1. asc(src) checked 2. sha512 exist 3. version correct 4. compiling passed 5. UTs passed Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2021年11月7日周日 下午3:00写道： > +1, I checked > > [X] Download links are valid. > > [X] Checksums and PGP signatures are valid. > > [X] Source code distributions have correct names matching the current > release. > > [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [X] All files have license headers if necessary. > > [X] No compiled archives bundled in source archive. > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere > > > Haoran Meng 于2021年11月2日周二 上午1:00写道： > > > Hello ShardingSphere Community, > > > > This is a call for vote to release Apache ShardingSphere version 5.0.0 > > > > Release notes: > > https://github.com/apache/shardingsphere/blob/5.0.0/RELEASE-NOTES.md > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/shardingsphere/5.0.0/ > > > > Maven 2 staging repository: > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1069/org/apache/shardingsphere/ > > > > Git tag for the release: > > https://github.com/apache/shardingsphere/tree/5.0.0/ > > > > Release Commit ID: > > > > > https://github.com/apache/shardingsphere/commit/d3409a2e36b4233372cfd048038634b7a518dc5d > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > > > Look at here for how to verify this release candidate: > > https://shardingsphere.apache.org/community/en/contribute/release/ > > > > GPG user ID: > > menghaoran > > > > 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 > > > > PMC vote is +1 binding, all others is +1 non-binding. > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] Source code distributions 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. > > >
Re: [VOTE] Release Apache ShardingSphere 5.0.0-RC1
Hi, SkyWalking eyes tool provides capabilities to resolve all dependencies for Maven. You could use it to check. zhangli...@apache.org 于2021年10月23日 周六下午12:24写道： > Sorry, I have to say -1. > > The new lib `rxtx` is LGPL which is CATEGORY X. > > I find other problems which is not block issue, but it is better to fix > them into next release. > > 1. The licenses of new libraries are not add yet, they are: > > Aalto XML (Apache 2.0) > Barchart UDT Bundle (BSD2) > Stax2 API (BSD2) > > The missing licenses are all compatible. > > 2. he reference of `commons-compiler 3.0.11` is wrong. > > 3. ElasticJob has already upgraded to 3.0.1, ShardingSphere is still using > 3.0.0-beta which is not stable. > > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere > > > Zheng Feng 于2021年10月21日周四 下午6:04写道： > > > +1 (non-binding) > > > > Haoran Meng 于2021年10月20日周三 下午4:38写道： > > > > > Hello ShardingSphere Community, > > > > > > This is a call for vote to release Apache ShardingSphere version > > 5.0.0-RC1 > > > > > > Release notes: > > > https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md > > > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/shardingsphere/5.0.0-RC1/ > > > > > > Maven 2 staging repository: > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1067/org/apache/shardingsphere/ > > > > > > Git tag for the release: > > > https://github.com/apache/shardingsphere/tree/5.0.0-RC1/ > > > > > > Release Commit ID: > > > > > > > > > https://github.com/apache/shardingsphere/commit/d38a546468a3eb3397cb3d218f61d626229f113a > > > > > > Keys to verify the Release Candidate: > > > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > > > > > Look at here for how to verify this release candidate: > > > https://shardingsphere.apache.org/community/en/contribute/release/ > > > > > > GPG user ID: > > > menghaoran > > > > > > 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 > > > > > > PMC vote is +1 binding, all others is +1 non-binding. > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > > > > [ ] Checksums and PGP signatures are valid. > > > > > > [ ] Source code distributions 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. > > > > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Introduce Quarkus extension for ShardingSphere
I think this doesn't need PMC prove, it is out of Apache ShardingSphere. Zheng Feng 于2021年9月28日 周二上午9:46写道： > Hi all, > > I'm working on a quarkus extension for shardingsphere which could be found > on [1]. I think this would be very helpful for people who want to integrate > a application with the shardingsphere in Quarkus. And it would leverage > quarkus datasources and many other capabilities to improve the performance > of applications startup speed and runtime memory, especially with the > native mode which could compile the Java classes into the native executions > by using Graal VM. Anyway, feel free to comment here or github discussion > [2]. > > Thanks, > Zheng Feng > > [1] https://github.com/quarkiverse/quarkus-shardingsphere-jdbc > [2] https://github.com/apache/shardingsphere/discussions/12594 > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: What is the useful of asf branch on https://github.com/apache/shardingsphere-doc
It is used by ASF INFRA to host the static website files and deploy them on the environment. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2021年7月26日周一 下午1:53写道： > Hi, > > I notice there is asf branch on > https://github.com/apache/shardingsphere-doc > . > It seems useless, can I remove the branch? > > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere ElasticJob UI 3.0.0
Sorry, I don't have a local JDK8 env to compile. SkyWalking is just checking JDK8 level compiling on GitHub CI only. I didn't check manually anymore. Sheng Wu 吴晟 Twitter, wusheng1108 吴伟杰 于2021年7月23日周五 上午11:46写道： > Hi Sheng > Please try JDK8. We will adapt JDK11 next release. > > Weijie Wu 吴伟杰 > > > 在 2021年7月23日星期五，Sheng Wu 写道： > > > Hi > > > > I am using JDK 11 to compile the project, but face this exception. Is > this > > some local setting I need to apply to? > > ``` > > > > [INFO] --- maven-compiler-plugin:3.3:compile (default-compile) @ > > shardingsphere-elasticjob-lite-ui-backend --- > > > > [INFO] Changes detected - recompiling the module! > > > > [INFO] Compiling 62 source files to > > /Users/wusheng/Downloads/apache-shardingsphere-elasticjob-3.0.0-ui-src/ > > shardingsphere-elasticjob-lite-ui/shardingsphere- > > elasticjob-lite-ui-backend/target/classes > > > > WARNING: An illegal reflective access operation has occurred > > > > WARNING: Illegal reflective access by lombok.javac.apt.LombokProcessor to > > field > > com.sun.tools.javac.processing.JavacProcessingEnvironment.discoveredProcs > > > > WARNING: Please consider reporting this to the maintainers of > > lombok.javac.apt.LombokProcessor > > > > WARNING: Use --illegal-access=warn to enable warnings of further illegal > > reflective access operations > > > > WARNING: All illegal access operations will be denied in a future release > > > > [INFO] > > > > > > [INFO] Reactor Summary for shardingsphere-elasticjob-ui 3.0.0: > > > > [INFO] > > > > [INFO] shardingsphere-elasticjob-ui ... SUCCESS [ > > 1.512 > > s] > > > > [INFO] shardingsphere-elasticjob-lite-ui .. SUCCESS [ > > 0.626 > > s] > > > > [INFO] shardingsphere-elasticjob-lite-ui-frontend . SUCCESS > [02:43 > > min] > > > > [INFO] shardingsphere-elasticjob-lite-ui-backend .. FAILURE [ > > 24.421 s] > > > > [INFO] shardingsphere-elasticjob-cloud-ui . SKIPPED > > > > [INFO] shardingsphere-elasticjob-cloud-ui-frontend SKIPPED > > > > [INFO] shardingsphere-elasticjob-cloud-ui-backend . SKIPPED > > > > [INFO] shardingsphere-elasticjob-ui-distribution .. SKIPPED > > > > [INFO] shardingsphere-elasticjob-ui-src-distribution .. SKIPPED > > > > [INFO] shardingsphere-elasticjob-lite-ui-bin-distribution . SKIPPED > > > > [INFO] shardingsphere-elasticjob-cloud-ui-bin-distribution SKIPPED > > > > [INFO] > > > > > > [INFO] BUILD FAILURE > > > > [INFO] > > > > > > [INFO] Total time: 03:10 min > > > > [INFO] Finished at: 2021-07-23T09:16:35+08:00 > > > > [INFO] > > > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile > > (default-compile) > > on project shardingsphere-elasticjob-lite-ui-backend: Fatal error > > compiling: > > java.lang.ExceptionInInitializerError: > > com.sun.tools.javac.code.TypeTags -> [Help > > 1] > > ``` > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Juan Pan 于2021年7月21日周三 上午8:15写道： > > > > > Hi +1 binding > > > > > > > > > > > > here is my checking list. > > > > > > > > > > > > > > > [x] Download links are valid. > > > > > > [x] Checksums and PGP signatures are valid. > > > > > > [x] LICENSE, NOTICE files are correct. > > > > > > [x] All files have license headers if necessary. > > > > > > > > > > > > > > > > > > > > -- > > > Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) > > IPMC > > > Twitter, @trista86934690 > > > > > > > > > On 07/15/2021 11:04，吴伟杰 wrote： > > > Hello ShardingSphere Community, > > > > > > This is a call for vote to release Apache ShardingSphere ElasticJob UI > > > version 3.0.0 > > > > > > Release notes: > > &
Re: [VOTE] Release Apache ShardingSphere ElasticJob UI 3.0.0
Hi I am using JDK 11 to compile the project, but face this exception. Is this some local setting I need to apply to? ``` [INFO] --- maven-compiler-plugin:3.3:compile (default-compile) @ shardingsphere-elasticjob-lite-ui-backend --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 62 source files to /Users/wusheng/Downloads/apache-shardingsphere-elasticjob-3.0.0-ui-src/shardingsphere-elasticjob-lite-ui/shardingsphere-elasticjob-lite-ui-backend/target/classes WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by lombok.javac.apt.LombokProcessor to field com.sun.tools.javac.processing.JavacProcessingEnvironment.discoveredProcs WARNING: Please consider reporting this to the maintainers of lombok.javac.apt.LombokProcessor WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] [INFO] Reactor Summary for shardingsphere-elasticjob-ui 3.0.0: [INFO] [INFO] shardingsphere-elasticjob-ui ... SUCCESS [ 1.512 s] [INFO] shardingsphere-elasticjob-lite-ui .. SUCCESS [ 0.626 s] [INFO] shardingsphere-elasticjob-lite-ui-frontend . SUCCESS [02:43 min] [INFO] shardingsphere-elasticjob-lite-ui-backend .. FAILURE [ 24.421 s] [INFO] shardingsphere-elasticjob-cloud-ui . SKIPPED [INFO] shardingsphere-elasticjob-cloud-ui-frontend SKIPPED [INFO] shardingsphere-elasticjob-cloud-ui-backend . SKIPPED [INFO] shardingsphere-elasticjob-ui-distribution .. SKIPPED [INFO] shardingsphere-elasticjob-ui-src-distribution .. SKIPPED [INFO] shardingsphere-elasticjob-lite-ui-bin-distribution . SKIPPED [INFO] shardingsphere-elasticjob-cloud-ui-bin-distribution SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:10 min [INFO] Finished at: 2021-07-23T09:16:35+08:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on project shardingsphere-elasticjob-lite-ui-backend: Fatal error compiling: java.lang.ExceptionInInitializerError: com.sun.tools.javac.code.TypeTags -> [Help 1] ``` Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2021年7月21日周三 上午8:15写道： > Hi +1 binding > > > > here is my checking list. > > > > > [x] Download links are valid. > > [x] Checksums and PGP signatures are valid. > > [x] LICENSE, NOTICE files are correct. > > [x] All files have license headers if necessary. > > > > > > -- > Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) IPMC > Twitter, @trista86934690 > > > On 07/15/2021 11:04，吴伟杰 wrote： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere ElasticJob UI > version 3.0.0 > > Release notes: > > https://github.com/apache/shardingsphere-elasticjob-ui/blob/master/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/elasticjob-ui-3.0.0/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob-ui/tree/3.0.0/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob-ui/commit/1c1707b3aac284f957babc89023a24c8355dae2d > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > Look at here for how to verify this release candidate: > > https://shardingsphere.apache.org/community/en/contribute/release-elasticjob-ui/ > > GPG key ID: > 2DE3A2A9 > > The vote will be open for at least 72 hours or until the necessary number > of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > PMC vote is +1 binding, all others are +1 non-binding. > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] Source code distributions 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. >
Re: [DISCUSS] Remove ShardingSphere SkyWalking agent plugins for legacy version from SkyWalking's master branch
Thank you so much to polish this. I have approved it. Sheng Wu 吴晟 Twitter, wusheng1108 吴伟杰 于2021年7月18日周日 下午6:34写道： > Hi Sheng > > I have submitted a PR to do that. > https://github.com/apache/skywalking/pull/7323 > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere > > Sheng Wu 于2021年7月14日周三 下午5:42写道： > > > > Hi Weijie > > > > Could you submit a pull request to remove all these? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Juan Pan 于2021年7月12日周一 下午12:19写道： > > > > > +1 from me. > > > > > > > > > > > > > > > > -- > > > Juan Pan(Trista), Apache ShardingSphere PMC > > > Twitter, @trista86934690 > > > > > > > > > On 07/11/2021 19:05，吴伟杰 wrote： > > > Hi > > > > > > Consider the 3.x is a GA release, and the plugins for 4.x RC are no > > > longer needed because there are already plugins for 4.x GA. > > > Our primary conclusion is removing the following plugins: > > > 1. sharding-jdbc-1.5.x-plugin > > > 2. sharding-sphere-4.x-rc3-plugin > > > 3. sharding-sphere-4.x-plugin (This is for RC1 and RC2) > > > > > > If no one objects, I will clear up the codebase next weekend. > > > > > > -- > > > > > > Sincerely, > > > Weijie Wu (TeslaCN) > > > Apache ShardingSphere > > > > > > Sheng Wu 于2021年7月11日周日 上午9:12写道： > > > > > > Hi > > > > > > Do we have a conclusion? And Weijie, could you follow this and clear > up the > > > codebase? > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > Juan Pan 于2021年7月1日周四 上午9:11写道： > > > > > > Hi, > > > > > > > > > I have no clear idea on how each plugin is different, but they are > > > actually different. > > > Considering users' preference for different releases,My +1 to keep the > 4.0 > > > and 4.1 GA versions. > > > > > > > > > > > > > > > > > > > -- > > > Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) > IPMC > > > Twitter, @trista86934690 > > > > > > > > > On 07/1/2021 07:50，Sheng Wu wrote： > > > Hi > > > > > > ``` > > > 3. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > > > 4. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > > > 5. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > > > 6. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > > > ``` > > > > > > What is the difference between 4.x and 4.0/4.1 plugins? Could some of > them > > > be removed? > > > And RC3 should be removed as you have plugins for GA releases already. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > 吴伟杰 于2021年6月30日周三 下午11:19写道： > > > > > > Hi All, > > > > > > SkyWalking's master branch hosts 7 agent plugins for different > versions of > > > ShardingSphere. > > > They think the plugins are too many. ( > > > https://github.com/apache/skywalking/pull/7171#issuecomment-868353013) > > > Here is the list: > > > > > > 1. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > > > 2. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > > > 3. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > > > 4. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > > > 5. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > > > 6. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > > > 7. > > > > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/shardingsphere-5.0.0-beta-plugin > > > > > > > > > Since the sharding-jdbc-1.5.x and the sharding-sphere-3.x have no > longer > > > been maintained, I propose to > > > remove sharding-jdbc-1.5.x-plugin > > > < > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > > > > > > and sharding-sphere-3.x-plugin > > > < > > > > > > > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > > > > > > from > > > SkyWalking's master branch to reduce maintenance costs. > > > > > > -- > > > > > > Sincerely, > > > Weijie Wu (TeslaCN) > > > Apache ShardingSphere > > > > > > > > > >
Re: [DISCUSS] Remove ShardingSphere SkyWalking agent plugins for legacy version from SkyWalking's master branch
Hi Weijie Could you submit a pull request to remove all these? Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2021年7月12日周一 下午12:19写道： > +1 from me. > > > > > -- > Juan Pan(Trista), Apache ShardingSphere PMC > Twitter, @trista86934690 > > > On 07/11/2021 19:05，吴伟杰 wrote： > Hi > > Consider the 3.x is a GA release, and the plugins for 4.x RC are no > longer needed because there are already plugins for 4.x GA. > Our primary conclusion is removing the following plugins: > 1. sharding-jdbc-1.5.x-plugin > 2. sharding-sphere-4.x-rc3-plugin > 3. sharding-sphere-4.x-plugin (This is for RC1 and RC2) > > If no one objects, I will clear up the codebase next weekend. > > ------ > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere > > Sheng Wu 于2021年7月11日周日 上午9:12写道： > > Hi > > Do we have a conclusion? And Weijie, could you follow this and clear up the > codebase? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Juan Pan 于2021年7月1日周四 上午9:11写道： > > Hi, > > > I have no clear idea on how each plugin is different, but they are > actually different. > Considering users' preference for different releases,My +1 to keep the 4.0 > and 4.1 GA versions. > > > > > > ------ > Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) IPMC > Twitter, @trista86934690 > > > On 07/1/2021 07:50，Sheng Wu wrote： > Hi > > ``` > 3. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > 4. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > 5. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > 6. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > ``` > > What is the difference between 4.x and 4.0/4.1 plugins? Could some of them > be removed? > And RC3 should be removed as you have plugins for GA releases already. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > 吴伟杰 于2021年6月30日周三 下午11:19写道： > > Hi All, > > SkyWalking's master branch hosts 7 agent plugins for different versions of > ShardingSphere. > They think the plugins are too many. ( > https://github.com/apache/skywalking/pull/7171#issuecomment-868353013) > Here is the list: > > 1. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > 2. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > 3. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > 4. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > 5. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > 6. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > 7. > > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/shardingsphere-5.0.0-beta-plugin > > > Since the sharding-jdbc-1.5.x and the sharding-sphere-3.x have no longer > been maintained, I propose to > remove sharding-jdbc-1.5.x-plugin > < > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > > and sharding-sphere-3.x-plugin > < > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > > from > SkyWalking's master branch to reduce maintenance costs. > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere > > >
Re: [DISCUSS] Remove ShardingSphere SkyWalking agent plugins for legacy version from SkyWalking's master branch
Hi Do we have a conclusion? And Weijie, could you follow this and clear up the codebase? Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2021年7月1日周四 上午9:11写道： > Hi, > > > I have no clear idea on how each plugin is different, but they are > actually different. > Considering users' preference for different releases,My +1 to keep the 4.0 > and 4.1 GA versions. > > > > > -- > Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) IPMC > Twitter, @trista86934690 > > > On 07/1/2021 07:50，Sheng Wu wrote： > Hi > > ``` > 3. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > 4. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > 5. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > 6. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > ``` > > What is the difference between 4.x and 4.0/4.1 plugins? Could some of them > be removed? > And RC3 should be removed as you have plugins for GA releases already. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > 吴伟杰 于2021年6月30日周三 下午11:19写道： > > Hi All, > > SkyWalking's master branch hosts 7 agent plugins for different versions of > ShardingSphere. > They think the plugins are too many. ( > https://github.com/apache/skywalking/pull/7171#issuecomment-868353013) > Here is the list: > > 1. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > 2. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > 3. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin > 4. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin > 5. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin > 6. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin > 7. > > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/shardingsphere-5.0.0-beta-plugin > > > Since the sharding-jdbc-1.5.x and the sharding-sphere-3.x have no longer > been maintained, I propose to > remove sharding-jdbc-1.5.x-plugin > < > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > > and sharding-sphere-3.x-plugin > < > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > > from > SkyWalking's master branch to reduce maintenance costs. > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere > >
Re: [VOTE] Release Apache ShardingSphere ElasticJob-3.0.0
+1 binding 1. Download source correct 2. sha512 exist 3. asc checked 4. version correct. Sheng Wu 吴晟 Twitter, wusheng1108 吴伟杰 于2021年6月26日周六 下午8:45写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere > ElasticJob-3.0.0 > > Release notes: > > https://github.com/apache/shardingsphere-elasticjob/blob/master/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/elasticjob-3.0.0/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1063/org/apache/shardingsphere/elasticjob/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob/tree/3.0.0/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob/commit/1b2b15d7bf653b1fd6d455d940eabb13793347bb > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > Look here for how to verify this release candidate: > > https://shardingsphere.apache.org/community/en/contribute/release-elasticjob/ > > GPG key ID: > > 2DE3A2A9 > > The vote will be open for at least 72 hours or until the necessary number > of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > PMC vote is +1 binding, all others are +1 non-binding. > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] Source code distributions 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. > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere >
Re: [DISCUSS] Remove ShardingSphere SkyWalking agent plugins for legacy version from SkyWalking's master branch
Hi ``` 3. https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin 4. https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin 5. https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin 6. https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin ``` What is the difference between 4.x and 4.0/4.1 plugins? Could some of them be removed? And RC3 should be removed as you have plugins for GA releases already. Sheng Wu 吴晟 Twitter, wusheng1108 吴伟杰 于2021年6月30日周三 下午11:19写道： > Hi All, > > SkyWalking's master branch hosts 7 agent plugins for different versions of > ShardingSphere. > They think the plugins are too many. ( > https://github.com/apache/skywalking/pull/7171#issuecomment-868353013) > Here is the list: > >1. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin >2. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin >3. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.0.x-plugin >4. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.1.0-plugin >5. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-RC3-plugin >6. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-4.x-plugin >7. > > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/shardingsphere-5.0.0-beta-plugin > > > Since the sharding-jdbc-1.5.x and the sharding-sphere-3.x have no longer > been maintained, I propose to > remove sharding-jdbc-1.5.x-plugin > < > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-jdbc-1.5.x-plugin > > > and sharding-sphere-3.x-plugin > < > https://github.com/apache/skywalking/tree/master/apm-sniffer/apm-sdk-plugin/sharding-sphere-3.x-plugin > > > from > SkyWalking's master branch to reduce maintenance costs. > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere >
Re: The design of the Skywlking Satellite
Thanks, Jiapeng I have cc'ed to APISIX and ShardingSphere mail list, as both of you are working on the SkyWalking integration from different points, this would be helpful for your end-users. Welcome you to join this sub project. Sheng Wu 吴晟 Twitter, wusheng1108 刘 嘉鹏 于2020年11月25日周三 下午8:03写道： > HI all: > > Based today’s online meeting, the design of Satellite was approved. > The final design doc is release on the website: > https://skywalking.apache.org/blog/2020-11-25-skywalking-satellite-0.1.0-design/ > I would close the discussion issue later. > https://github.com/apache/skywalking/issues/5871 > If you are interest in Satellite, welcome to join us. > > Jiapeng Liu > > 2020年11月20日 22:02，刘 嘉鹏 mailto:evan...@outlook.com>> > 写道： > > Hi all: > > We are about to set up a new subproject which is called Satellite.It is a > lightweight collector/sidecar could be deployed closing to the target > monitored system, to collect metrics, traces, and logs. Also, it provides > advanced features, such as local cache, format transform, sampling. > > If you are interested, please join the discussion. > The doc: > > https://docs.google.com/document/d/1RB5EXyX9k63QabSpaWLZvN5JQ4NoNgGIH1t8LMt6Bys/edit#heading=h.o1c72xcxm0n7 > > The discussion issue: > https://github.com/apache/skywalking/issues/5871 > > Jiapeng Liu > >
Re: [ANNOUNCE] Apache ShardingSphere 5.0.0-alpha available
Looking forward to your latest documentation update about the SQL parser :) Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年11月10日周二 下午4:09写道： > Hi all, > > > Apache ShardingSphere Team is glad to announce the new release of Apache > ShardingSphere 5.0.0-alpha. > > > ShardingSphere is an open-source ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, ShardingSphere-JDBC & ShardingSphere-Proxy. > They both provide functions of data sharding, distributed transaction and > database governance, applicable in a variety of situations such as Java > isomorphism, heterogeneous language. > Aiming at reasonably making full use of the computation and storage > capacity of the database in a distributed system, ShardingSphere defines > itself as a middleware, rather than a totally new type of database. > As the cornerstone of many enterprises, relational database still takes a > huge market share. > Therefore, at the current stage, we prefer to focus on its increment > instead of a total overturn. > > > Download Links: > https://shardingsphere.apache.org/document/current/en/downloads/ > > > Release Notes: > https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md > > > Website: https://shardingsphere.apache.org/ > > > ShardingSphere Resources: > - Issue: https://github.com/apache/shardingsphere/issues/ > - Mailing list: dev@shardingsphere.apache.org > - Documents: https://shardingsphere.apache.org/document/current/ > > > > > > > - Apache ShardingSphere Team > > > Juan Pan (Trista) > > Senior DBA & PMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > >
Re: [New feature] New SQLASTParserEngine is pubic for user to parse your SQLs soon
Great!! SkyWalking community is waiting for this for a long time. To SkyWalking dev team Once we have this, we could have `table` oriented metrics, such as write/table/second, read/table/second, or the `hot compose query tables`. These kinds of metrics would be helpful to identify the performance issue. Thanks, ShardingSphere to bring this to the open. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年10月21日周三 下午7:37写道： > Hi community, > > I am glad to announce that ShardingSphere will provide an independent SQL > parser engine for parsing SQLs! > I believe you will have some of the scenarios or use the SQL parser engine > to get a parsed AST. From now on, you will have another option for your > cases. Here are some of the advantages for ShardingSphere parser engine. > > Advantages > Mostly perfect SQL statements supported for MySQL database > Mostly perfect SQL statements supported for PostgreSQL database > Basically SQL statements supported for SQLServer database > Basically SQL statements supported for Oracle database > SQL parsed result cache for the parsing performance > AST parsed result and SQLStatement parsed result are provided meanwhile > Simple extension approach for SQLStatement visitors > Simple supplement approach and for SQL definition > Continuous improvement for the much better feature in the future. > > 5.x release will include this one, please wait for our good news! > > > > Juan Pan (Trista) > > Senior DBA & PMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > >
Re: [DISCUSS] DAG in ElasticJob
Left message on the GitHub issue. Sheng Wu 吴晟 Twitter, wusheng1108 guo jiwei 于2020年8月31日周一 下午9:54写道： > Hi, dev. >As coodajingang has contributed DAG to the community, and DAG is a core > feature in the ElasticJob, so I want to make this thread for us to discuss. > Before the discussion, we have to design 2 job execution types > like daemon and transient in ElasticJob Cloud. To illustrate simply, jobs > execute in second do not need to config misfire or DAG. > The detailed issue is here [1]. > Then, for DAG, how does it integrate with ElasticJob? And how do we > define the API? > With these questions, we may hold a video conference to discuss the > design and implementation of DAG in depth this weekend. > If you're interested, please join to discuss and leave your comments。 > > [1] : https://github.com/apache/shardingsphere-elasticjob/issues/1377 > > Regards > Jiwei Guo (Tboy) >
Re: [ElasticJob] Discuss about use RESTful API or socket for elasticjob's remote API
For more cloud natively, gRPC and GraphQL are much better than either private tcp/socket or rest. Also, today, CLI is the real solution for communicating with platform like k8s. Sheng Wu 吴晟 Twitter, wusheng1108 guo jiwei 于2020年7月31日周五 下午12:30写道： > Hi, >I think we'd better support both of them. >Kernel-level API can trace or dump data to monitor ElasticJob and make > it more friendly to reliability and stability. >And high level can provide more base functional operations for users. > > Regards > Jiwei Guo (Tboy) > > > On Fri, Jul 31, 2020 at 12:02 PM zhangli...@apache.org < > zhangli...@apache.org> wrote: > > > Hi all, > > > > The current elasticjob's remote API used RESTful API for cloud and socket > > for lite, they are in-consist for now. > > > > I'd like to discuss how to deal with the remote APIs? > > > > Choose socket or RESTful only, or both? > > > > If both, we can design for the socket (used with nc or telnet) for > > kernel-level remote API, and add a additional module for RESTful API for > > high level usage. > > > > Any suggestions? > > > > -- > > > > Sincerely, > > Liang Zhang (John) > > Apache ShardingSphere > > >
Apache Software Foundation, Trillions and Trillions Served with Chinese subtitle LIVE!
Hi Sally, Michael, Dominik, DevCom, and ALC Beijing First of all, thank you to make the video `Apache Software Foundation, Trillions and Trillions Served`, provide helps to me. I am here glad to share, with the supports from the SkyWalking community, ALC Beijing community, and Kaiyuanshe, we have this video online hosted on bilibili which is China's local friendly platform. And we have provided Chinese subtitles on that. https://www.bilibili.com/video/BV1Uz411i7MH In this short time, we already have 200+ watches, and we expect more. Thank you all to make this happens. Sheng Wu 吴晟 Twitter, wusheng1108
Re: Trillions and Trillions Served, is hosted on the China Local Video Platform
Hi Dominik and everyone interested in the translation I have moved this subtitle to the ALC Beijing https://github.com/alc-beijing/alc-site/issues/62 Sheng Wu 吴晟 Twitter, wusheng1108 Dominik Gehring 于2020年6月16日周二 下午3:41写道： > Dear all > > Glad to hear the download finally went through! > Here are the automatic generated subtitles from youtube. They are not 100% > correct but almost. > > Best , Dom > > Am Di., 16. Juni 2020 um 09:33 Uhr schrieb Willem Jiang < > willem.ji...@gmail.com>: > >> Thanks Sally. >> The English subtitle could save us lots of time when doing the >> translation. >> >> Best Regards, >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Tue, Jun 16, 2020 at 11:17 AM Sally Khudairi wrote: >> > >> > Thanks, Willem. >> > >> > We don't have a transcript at present. I can arrange for that to >> happen, but it will take a few days. >> > >> > I'll let you know when it's ready. >> > >> > Best, >> > Sally >> > >> > - - - >> > Vice President Marketing & Publicity >> > Vice President Sponsor Relations >> > The Apache Software Foundation >> > >> > Tel +1 617 921 8656 | s...@apache.org >> > >> > On Mon, Jun 15, 2020, at 23:00, Willem Jiang wrote: >> > > Thanks Sheng for the great efforts. >> > > It could be great if we have the English subtitle first for the >> > > Chinese translation. >> > > @Sally Khudairi Could you help us with that ? >> > > >> > > BTW, I already created an issue[1] in ALC-Beijing to call for help :) >> > > Please add your comment on the issue if you are interested to offer >> your help. >> > > >> > > [1]https://github.com/alc-beijing/alc-site/issues/62 >> > > >> > > >> > > Willem Jiang >> > > >> > > Twitter: willemjiang >> > > Weibo: 姜宁willem >> > > >> > > On Tue, Jun 16, 2020 at 10:40 AM Sally Khudairi >> wrote: >> > > > >> > > > Beautiful --thanks for your great efforts, Sheng! >> > > > >> > > > Do enjoy :-) >> > > > >> > > > - - - >> > > > Vice President Marketing & Publicity >> > > > Vice President Sponsor Relations >> > > > The Apache Software Foundation >> > > > >> > > > Tel +1 617 921 8656 | s...@apache.org >> > > > >> > > > >> > > > On Mon, Jun 15, 2020, at 22:32, Sheng Wu wrote: >> > > > > Hi ALC Beijing, Sally, Michael, Dominik and All >> > > > > >> > > > > I am glad to share, the video, Trillions and Trillions Served[1], >> has been online at the China local platform[2], hosted by Apache SkyWalking >> account, >> > > > > >> > > > > https://www.bilibili.com/video/BV1Uz411i7MH >> > > > > >> > > > > Also, in order to get more people to watch it, I have reached >> Jiansheng(ALC Beijing) and Ted Liu(ASF Member) to see what we could do to >> provide Chinese subtitles for this. >> > > > > >> > > > > Thanks all for helping me. >> > > > > >> > > > > [1] https://www.youtube.com/watch?v=JUt2nb0mgwg=youtu.be >> > > > > [2] Notice, as Youtube is not accessible inside China, we >> organized this. >> > > > > >> > > > > >> > > > > Sheng Wu 吴晟 >> > > > > Twitter, wusheng1108 >> > > >> > > > -- > - - - - - - - - - - - - - - - - - - - - - - - - > dominik gehring > - - - - - - - - - - - - - - - - - - - - - - - - > binzstrasse 23 > ch-8045 zürich > - - - - - - - - - - - - - - - - - - - - - - - - > g...@kg-studio.ch > http://www.kg-studio.ch >
Trillions and Trillions Served, is hosted on the China Local Video Platform
Hi ALC Beijing, Sally, Michael, Dominik and All I am glad to share, the video, Trillions and Trillions Served[1], has been online at the China local platform[2], hosted by Apache SkyWalking account, https://www.bilibili.com/video/BV1Uz411i7MH Also, in order to get more people to watch it, I have reached Jiansheng(ALC Beijing) and Ted Liu(ASF Member) to see what we could do to provide Chinese subtitles for this. Thanks all for helping me. [1] https://www.youtube.com/watch?v=JUt2nb0mgwg=youtu.be [2] Notice, as Youtube is not accessible inside China, we organized this. Sheng Wu 吴晟 Twitter, wusheng1108
Re: [ElasticJob] Discuss new features of ElasticJob 3.0
zhangli...@apache.org 于2020年6月15日 周一17:58写道： > How about spilt them? > For event trace data (about job execute timestamp and result), persist into > MySQL or other databases, for metrics, persist into Prometheus. I think separating them will make you can't use Grafana. I think alarm, monitor and observability should be an important and separated topic. Sheng > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年6月15日周一 下午2:02写道： > > > What event trace data? Prometheus is focusing on metrics only. Only > > statistic data is suitable. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年6月15日周一 下午1:34写道： > > > > > Hi Sheng, > > > > > > The mean of `Support prometheus storage` is putting the event trace > data > > > info prometheus ecosystem, we can use push gateway to collect the data > > and > > > use grafana to display the result. > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > > > > > Sheng Wu 于2020年6月15日周一 上午9:26写道： > > > > > > > Hi Liang > > > > > > > > About SkyWalking, that is another topic. It is fine to do that later. > > > > My question is, what do you mean `Support prometheus storage`. > > Prometheus > > > > is a monitoring system, basically. What does it storage you mean? > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > > > > zhangli...@apache.org 于2020年6月13日周六 > 上午1:28写道： > > > > > > > > > For persist job event trace. We can consider about use SkyWalking > to > > > > trace > > > > > the job event, is it possible? > > > > > > > > > > -- > > > > > > > > > > Liang Zhang (John) > > > > > Apache ShardingSphere & Dubbo > > > > > > > > > > > > > > > Sheng Wu 于2020年6月12日周五 下午4:54写道： > > > > > > > > > > > zhangli...@apache.org 于2020年6月12日周五 > > > 下午4:24写道： > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > We are beginning to develop ElasticJob, and want to add some > new > > > > > features > > > > > > > in version 3.0. > > > > > > > > > > > > > > I want discuss the feature of it. > > > > > > > > > > > > > > Some ideas for new features: > > > > > > > > > > > > > > - Support one time trigger for ElasticJob lite > > > > > > > - Support job dependency based one sharding item > > > > > > > - Use native ZooKeeper API instead of curator > > > > > > > > > > > > > > Some ideas for new architecture: > > > > > > > > > > > > > > - Refactor Job API, just keep SimpleJob, make other job types > > > > introduce > > > > > > via > > > > > > > SPI > > > > > > > - Redesign Job domain, make job as top level interface, which > > > > composite > > > > > > by > > > > > > > task (sharding item) > > > > > > > - Refactor event trace module > > > > > > > - Split event trace and elasticjob-core module > > > > > > > - Open SPI for event trace data storage > > > > > > > - Support prometheus storage > > > > > > > > > > > > > > > > > > > What is Prometheus storage? > > > > > > > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Liang Zhang (John) > > > > > > > Apache ShardingSphere & Dubbo > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [ElasticJob] Discuss new features of ElasticJob 3.0
What event trace data? Prometheus is focusing on metrics only. Only statistic data is suitable. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年6月15日周一 下午1:34写道： > Hi Sheng, > > The mean of `Support prometheus storage` is putting the event trace data > info prometheus ecosystem, we can use push gateway to collect the data and > use grafana to display the result. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年6月15日周一 上午9:26写道： > > > Hi Liang > > > > About SkyWalking, that is another topic. It is fine to do that later. > > My question is, what do you mean `Support prometheus storage`. Prometheus > > is a monitoring system, basically. What does it storage you mean? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年6月13日周六 上午1:28写道： > > > > > For persist job event trace. We can consider about use SkyWalking to > > trace > > > the job event, is it possible? > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > > > > > Sheng Wu 于2020年6月12日周五 下午4:54写道： > > > > > > > zhangli...@apache.org 于2020年6月12日周五 > 下午4:24写道： > > > > > > > > > Hi all, > > > > > > > > > > We are beginning to develop ElasticJob, and want to add some new > > > features > > > > > in version 3.0. > > > > > > > > > > I want discuss the feature of it. > > > > > > > > > > Some ideas for new features: > > > > > > > > > > - Support one time trigger for ElasticJob lite > > > > > - Support job dependency based one sharding item > > > > > - Use native ZooKeeper API instead of curator > > > > > > > > > > Some ideas for new architecture: > > > > > > > > > > - Refactor Job API, just keep SimpleJob, make other job types > > introduce > > > > via > > > > > SPI > > > > > - Redesign Job domain, make job as top level interface, which > > composite > > > > by > > > > > task (sharding item) > > > > > - Refactor event trace module > > > > > - Split event trace and elasticjob-core module > > > > > - Open SPI for event trace data storage > > > > > - Support prometheus storage > > > > > > > > > > > > > What is Prometheus storage? > > > > > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Liang Zhang (John) > > > > > Apache ShardingSphere & Dubbo > > > > > > > > > > > > > > >
Re: [ElasticJob] Discuss new features of ElasticJob 3.0
Hi Liang About SkyWalking, that is another topic. It is fine to do that later. My question is, what do you mean `Support prometheus storage`. Prometheus is a monitoring system, basically. What does it storage you mean? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年6月13日周六 上午1:28写道： > For persist job event trace. We can consider about use SkyWalking to trace > the job event, is it possible? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年6月12日周五 下午4:54写道： > > > zhangli...@apache.org 于2020年6月12日周五 下午4:24写道： > > > > > Hi all, > > > > > > We are beginning to develop ElasticJob, and want to add some new > features > > > in version 3.0. > > > > > > I want discuss the feature of it. > > > > > > Some ideas for new features: > > > > > > - Support one time trigger for ElasticJob lite > > > - Support job dependency based one sharding item > > > - Use native ZooKeeper API instead of curator > > > > > > Some ideas for new architecture: > > > > > > - Refactor Job API, just keep SimpleJob, make other job types introduce > > via > > > SPI > > > - Redesign Job domain, make job as top level interface, which composite > > by > > > task (sharding item) > > > - Refactor event trace module > > > - Split event trace and elasticjob-core module > > > - Open SPI for event trace data storage > > > - Support prometheus storage > > > > > > > What is Prometheus storage? > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: [ElasticJob] Discuss new features of ElasticJob 3.0
zhangli...@apache.org 于2020年6月12日周五 下午4:24写道： > Hi all, > > We are beginning to develop ElasticJob, and want to add some new features > in version 3.0. > > I want discuss the feature of it. > > Some ideas for new features: > > - Support one time trigger for ElasticJob lite > - Support job dependency based one sharding item > - Use native ZooKeeper API instead of curator > > Some ideas for new architecture: > > - Refactor Job API, just keep SimpleJob, make other job types introduce via > SPI > - Redesign Job domain, make job as top level interface, which composite by > task (sharding item) > - Refactor event trace module > - Split event trace and elasticjob-core module > - Open SPI for event trace data storage > - Support prometheus storage > What is Prometheus storage? Sheng Wu 吴晟 Twitter, wusheng1108 > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Consider to remove the incubator release?
Hi ShardingSphere As we have released new versions after graduation, the incubator releases seem to be able to remove from the mirror system. What do you think? NOTICE, All incubator releases are still available in the archive. https://archive.apache.org/dist/incubator/shardingsphere/ Sheng Wu 吴晟 Twitter, wusheng1108
Re: Could someone move the notification mail from dev?
You could do by yourself. https://github.com/apache/skywalking-rocketbot-ui/blob/master/.asf.yaml#L33 Do you want this way? Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2020年6月10日周三 上午11:27写道： > Hi Sheng, > > Don't worry, I'm going to send a ticket to infra. > > -- > > Zhang Yonglun > Apache ShardingSphere > > > Sheng Wu 于2020年6月10日周三 上午11:20写道： > > > Anyone would take care of this? > > The dev mail list turns crazy to me, already. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Sheng Wu 于2020年6月8日周一 上午11:36写道： > > > > > Hi > > > > > > As new repos have been added, there are many notification mails in the > > > mail list again. Could some one remove them? > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > >
Re: Could someone move the notification mail from dev?
Anyone would take care of this? The dev mail list turns crazy to me, already. Sheng Wu 吴晟 Twitter, wusheng1108 Sheng Wu 于2020年6月8日周一 上午11:36写道： > Hi > > As new repos have been added, there are many notification mails in the > mail list again. Could some one remove them? > > Sheng Wu 吴晟 > Twitter, wusheng1108 >
Could someone move the notification mail from dev?
Hi As new repos have been added, there are many notification mails in the mail list again. Could some one remove them? Sheng Wu 吴晟 Twitter, wusheng1108
Re: [New API] Automatic Sharding Strategies for Databases and Tables
Does shardingsphere consider to support wildcard of table name this time? Which is still the biggest block for SkyWalking recommending ShardingSphere as the best-practice solution to medium size users. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年6月7日周日 下午3:00写道： > Thanks for your reply, I will consider your suggestion. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > > > On 06/7/2020 14:47，zhangli...@apache.org wrote： > Hi Trista, > > It is a excellent improvement! > > I have a little suggestion, how about separate the table rule > configuration to automatic_tables and manual_tables? It may better to > create the new concepts about `at_table` and `mt_table`. > User should to know what they configure actually. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan 于2020年6月7日周日 下午2:16写道： > > Hi community, > > > > > As you know, ShardingSphere is not just a simple distributed database > middleware. > > We aim at providing transparent distributed database service to our > end-users. > > Therefore, a group of new APIs is being considered to cover the detail of > sharding databases and tables, making users view distributed database > clusters as a single logical database. > > This issue[1] conveys my draft of YAML API and hopefully see your > feedback. :) > > > > > Notice: The new API is an enhancement for the old one, rather than > replacement, i.e., forward compatible. > > > > > Also, I schedule this task here, which is not an easy job, apparently. > > - [ ] New API design > > - [ ] Configuration modification > > - [ ] New interface for automatic sharding algorithm > > - [ ] Implements the New interface > > - [ ] The conversation from configuration to sharding strategies > > - [ ] Changes for various clients, such as Spring, YAML, Proxy and so on > > - [ ] Tests > > > > > > > > [1] https://github.com/apache/shardingsphere/issues/5937 > > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > > >
Re: [ElasticJob] discuss about merge ElasticJob repository
SkyWalking has multiple(>5) repo for hosting different type source codes, I think the key is, do we want to release separately? From the project perspective, I would say YES. Sheng Wu 吴晟 Twitter, wusheng1108 guo jiwei 于2020年6月6日周六 下午8:39写道： > Hi, >Good news! >As star the elastic-job project , four repos feels a little bit more . > One is preferred ! > > Regards > Jiwei Guo (Tboy) > > > On Sat, Jun 6, 2020 at 2:18 PM KimmKing wrote: > > > Sound nice. > > There more point I want to discuss here： > > - split frontend and backend or not? (for xxx-console) > > - what is elastic-job roadmap > > - what is the scope of next release version > > > > At 2020-06-06 01:18:10, "zhangli...@apache.org" > > wrote: > > >Hi all, > > > > > >ElasticJob has already transform to asf repo. There are 4 ElasticJob > repo > > >for elastic-job-lite, elastic-job-cloud, elastic-job-doc and > > >elastic-job-example. > > >I plan to keep consist with ShardingSphere' repo, just merge doc and > > >example into one repo. > > > > > >How about just use one repo for all of ElasticJob? > > > > > >-- > > > > > >Liang Zhang (John) > > >Apache ShardingSphere & Dubbo > > >
Re: Draft of ASF Board Report for Apache ShardingSphere
zhangli...@apache.org 于2020年6月3日周三 上午11:45写道： > Thank you for update, I update the draft as: > > - We have voted for accepting donation from ElasticJob (a distribute > scheduler framework) as a new scheduler solution and passed. The IP > clearance has been sent to the incubator. > Good for me. Sheng Wu 吴晟 Twitter, wusheng1108 > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年6月3日周三 上午10:29写道： > > > zhangli...@apache.org 于2020年6月2日周二 下午11:09写道： > > > > > Hi All, > > > > > > We will report to ASF Board on 10th June. This is the draft of report, > > > please let me know if we need to change anything. > > > > > > > > > ## Description: > > > The mission of Apache ShardingSphere is the creation and maintenance of > > > software related to a database clustering system providing data > sharding, > > > distributed transactions, and distributed database management > > > > > > ## Issues: > > > No. > > > > > > ## Membership Data: > > > Apache ShardingSphere was founded 2020-04-15 (2 months ago) > > > There are currently 25 committers and 14 PMC members in this project. > > > The Committer-to-PMC ratio is roughly 7:4. > > > > > > Community changes, past quarter: > > > - No new PMC members (project graduated recently). > > > - No new committers were added. > > > > > > ## Project Activity: > > > Software development activity: > > > > > > - We are preparing to release the bug fix release 4.1.1. > > > - We have added support for pluggable architecture in our master > branch. > > > - We are designing the new API for version 5.x. > > > - We accepted the donation from ElasticJob (a distribute scheduler > > > framework) as a new scheduler solution. > > > > > > > I think the more accurate statement is > > We have voted for accepting..., and passed. The IP clearance has been > sent > > to the incubator. > > > > The IP clearance lazy consensus has not been done, right? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > > > > > ## Community Health: > > > Overall community health is good. The mailing list decreased 29% > because > > > after graduation, more contributors focus development tasks on GitHub, > > > issues, pull requests, contributors are still increasing rapidly. > > > > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: Draft of ASF Board Report for Apache ShardingSphere
Yes, the issue is about project status and community status. Anything requires the ASF board's attention. Not relate to feature, routine bug/release, new committer, etc, unless, it breaks the ASF guidelines but the PMC didn't/wouldn't stop it. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年6月3日周三 上午11:40写道： > Issues maybe like problems of IP clearance or something broken with PMC. > Until now, there is no issue in the community. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan 于2020年6月3日周三 上午10:26写道： > > > Hi John, > > > > > > Thanks for this report draft. LGTM > > BTW, `ISSUES` is none. I have no idea how to define the issue in our > > report. Could you give me some hints? > > > > > > Best, > > Trista > > > > > > Juan Pan (Trista) > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > E-mail: panj...@apache.org > > > > > > > > > > On 06/2/2020 23:09，zhangli...@apache.org wrote： > > Hi All, > > > > We will report to ASF Board on 10th June. This is the draft of report, > > please let me know if we need to change anything. > > > > > > ## Description: > > The mission of Apache ShardingSphere is the creation and maintenance of > > software related to a database clustering system providing data sharding, > > distributed transactions, and distributed database management > > > > ## Issues: > > No. > > > > ## Membership Data: > > Apache ShardingSphere was founded 2020-04-15 (2 months ago) > > There are currently 25 committers and 14 PMC members in this project. > > The Committer-to-PMC ratio is roughly 7:4. > > > > Community changes, past quarter: > > - No new PMC members (project graduated recently). > > - No new committers were added. > > > > ## Project Activity: > > Software development activity: > > > > - We are preparing to release the bug fix release 4.1.1. > > - We have added support for pluggable architecture in our master branch. > > - We are designing the new API for version 5.x. > > - We accepted the donation from ElasticJob (a distribute scheduler > > framework) as a new scheduler solution. > > > > ## Community Health: > > Overall community health is good. The mailing list decreased 29% because > > after graduation, more contributors focus development tasks on GitHub, > > issues, pull requests, contributors are still increasing rapidly. > > > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > >
Re: Draft of ASF Board Report for Apache ShardingSphere
zhangli...@apache.org 于2020年6月2日周二 下午11:09写道： > Hi All, > > We will report to ASF Board on 10th June. This is the draft of report, > please let me know if we need to change anything. > > > ## Description: > The mission of Apache ShardingSphere is the creation and maintenance of > software related to a database clustering system providing data sharding, > distributed transactions, and distributed database management > > ## Issues: > No. > > ## Membership Data: > Apache ShardingSphere was founded 2020-04-15 (2 months ago) > There are currently 25 committers and 14 PMC members in this project. > The Committer-to-PMC ratio is roughly 7:4. > > Community changes, past quarter: > - No new PMC members (project graduated recently). > - No new committers were added. > > ## Project Activity: > Software development activity: > > - We are preparing to release the bug fix release 4.1.1. > - We have added support for pluggable architecture in our master branch. > - We are designing the new API for version 5.x. > - We accepted the donation from ElasticJob (a distribute scheduler > framework) as a new scheduler solution. > I think the more accurate statement is We have voted for accepting..., and passed. The IP clearance has been sent to the incubator. The IP clearance lazy consensus has not been done, right? Sheng Wu 吴晟 Twitter, wusheng1108 > > ## Community Health: > Overall community health is good. The mailing list decreased 29% because > after graduation, more contributors focus development tasks on GitHub, > issues, pull requests, contributors are still increasing rapidly. > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [Vote] ElasticJob donation
+1 binding, good luck. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年5月24日周日 下午9:56写道： > Hi ShardingSphere community, > > After we discuss fully about donate ElasticJob as a subproject of Apache > ShardingSphere in thread[1], I would like to start vote. > > Voting will start now (May. 24th date) and will remain open for at least 72 > hours, Request all PMC members to give their vote. > [ ] +1 Agree with donate ElasticJob as a subproject of Apache > ShardingSphere. > [ ] +0 No opinion. > [ ] -1 Do not agree because > > [1] > > https://lists.apache.org/thread.html/rd6171e2065be6bcfbeb7aba7e5c876eeed04db585c6ab78fc03a581c%40%3Cdev.shardingsphere.apache.org%3E > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [Proposal] ElasticJob donation
zhangli...@apache.org 于2020年5月21日周四 下午11:16写道： > Thank you for reminder. > > I update the wiki for: > > 1. Revise PPMC to PMC > 2. Add elastic-job-cloud into donation list because I think keep all things > is better for ElasticJob. > > For ICLA issue, I review the contributor list carefully, There are 4 people > signed ICLA already, they are Liang Zhang, Hao Cao, Hongtao Gao, Guangyun > Li. The Top 6 contributors commit more than 2 times, so I want get ICLA > from them. > I will contact Xinguo Zhang and Sean Wang later. > > > > What concerns me a bit is that the core committer is only one person, > Liang Zhang (Please correct if I missed something). > > > +1 from me too. A little concern only. > > Because other contributors are not active in apache community. After > ElasticJob become as a sub-project of Apache ShardingSphere, we need > to attract more active contributors and rebuild the community. > Once the PMC agrees to accept this workload, this should not be a block. Personally, I have a little concern only. Leave this to other PMC members, who are more active and maintaining the codes. I will follow their choices. Sheng Wu 吴晟 Twitter, wusheng1108 > > ------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年5月21日周四 下午8:54写道： > > > Inline. > > > > > > zhangli...@apache.org 于2020年5月21日周四 下午5:47写道： > > > > > Hi ShardingSphere commnuty, > > > > > > The ElasticJob donation proposal is posted on > > > > > > > > > https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ElasticJob+Donation+Proposal > > > > > > The discuss of donation ElasticJob as a subproject is in > > > https://github.com/elasticjob/elastic-job-lite/issues/728 > > > > > > I just paste to proposal to here: > > > > > > > > > > > > ElasticJob Donation Proposal > > > > > > # Abstract > > > > > > ElasticJob[1] is a distributed scheduling solution which is a suitable > > > framework for Apache ShardingSphere[2] scaling data migration jobs. > > > This project is supported By Dangdang and builds with Java. > > > Elastic-Job is a lightweight, decentralized solution that provides > > > distributed task sharding services. > > > > > > # Proposal > > > > > > The goal of this proposal is to bring the existing ElasticJob codebase, > > > developers and community into the Apache Software Foundation (ASF) as > > > ShardingSphere's sub-project. > > > This project started in Open Source on Github nearly 5 years. > > > ElasticJob is submitting this proposal to donate it to the Apache > > > ShardingSphere Incubator under the Apache License, Version 2.0, in > order > > to > > > replace the existing scheduler framework. > > > These artifacts are currently available on GitHub at > > > https://github.com/elasticjob/elastic-job-lite. > > > > > > # Background > > > > > > ShardingSphere is a excellent distributed database middleware and have > > many > > > open source users at domestic and abroad. > > > But the current scheduler of data scaling can not support sharding and > > > distribute job. > > > The project ElasticJob is another open source project which established > > by > > > Apache ShardingSphere's VP Liang Zhang on 2014. > > > Just like data sharding with Apache ShardingSphere, ElasticJob focused > on > > > job sharding. The feature of current job scheduler of scaling is too > > simple > > > and can not afford data migrate distribute job to . So Liang Zhang > decide > > > bring ElasticJob as a sub-project to provide distribute scheduler > > > supporting. > > > > > > # Current status > > > > > > ElasticJob has no updated during previous 2 years because Liang Zhang > do > > > not have time to maintain the community. But it still has lots of users > > > using ElasticJob in China. We think bring ElasticJob into Apache > > > ShardingSphere community can help the project growth up. > > > > > > # Core developer > > > > > > Liang Zhang is an experienced open source developer and ShardingSphere > > VP. > > > > > > # Donation source > > > > > > Github repo: > > > https://github.com/elasticjob/elastic-job-lite > > > https://github.com/elasticjob/elastic-job-cloud (Do not donation > because > > > it > > > is not suitable
Re: [Proposal] ElasticJob donation
Inline. zhangli...@apache.org 于2020年5月21日周四 下午5:47写道： > Hi ShardingSphere commnuty, > > The ElasticJob donation proposal is posted on > > https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ElasticJob+Donation+Proposal > > The discuss of donation ElasticJob as a subproject is in > https://github.com/elasticjob/elastic-job-lite/issues/728 > > I just paste to proposal to here: > > > > ElasticJob Donation Proposal > > # Abstract > > ElasticJob[1] is a distributed scheduling solution which is a suitable > framework for Apache ShardingSphere[2] scaling data migration jobs. > This project is supported By Dangdang and builds with Java. > Elastic-Job is a lightweight, decentralized solution that provides > distributed task sharding services. > > # Proposal > > The goal of this proposal is to bring the existing ElasticJob codebase, > developers and community into the Apache Software Foundation (ASF) as > ShardingSphere's sub-project. > This project started in Open Source on Github nearly 5 years. > ElasticJob is submitting this proposal to donate it to the Apache > ShardingSphere Incubator under the Apache License, Version 2.0, in order to > replace the existing scheduler framework. > These artifacts are currently available on GitHub at > https://github.com/elasticjob/elastic-job-lite. > > # Background > > ShardingSphere is a excellent distributed database middleware and have many > open source users at domestic and abroad. > But the current scheduler of data scaling can not support sharding and > distribute job. > The project ElasticJob is another open source project which established by > Apache ShardingSphere's VP Liang Zhang on 2014. > Just like data sharding with Apache ShardingSphere, ElasticJob focused on > job sharding. The feature of current job scheduler of scaling is too simple > and can not afford data migrate distribute job to . So Liang Zhang decide > bring ElasticJob as a sub-project to provide distribute scheduler > supporting. > > # Current status > > ElasticJob has no updated during previous 2 years because Liang Zhang do > not have time to maintain the community. But it still has lots of users > using ElasticJob in China. We think bring ElasticJob into Apache > ShardingSphere community can help the project growth up. > > # Core developer > > Liang Zhang is an experienced open source developer and ShardingSphere VP. > > # Donation source > > Github repo: > https://github.com/elasticjob/elastic-job-lite > https://github.com/elasticjob/elastic-job-cloud (Do not donation because > it > is not suitable for ShardingSphere now) > If this is not a part of the donation, it should not be listed as a part of the proposal. This is misleading. What is the expectation of this repo? As it is still using the elasticjob repo and elastic-job- prefix? https://github.com/elasticjob/elastic-job-doc > https://github.com/elasticjob/elastic-job-example > > # Source and Intellectual Property Submission Plan > > ElasticJob was originally created by Liang Zhang in Dec 2014. So, He was > the creator and main contributor of ElasticJob. The project major > contributors are Liang Zhang and Hao Cao. Both of them are ShardingSphere > PPMC members, ICLAs are submitted. And have no others ICLA need to be > PPMC is not the right term, I think you mean PMC member? More importantly, I don't agree the project only has two major contributors, this is the data showing on the Github contributor page of the elastic-job-lite repo There are 6 people having 100+ LOC contributions, 10 people have more than one commits. We could not expect we have all ICLA from all of them, but the description is not accurate about `major`. We should try to get as many ICLA as possible. > submitted. > > At last, the SGA will be provided by Dangdang. > > # External Dependencies > > ## Apache-2.0 licenses > > - commons-lang3 > - commons-codec > - commons-exec > - commons-dbcp > - curator > - guava > - gson > - quartz > - jetty > - unitils > - springframework > > ## MIT licenses > > - lombok > - mockito > - slf4j > > ## EPL-1.0 licenses > > - aspectj > - logback > - junit > - h2 > > ## CDDL 1.1 > > - jersey > > ## GPL-2.0 > > - mysql for provided only > > # Required Resources > > Git Repositories: > > - https://github.com/elasticjob/elastic-job-lite.git > - https://github.com/elasticjob/elastic-job-doc.git > - https://github.com/elasticjob/elastic-job-example.git I think these are wrong, I think these should be the expected resources in the ASF. And which issue tracker are you planning to do? > What concerns me a bit is that the core committer is only one person, Liang Zhang (Please correct if I missed something). +1 from me too. A little concern only. Sheng Wu > > > > [1] https://github.com/elasticjob > [2] https://github.com/apache/shardingsphere > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Incubator status updated
Hi I just updated the incubator status of ShardingSphere, on the SVN. After the refresh period, we should be able to see the status changed https://incubator.apache.org/projects/shardingsphere.html These changes are originally done by Liang Zhang, I just helped on pushing to SVN due to privilege requirements. Sheng Wu 吴晟 Twitter, wusheng1108
Re: [DISCUSS]About a hotfix release version 4.1.1
hotfix for a blocking issue, makes sense to me. Sheng Wu 吴晟 Twitter, wusheng1108 KimmKing 于2020年5月14日周四 下午2:46写道： > Hi, community. > After the latest version 4.1.0 release, there is a bug[1] found > during loading Oracle tables metadata and cause sharding-jdbc/proxy can't > bootstrap. > And it had fixed in master by a community contributor now [2]. > So, we should consider about a hotfix release version 4.1.1, fix it > to backport 4.x, and make sure Oracle env users can be use this coming > version. > > > Any suggestion/idea is welcome. > > > [1].https://github.com/apache/shardingsphere/issues/5581 > [2].https://github.com/apache/shardingsphere/pull/5436 > >
Re: Draft of ShardingSphere Board Report for May 2020
Good to me. Thanks Liang. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年5月7日周四 下午4:19写道： > Hi All, > > The Draft of ShardingSphere Board Report for May 2020 is below, please > advice if I missed anything. > > -- > > ## Description: > The mission of Apache ShardingSphere is the creation and maintenance of > software related to a database clustering system providing data sharding, > distributed transactions, and distributed database management > > ## Issues: > There are no issues requiring board attention. > > ## Membership Data: > Apache ShardingSphere was founded 2020-04-15 (22 days ago) > There are currently 25 committers and 14 PMC members in this project. > The Committer-to-PMC ratio is roughly 7:4. > > Community changes, past quarter: > - No new PMC members (project graduated recently). > - No new committers were added. > > ## Project Activity: > Apache ShardingSphere just completed the release process for 4.0.1 and > 4.1.0. > 4.0.1 carrying a number of bug fixes; 4.1.0 contained a few new features. > > At this time, we are focusing on the big release of 5.x, > this version contains some major shifts in thinking about the project > - specifically, 5.x looks to achieve these goals: > > - Provide a micro and pluggable kernel to load features by java SPI. > - Redesign API to adaptor new kernel. > - Provide an independent SQL parser SDK. > > > ## Community Health: > Apache ShardingSphere still in the rapid develop mode, > there are explosive growth for issues and pull requests > because of Apache ShardingSphere become TLP. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [SHARDING-SCALING]Optimization about job start API
I think qq mail box and some mail local tool have this issue. Gmail showing
them.
Sheng Wu 吴晟
Twitter, wusheng1108
sushixiang 于2020年4月30日周四 上午8:58写道：
> Sorry, I don't know why the blanksturn into nbsp;.
>
>
>
>
> --Original--
> From:"KimmKing" Date:Wed, Apr 29, 2020 07:24 PM
> To:"dev" birdyan...@163.com;
>
> Subject:Re:[SHARDING-SCALING]Optimization about job start API
>
>
>
> a text format mail is better.
>
>
>
>
>
> At 2020-04-29 13:35:13, "sushixiang" Hi everyone,nbsp;
> As we know, sharding-scaling can be used for migrating data from
> single datasource to ShardingSphere when first using
> ShardingSphere,nbsp;and the start API is showed below:
>
>
> curl -X POST \
> nbsp; http://localhost:/shardingscaling/job/start \
> nbsp; -H 'content-type: application/json' \
> nbsp; -d '{
> nbsp; nbsp;"ruleConfiguration": {
> nbsp; nbsp; nbsp; "sourceDatasource": "ds_0:
> !!YamlDataSourceConfiguration\nnbsp; dataSourceClassName:
> com.zaxxer.hikari.HikariDataSource\nnbsp; properties:\nnbsp;
> nbsp; jdbcUrl: jdbc:mysql://
> 127.0.0.1:3306/test?serverTimezone=UTCamp;useSSL=false\nnbsp
> <http://127.0.0.1:3306/test?serverTimezone=UTCamp;useSSL=false%5Cnnbsp>;
> nbsp; username: root\nnbsp; nbsp; password:
> '\''123456'\''\nnbsp; nbsp; connectionTimeout: 3\nnbsp;
> nbsp; idleTimeout: 6\nnbsp; nbsp; maxLifetime:
> 180\nnbsp; nbsp; maxPoolSize: 50\nnbsp; nbsp;
> minPoolSize: 1\nnbsp; nbsp; maintenanceIntervalMilliseconds:
> 3\nnbsp; nbsp; readOnly: false\n",
> nbsp; nbsp; nbsp; "sourceRule": "tables:\nnbsp;
> t_order:\nnbsp; nbsp; actualDataNodes: ds_0.t_order\nnbsp;
> nbsp; tableStrategy:\nnbsp; nbsp; nbsp; none",
> nbsp; nbsp; nbsp; "destinationDataSources": {
> nbsp; nbsp; nbsp; nbsp; nbsp;"name": "dt_0",
> nbsp; nbsp; nbsp; nbsp; nbsp;"password":
> "123456",
> nbsp; nbsp; nbsp; nbsp; nbsp;"url":
> "jdbc:mysql://127.0.0.1:3306/test2?serverTimezone=UTCamp;useSSL=false
> ",
> nbsp; nbsp; nbsp; nbsp; nbsp;"username":
> "root"
> nbsp; nbsp; nbsp; }
> nbsp; nbsp;},
> nbsp; nbsp;"jobConfiguration": {
> nbsp; nbsp; nbsp; "concurrency": 3
> nbsp; nbsp;}
> }'
>
>
>
> But I think the configuration may be much complex for the fisrt use,
> if we need migrate all tables from the source database, we should config
> all tables in the 'sourceRule' item, and for first use, we may not have the
> concept of table rules.
>
>
> So, I think a simpler configuration may be needed, not only the first
> data migrate scenario, does anyone has some suggestions about it?
>
>
> All data migrate scenarios can refer the link:nbsp;
> https://shardingsphere.apache.org/document/current/en/features/sharding-scaling/core-features/
Re: Re: Re: [DISCUSS]About metrics feature
Here it is, https://docs.google.com/document/d/1biRE3Bc0cTbs7qnBozUuAxCmeP5n8y0JKJAyzqitLnM/edit?urp=gmail_link#heading=h.1a769t91apcq The API usage PR is this, https://github.com/apache/skywalking/pull/4694 If you have any questions, welcome to join us Tuesday night bi-weekly meeting. You could find the information on the skywalking dev mail list. Sheng Wu 吴晟 Twitter, wusheng1108 KimmKing 于2020年4月26日周日 上午11:27写道： > Thanks, Sheng. > By the way, do you have a plan, this metric feature will be released > in which incoming version. > And where I can get the google docs for SkyWalking Meter System > details. > > > > >: ) > > > 在 2020-04-25 15:51:02，"Sheng Wu" 写道： > >I think we have recorded Chinese Online discussion about this, > >https://www.bilibili.com/video/BV15Z4y147mf. > >Welcome to watch and provide feedback. If you need more helps, let me know > > > >Sheng Wu 吴晟 > >Twitter, wusheng1108 > > > > > >KimmKing 于2020年4月25日周六 下午3:29写道： > > > >> It's a good news. > >> We will follow it. > >> > >> At 2020-04-23 20:04:31, "Sheng Wu" wrote: > >> >Metrics features are more about internal key points, the outside > >> >integrations are clear, Prometheus, or micrometer. BTW, SkyWalking will > >> >have an online meeting to discuss metrics/meter systems in SkyWalking > 8. > >> > > >> >Sheng Wu 吴晟 > >> >Twitter, wusheng1108 > >> > > >> > > >> >KimmKing 于2020年4月23日周四 下午6:21写道： > >> > > >> >> Hi, community: > >> >> We know there are three important parts of observability with modern > >> >> distributed system: logging, metric and tracing. > >> >> The tracing feature for observability in ShardingSphere components, > >> >> logging feature is easy to gain via some tools such like ELK.And it's > >> the > >> >> time to design and implement metrics feature now. Finally we get a > >> complete > >> >> observability with UI console(integration with promethus/grafana). > >> >> So we will launch this mission for the certain tasks about metrics. > >> >> @yu199195 will be in charge of them. > >> >> > >> >> > >> >> Any ideas and questions are welcome here. > >> >
Re: Re: [DISCUSS]About metrics feature
I think we have recorded Chinese Online discussion about this, https://www.bilibili.com/video/BV15Z4y147mf. Welcome to watch and provide feedback. If you need more helps, let me know Sheng Wu 吴晟 Twitter, wusheng1108 KimmKing 于2020年4月25日周六 下午3:29写道： > It's a good news. > We will follow it. > > At 2020-04-23 20:04:31, "Sheng Wu" wrote: > >Metrics features are more about internal key points, the outside > >integrations are clear, Prometheus, or micrometer. BTW, SkyWalking will > >have an online meeting to discuss metrics/meter systems in SkyWalking 8. > > > >Sheng Wu 吴晟 > >Twitter, wusheng1108 > > > > > >KimmKing 于2020年4月23日周四 下午6:21写道： > > > >> Hi, community: > >> We know there are three important parts of observability with modern > >> distributed system: logging, metric and tracing. > >> The tracing feature for observability in ShardingSphere components, > >> logging feature is easy to gain via some tools such like ELK.And it's > the > >> time to design and implement metrics feature now. Finally we get a > complete > >> observability with UI console(integration with promethus/grafana). > >> So we will launch this mission for the certain tasks about metrics. > >> @yu199195 will be in charge of them. > >> > >> > >> Any ideas and questions are welcome here. >
Re: [Zoom Meeting] SkyWalking Meter System Prototype Discussion
Forward to ShardingSphere, since you are asking about the metrics just a moment ago. Sheng Wu 吴晟 Twitter, wusheng1108 Sheng Wu 于2020年4月23日周四 下午8:13写道： > Hi Dev Team > > The meter system has been designed and implemented in PR[1]. We will host > a zoom meeting to discuss the details, focusing on Prometheus and also > about Micrometer. > > I will give the introduction about the APIs and my idea, we could do free > discussion about that. > The meeting time is 230PM-330PM tomorrow. > > - > Sheng Wu is inviting you to a scheduled Zoom meeting. > > Topic: SkyWalking Meter System Prototype Discussion > Time: Apr 24, 2020 02:30 PM Beijing, Shanghai > > Join Zoom Meeting > https://zoom.com.cn/j/6112980?pwd=S1lVVlVkQWNJN3lra1crNUFmMFNpZz09 > > Meeting ID: 611 2987 7770 > Password: 046131 > One tap mobile > +85258086088,,6112980#,,#,046131# Hong Kong, China > +85258033730,,6112980#,,#,046131# Hong Kong, China > > Dial by your location > +852 5808 6088 Hong Kong, China > +852 5803 3730 Hong Kong, China > +852 5803 3731 Hong Kong, China > +1 408 638 0968 US (San Jose) > +1 646 558 8656 US (New York) > Meeting ID: 611 2987 7770 > Password: 046131 > Find your local number: https://zoom.com.cn/u/ic58XCYbXg > - > > [1] https://github.com/apache/skywalking/pull/4694 > > > Sheng Wu 吴晟 > Twitter, wusheng1108 >
Re: [DISCUSS]About metrics feature
Metrics features are more about internal key points, the outside integrations are clear, Prometheus, or micrometer. BTW, SkyWalking will have an online meeting to discuss metrics/meter systems in SkyWalking 8. Sheng Wu 吴晟 Twitter, wusheng1108 KimmKing 于2020年4月23日周四 下午6:21写道： > Hi, community: > We know there are three important parts of observability with modern > distributed system: logging, metric and tracing. > The tracing feature for observability in ShardingSphere components, > logging feature is easy to gain via some tools such like ELK.And it's the > time to design and implement metrics feature now. Finally we get a complete > observability with UI console(integration with promethus/grafana). > So we will launch this mission for the certain tasks about metrics. > @yu199195 will be in charge of them. > > > Any ideas and questions are welcome here.
Re: Congratulations! The board made ShardingSphere TLP today
Yes!! Congrats to all! Sheng Wu 吴晟 Twitter, wusheng1108 Craig Russell 于2020年4月16日周四 上午9:19写道： > ShardingSphere is now officially an Apache Project! > > Champagne! Balloons! Parades! Dragons! > > Best, > Craig > > Craig L Russell > c...@apache.org > >
Re: [RESULT] [VOTE] Graduate Apache ShardingSphere (incubating)
Congrats to the community. The vote passed. Mentors, I have added the `Establish ShardingSphere` into the next month's board agenda. Good luck, look forward to the good news. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年3月28日周六 下午12:45写道： > With 6 +1 non-binding votes, 10 +1 binding votes and no -1 or +/-0 votes, > this vote PASSES. > Thanks to everyone who voted. The vote tally is attached. > > Non-binding: > Lidong Dai > Ming Wen > Xiangdong Huang > Xin Wang > Zili Chen > Zhongyi Tan > > Binding: > Sheng Wu > Tianqi Chen > Ted Liu > Kevin Ratnasekera > Byung-Gon Chun > Willem Jiang > Liang Chen > ShaoFeng Shi > Junping Du > Gosling Von > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [DISCUSS] 4.1.0 release plan
I think this isn't requiring a vote :) It is just a feature, you could run this differently, as this has no side effect. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年3月26日周四 下午1:38写道： > Hi > > > Since ShardingProxy docker can not load libs(Especially > mysql-connector-java.jar) from the external directory, users can not start > ShardingProxy docker with MySQL databases.[1] > Considering the broad adoption of MySQL, it is not a minor issue, I think. > I'd like to listen to the community's voice about this issue. > > > https://github.com/apache/incubator-shardingsphere/issues/4919 > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 03/26/2020 12:32，Zhang Yonglun wrote： > The release would be like this after update: > > New Features > > - Support scaling for ShardingSphere (alpha version) > - Move etcd registry center from experiment repo to apache repo > - Upgrade to Java 8 > > > Enhancement > > - Optimization for Sharing Parser with ANTLR Visitor improving the parsing > performance of long SQL by 100%~1000% > - Use multiple threads to load metadata for different data sources > - Support `allow.range.query.with.inline.sharding` option > > > Refactor > > - Migrate LeafKeyGenerator and remove distributedLock > > > Bug Fixes > > - Fix an exception caused by using a CHAR/VARCHAR type column as a order by > item > - Refine `DataTypeName` syntax rules of all database dialects > - Fix an exception caused by executing `BEGIN` using prepared statement of > MySQL C API > - Fix the problem that `ALTER TABLE` fails to execute when the field type > of the table contains Integer/Double/BigDecimal > - Fix the problem of the stop index dislocation of segment with alias > - Fixed the problem that overwriting SQL `SELECT * FROM tbl WHERE > encrypt_col = ? AND (sharding_key = ? OR sharding_key =?)` when using > sharding + encrypt would throw StringIndexOutOfBoundsException > - Fixed the problem of incorrect decoding after AES encoding when using > Sharding-Proxy in Spring Boot > > > Please feel free to leave comments. > -- > > Zhang Yonglun > Apache ShardingSphere > > > Zhang Yonglun 于2020年3月17日周二 下午12:30写道： > > Hi ShardingSphere community, > > I'm preparing a new release of ShardingSphere 4.x. The new release include > a couple significant updates, so the version will be 4.1.0. > > The target tag is > https://github.com/apache/incubator-shardingsphere/tree/dev-5.x which > include many bug fixes, enhancement and refactor. > > All updatas can be found in > > https://github.com/apache/incubator-shardingsphere/issues?q=is%3Aissue+milestone%3A5.0.0+ > . > > After reviewing those issues, the major items in our next release note > would be: > > - Support scaling for shardingsphere > - Optimization for Sharing Parser with ANTLR Visitor for MySQL > - Parsing SubQuery > - Upgrade to Java 8 > - Redesign class domain of parser module > - Create database protocol module > - Create new module for shardingsphere-sql-parse-binder > - Refactor orchestration center interface > - Improve integrate SQL parser test engine > - Decouple UI and ShardingSphere > > 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. > -- > > Zhang Yonglun > Apache ShardingSphere > >
Re: [DISCUSS] Enhancement for Apache ShardingProxy to serve well as a backend server for Apache Skywalking
Thanks for the update. Keep us posted. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年3月24日周二 下午6:27写道： > > > Hi Skywalking and ShardingSphere community, > > > Since there is a blocker to make ShardingProxy served as a backend server > for Skywalking[1], > I have to firstly handle this issue[2] that ShardingProxy can not load > `shardingAlgorithm.jar` from an external path. > Some rough ideas came up to my mind, but time is needed to carry out, so > please wait for my good news. > > > I will give the update here later. Welcome your comments. > > > [1] > https://lists.apache.org/thread.html/r4b49739a1ca9b844a67f4ed8411beca4aa598d78911e2e2f21f367a5%40%3Cdev.skywalking.apache.org%3E > [2]https://github.com/apache/incubator-shardingsphere/issues/4919 > > > Cheers, > Trista > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > >
Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP
For me, yes. Sheng Wu 吴晟 Twitter, wusheng1108 Craig Russell 于2020年3月23日周一 上午10:35写道： > Apache ShardingSphere ... related to a database clustering system > providing data sharding, distributed transactions, and distributed database > management. > > General enough, but specific enough? > > Craig > > > On Mar 22, 2020, at 5:43 PM, Sheng Wu wrote: > > > > zhangli...@apache.org 于2020年3月18日周三 下午1:11写道： > > > >> Roger. > >> > >> How about use project description below to the board? > >> > >> Apache ShardingSphere is related to database middleware providing data > >> sharding, distributed transactions and distributed governance. > >> > > > > Hi Liang, Juan and Craig > > > > This is my idea. > > Apache ShardingSphere is a database clustering system providing data > > sharding, distributed transaction, and data(or Database?) management. > > > > My points are > > 1. The world `middleware` is not clear as ShardingSphere as it provides > > both embedded lib and proxy mode. > > 2. distributed governance and orchestration are not clear too. Due to we > > are going to accept more features, such as scaling out(right?), data > > management makes more sense to me. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > >> > >> -- > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> Craig Russell 于2020年3月18日周三 上午6:16写道： > >> > >>> Hi, > >>> > >>> In my opinion, this is way too wordy for a description of the project. > >> How > >>> about > >>> > >>> ... related to database middleware providing data sharding, > heterogeneous > >>> database support, and distributed transactions for Java application > >>> development. > >>> > >>> Other functionality descriptions can be added but maybe we can start > >>> editing this? > >>> > >>> Regards, > >>> Craig > >>> > >>>> On Mar 9, 2020, at 7:14 AM, zhangli...@apache.org wrote: > >>>> > >>>> WHEREAS, the Board of Directors deems it to be in the best interests > of > >>>> the Foundation and consistent with the Foundation's purpose to > >> establish > >>>> a Project Management Committee charged with the creation and > >> maintenance > >>>> of open-source software, for distribution at no charge to the public, > >>>> related to Apache ShardingSphere is an ecosystem consisted of a set of > >>>> distributed database middleware solutions, including 2 independent > >>>> products, Sharding-JDBC, Sharding-Proxy. They all provide functions of > >>>> data sharding, distributed transaction, database and data governance, > >>>> applicable in a variety of situations such as Java isomorphism and > >>>> heterogeneous language.. > >>> > >>> Craig L Russell > >>> c...@apache.org > >>> > >>> > >> > > Craig L Russell > c...@apache.org > >
Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP
zhangli...@apache.org 于2020年3月18日周三 下午1:11写道： > Roger. > > How about use project description below to the board? > > Apache ShardingSphere is related to database middleware providing data > sharding, distributed transactions and distributed governance. > Hi Liang, Juan and Craig This is my idea. Apache ShardingSphere is a database clustering system providing data sharding, distributed transaction, and data(or Database?) management. My points are 1. The world `middleware` is not clear as ShardingSphere as it provides both embedded lib and proxy mode. 2. distributed governance and orchestration are not clear too. Due to we are going to accept more features, such as scaling out(right?), data management makes more sense to me. Sheng Wu 吴晟 Twitter, wusheng1108 > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Craig Russell 于2020年3月18日周三 上午6:16写道： > > > Hi, > > > > In my opinion, this is way too wordy for a description of the project. > How > > about > > > > ... related to database middleware providing data sharding, heterogeneous > > database support, and distributed transactions for Java application > > development. > > > > Other functionality descriptions can be added but maybe we can start > > editing this? > > > > Regards, > > Craig > > > > > On Mar 9, 2020, at 7:14 AM, zhangli...@apache.org wrote: > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > the Foundation and consistent with the Foundation's purpose to > establish > > > a Project Management Committee charged with the creation and > maintenance > > > of open-source software, for distribution at no charge to the public, > > > related to Apache ShardingSphere is an ecosystem consisted of a set of > > > distributed database middleware solutions, including 2 independent > > > products, Sharding-JDBC, Sharding-Proxy. They all provide functions of > > > data sharding, distributed transaction, database and data governance, > > > applicable in a variety of situations such as Java isomorphism and > > > heterogeneous language.. > > > > Craig L Russell > > c...@apache.org > > > > >
Re: Is ShardingSphere(version 4.0.0/4.0.1) adapt to skywalking agent？
I think that depends on Yonglun Zhao's schedule. No SkyWalking committer is working on this. Sheng Wu 吴晟 Twitter, wusheng1108 Sanmu Wang 于2020年3月12日周四 下午3:46写道： > Is there any plan for new plugins? > > Sheng Wu 于2020年3月12日周四 下午2:59写道： > > > I think SkyWalking doesn't support those two versions. ShardingSphere > > changed internal mechanism which broke the prev plugins, but new plugins > > have not been provided yet. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Sanmu Wang 于2020年3月12日周四 下午2:51写道： > > > > > Hi all. > > > > > > > > > > > > Is Skywalking java agent support ShardingProxy and ShardingJDBC > (version > > > 4.0.0 and 4.0.1) for now? I found issue [1] and [2] still open on > > > skywalking GitHub. Is there any best practices for us to use > > ShardingProxy > > > with skywalking agent? > > > > > > > > > > > > ISSUE [1]: https://github.com/apache/skywalking/issues/4229 > > > > > > ISSUE [2]: https://github.com/apache/skywalking/issues/4131 > > > > > >
Re: Is ShardingSphere(version 4.0.0/4.0.1) adapt to skywalking agent？
I think SkyWalking doesn't support those two versions. ShardingSphere changed internal mechanism which broke the prev plugins, but new plugins have not been provided yet. Sheng Wu 吴晟 Twitter, wusheng1108 Sanmu Wang 于2020年3月12日周四 下午2:51写道： > Hi all. > > > > Is Skywalking java agent support ShardingProxy and ShardingJDBC (version > 4.0.0 and 4.0.1) for now? I found issue [1] and [2] still open on > skywalking GitHub. Is there any best practices for us to use ShardingProxy > with skywalking agent? > > > > ISSUE [1]: https://github.com/apache/skywalking/issues/4229 > > ISSUE [2]: https://github.com/apache/skywalking/issues/4131 >
Re: Talking about remove branch proxy-with-netty-backend
Good for me, Remove please. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年3月10日周二 下午1:41写道： > The branch proxy-with-netty-backend is a too old branch which is > establishing before we enter incubator. > This branch is for using netty to connect MySQL. The feature is not > completed and it seems no further update plan by the author. It is > difficult to merge master now for code conflict reason. > > I want remove this branch. Any suggestions? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [VOTE] Graduate Apache ShardingSphere (incubating)
+1 Look forward to the ShardingSphere becomes to my 3rd involved TLP. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年3月5日周四 下午12:05写道： > Establish the Apache ShardingSphere Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to Apache ShardingSphere is an ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, Sharding-JDBC, Sharding-Proxy. They all provide functions of > data sharding, distributed transaction, database and data governance, > applicable in a variety of situations such as Java isomorphism and > heterogeneous language.. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache ShardingSphere Project", be and hereby > is established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache ShardingSphere Project be and hereby is > responsible for the creation and maintenance of software related to > Apache ShardingSphere is an ecosystem consisted of a set of distributed > database middleware solutions, including 2 independent products, > Sharding-JDBC, Sharding-Proxy. They all provide functions of data > sharding, distributed transaction, database and data governance, > applicable in a variety of situations such as Java isomorphism and > heterogeneous language.; and be it further > > RESOLVED, that the office of "Vice President, Apache ShardingSphere" be > and hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache > ShardingSphere Project, and to have primary responsibility for > management of the projects within the scope of responsibility of the > Apache ShardingSphere Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache ShardingSphere > Project: > > * Craig L Russell > * Hao Cao > * Hongjun Du > * Hongtao Gao > * Juan Pan > * Jun Zhao > * Liang Zhang > * QingYang Chen > * Sheng Wu > * Von Gosling > * Willem Ning Jiang > * Xiaoguang Ma > * Yang Yi > * Yonglun Zhang > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed to > the office of Vice President, Apache ShardingSphere, to serve in > accordance with and subject to the direction of the Board of Directors > and the Bylaws of the Foundation until death, resignation, retirement, > removal or disqualification, or until a successor is appointed; and be > it further > > RESOLVED, that the Apache ShardingSphere Project be and hereby is tasked > with the migration and rationalization of the Apache Incubator > ShardingSphere podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > ShardingSphere podling encumbered upon the Apache Incubator PMC are > hereafter discharged. > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Strange 3rd party service. We may could send a mail to ask what the service vendor could do to fix this? But at least, this doesn't look like a block to me. I think basically, we could start the official vote on the dev for graduation? PPMC and dev team, WDYT? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年3月4日周三 下午2:39写道： > I check the website https://jitpack.io, it looks like they[1] crawling the > releases from GitHub directly, and then shade the groupId and artifactId by > their own rule. > The repo `dangdangdotcom/sharding-jdbc` is the previous repo before > entering incubator, we just transferred the repo to > `apache/incubator-shardingsphere` now. > But jitpack may has a bug, they can not recognize the transferred repo. > > I check the release build log[1], the build is come from apache repo. After > building finish totally, shade the package name. Please see details below: > > ``` > > [INFO] sharding-ui-distribution ... SUCCESS [ > 0.690 s] > [INFO] sharding-integration-test .. SUCCESS [ > 0.145 s] > [INFO] sharding-jdbc-test . SUCCESS [ > 0.527 s] > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 05:06 min > [INFO] Finished at: 2019-12-27T07:30:17Z > [INFO] > > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 > -Dhttps.protocols=TLSv1.2 > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; > support was removed in 8.0 > Found module: org.apache.shardingsphere:shardingsphere:4.0.0 > ... > > Build tool exit code: 0 > Looking for artifacts... > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 > -Dhttps.protocols=TLSv1.2 > Looking for pom.xml in build directory and ~/.m2 > Found artifact: org.apache.shardingsphere:shardingsphere:4.0.0 > 2019-12-27T07:30:34.790832592Z > Exit code: 0 > > Build artifacts: > com.github.dangdangdotcom.sharding-jdbc:sharding-proxy-distribution:4.0.0 > > com.github.dangdangdotcom.sharding-jdbc:shardingsphere-sql-parser-sqlserver:4.0.0 > > com.github.dangdangdotcom.sharding-jdbc:sharding-orchestration-reg-nacos:4.0.0 > ... > > ``` > > Could we just leave them there, any advice? > > [1] https://jitpack.io/p/dangdangdotcom/sharding-jdbc > [2] > https://jitpack.io/com/github/dangdangdotcom/sharding-jdbc/4.0.0/build.log > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan 于2020年3月4日周三 下午1:29写道： > > > Hi Justin, > > > > > > Thanks for your prompt feedback, which always provides us valuable > > instructions. > > It seems like items currently remaining Errata is not a big issue, and > the > > more critical case is the brand thing. Besides, to make the website more > > 'Apache' is another improvement. Make sense, and we will look into two > of > > them. > > > > > > Best wishes, > > Trista > > > > > > Juan Pan (Trista) > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > E-mail: panj...@apache.org > > > > > > > > > > On 03/4/2020 12:18，Justin Mclean wrote： > > Hi, > > > > IMO it's not immediately obvious from the project web site that this is > an > > Apache project. It probably meets the minimum requirements but it would > be > > nice to see more than that. > > > > Thanks, > > Justin > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Good to me. Justin, what do you think? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月26日周三 上午11:47写道： > The projects of OpenSharding repo[1] are some extensions and plugins of > ShardingSphere, they have license and copyright issues which are not > suitable for apache project. > > I have already remove the logo, organization description, website and mail > list for this repo. > > This repo may regard as a third-party plugins of ShardingSphere, not > official ShardingSphere's repo. After we remove the information, this repo > has no relationship with ShardingSphere now. > > Any advice? > > [1] https://github.com/OpenSharding > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月26日周三 上午9:57写道： > > > Hi > > > > I have the same question, why it can't be closed? I look through the > > projects in it, it seems either example or plugin. Why should they move > > into the ASF repo? > > The other thing is the org avatar is a branding issue. Also with mail > > list/website referring to the ASF site, which is not right. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Justin Mclean 于2020年2月26日周三 上午8:04写道： > > > > > HI, > > > > > > > - Some remain codes[1] still using the old package name > > > > `io.shardingsphere`, we plan to rename them as `io.opensharding`. > > [DONE] > > > > > > Why not org.apache.shardingsphere? > > > > > > > > > > [1] https://github.com/OpenSharding > > > > > > This seems a little confusing "Distributed database middleware, repo > > > transfer to https://github.com/apache/incubator-shardingsphere;, if so > > > why has this not been closed down? > > > > > > Thanks, > > > Justin > > > > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Hi I have the same question, why it can't be closed? I look through the projects in it, it seems either example or plugin. Why should they move into the ASF repo? The other thing is the org avatar is a branding issue. Also with mail list/website referring to the ASF site, which is not right. Sheng Wu 吴晟 Twitter, wusheng1108 Justin Mclean 于2020年2月26日周三 上午8:04写道： > HI, > > > - Some remain codes[1] still using the old package name > > `io.shardingsphere`, we plan to rename them as `io.opensharding`. [DONE] > > Why not org.apache.shardingsphere? > > > > [1] https://github.com/OpenSharding > > This seems a little confusing "Distributed database middleware, repo > transfer to https://github.com/apache/incubator-shardingsphere;, if so > why has this not been closed down? > > Thanks, > Justin >
Re: [PROPOSAL]ShardingShpere Cloud on Kubernetes(SSCK)
I will try to catch up the meeting. Hongtao Gao 于2020年2月21日 周五上午12:06写道： > And I schedule a call to share the details of this proposal in person. > Welcome everyone who interested in this project. > > Hongtao Gao is inviting you to a scheduled Zoom meeting. > > Topic: Preview of ShardingSphere Cloud on Kubernetes > Time: Feb 21, 2020 02:00 PM Beijing, Shanghai > > Join Zoom Meeting > https://zoom.us/j/900429848 > > Meeting ID: 900 429 848 > > One tap mobile > +14086380968,,900429848# US (San Jose) > +16465588656,,900429848# US (New York) > > Dial by your location > +1 408 638 0968 US (San Jose) > +1 646 558 8656 US (New York) > Meeting ID: 900 429 848 > Find your local number: https://zoom.us/u/aed7GpCH74 > > Hongtao Gao 于2020年2月20日周四 下午11:58写道： > > > One suggestion is maybe we can consider about add a architecture diagram. > > > > > > I will add one soon. > > > > I fixed some typos base on google doc’s advice, and one item seems no > >> clue for me is that Sharding-Sidecar is still in our mind without any > >> progress. > > > > > > Thanks for your fix, really appreciate it. If Sharding-Sidecar is only a > > concept now, we may make it happen by leveraging Kubernetes. > > > > Also we should follow up sharding-sidecar to keep pace with SSCK. > >> Hope we can POC it in next few months. > > > > > > Yes, that's what I believe. Let's work together to make it happen. > > > > zhaojun 于2020年2月20日周四 下午11:44写道： > > > >> That’s a excellent idea ! > >> I have learned a lot from your proposal, cloud-native is currently one > >> of the biggest trends in the software industry. > >> It became clear that we can leverage Kubernetes resources and sdk to > >> develop SSCK. > >> Also we should follow up sharding-sidecar to keep pace with SSCK. > >> Hope we can POC it in next few months. > >> > >> -- > >> Zhao Jun (cherrylzhao) > >> Apache ShardingSphere & ServiceComb > >> > >> > On Feb 20, 2020, at 9:50 AM, Hongtao Gao wrote: > >> > > >> > Hongtao Gao > >> > 2019年11月26日周二 上午10:04 > >> > 发送至 dev > >> > Hi everyone > >> > > >> > I'm glad to share my proposal with you about to setup ShardingShpere > >> Cloud > >> > on Kubernetes(SSCK) project. > >> > > >> > The aim of SSCK is to enable users to configure and manage components > of > >> > ShardingShpere in Kubernetes Cluster. > >> > > >> > The following is the doc of this proposal. I'm hoping to hear thoughts > >> from > >> > you soon. > >> > > >> > [PROPOSAL]ShardingShpere Cloud on Kubernetes(SSCK) - > >> > > >> > https://docs.google.com/document/d/1Yixu9Mik9dkQdEzuJm1HCAmoPxjlGuEpKUfjFFD99O8/edit?usp=sharing > >> > > >> > > >> > -- > >> > Hongtao Gao > >> > > >> > Apache SkyWalking && Apache ShardingSphere > >> > Twitter, @hanahmily > >> > >> > > > > -- > > Hongtao Gao > > > > Apache SkyWalking && Apache ShardingSphere > > Twitter, @hanahmily > > > > > -- > Hongtao Gao > > Apache SkyWalking && Apache ShardingSphere > Twitter, @hanahmily > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: PMC and Committer list after graduation
>From LADP notification Benjamin Hindman has been removed from mentor list. What happens? Or he is willing to step down? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月17日周一 下午5:48写道： > OK. > > PMC: > > - Benjamin Hindman > - Craig L Russell > - Hao Cao > - Hongjun Du > - Hongtao Gao > - Juan Pan > - Jun Zhao > - Liang Zhang (VP) > - QingYang Chen > - Sheng Wu > - Von Gosling > - Willem Ning Jiang > - Xiaoguang Ma > - Yang Yi > - Yonglun Zhang > > Committers: > > - Guangyuan Wang > - Haisheng Sun > - Ling Yue > - Nicholas Jiang > - Qi Wang > - Ya Li > - Yanan Zhao > - YangWen Ou > - Zhiyi Yan > - Zonglei Dong > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月17日周一 下午5:39写道： > > > Hi > > > > I think you should list the names here, other contributors, and even > > committers can't access Roster. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年2月17日周一 下午5:31写道： > > > > > Hi PPMC and Committers, > > > > > > The final PMC and committer list are confirmed[1]. > > > > > > Please feel free to discuss the list if you have any advices. > > > > > > [1] https://whimsy.apache.org/roster/ppmc/shardingsphere > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: PMC and Committer list after graduation
+1 good for me. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月17日周一 下午5:48写道： > OK. > > PMC: > > - Benjamin Hindman > - Craig L Russell > - Hao Cao > - Hongjun Du > - Hongtao Gao > - Juan Pan > - Jun Zhao > - Liang Zhang (VP) > - QingYang Chen > - Sheng Wu > - Von Gosling > - Willem Ning Jiang > - Xiaoguang Ma > - Yang Yi > - Yonglun Zhang > > Committers: > > - Guangyuan Wang > - Haisheng Sun > - Ling Yue > - Nicholas Jiang > - Qi Wang > - Ya Li > - Yanan Zhao > - YangWen Ou > - Zhiyi Yan > - Zonglei Dong > > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月17日周一 下午5:39写道： > > > Hi > > > > I think you should list the names here, other contributors, and even > > committers can't access Roster. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年2月17日周一 下午5:31写道： > > > > > Hi PPMC and Committers, > > > > > > The final PMC and committer list are confirmed[1]. > > > > > > Please feel free to discuss the list if you have any advices. > > > > > > [1] https://whimsy.apache.org/roster/ppmc/shardingsphere > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: PMC and Committer list after graduation
Hi I think you should list the names here, other contributors, and even committers can't access Roster. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月17日周一 下午5:31写道： > Hi PPMC and Committers, > > The final PMC and committer list are confirmed[1]. > > Please feel free to discuss the list if you have any advices. > > [1] https://whimsy.apache.org/roster/ppmc/shardingsphere > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Thanks, Liang Zhang and Honglun. I think the next step is to prepare the graduation resolution from this page[1]? And ask all community to vote about that? [1] https://whimsy.apache.org/roster/ppmc/shardingsphere Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月17日周一 下午3:05写道： > All tasks finished, lists: > > - Remove author information in java code. [DONE] > > - Some remain codes[1] still using the old package name > `io.shardingsphere`, we plan to rename them as `io.opensharding`. [DONE] > > - Major contributors sign ICLA. [DONE] > > - Discuss PMC list. [DONE] > > - Update incubator status site[2]. [DONE] > > [1] https://github.com/OpenSharding > > [2] https://incubator.apache.org/projects/shardingsphere.html > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhangli...@apache.org 于2020年2月17日周一 下午3:02写道： > > > Done of remove author from java doc. > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > zhangli...@apache.org 于2020年2月17日周一 下午3:01写道： > > > >> > I found one missing step. > >> > The incubator status page[1] requires to update. Including the news > >> about > >> > new committer, PMC and release. > >> > >> > [1] https://incubator.apache.org/projects/shardingsphere.html > >> > >> SVN done, waiting for web-site update > >> > >> -- > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> Zhang Yonglun 于2020年2月17日周一 下午2:44写道： > >> > >>> > > >>> > - Some remain codes[1] still using the old package name > >>> > `io.shardingsphere`, we plan to rename them as `io.opensharding`. > >>> [TODO] > >>> > >>> > >>> I've just finished this part. All the remain tasks cleared now. > >>> > >>> -- > >>> > >>> Zhang Yonglun > >>> Apache ShardingSphere > >>> > >>> > >>> Zhang Yonglun 于2020年2月15日周六 下午8:35写道： > >>> > >>> > I will change the name `io.shardingsphere` to `io.opensharding` in > >>> > OpenSharding. > >>> > > >>> > -- > >>> > > >>> > Zhang Yonglun > >>> > Apache ShardingSphere > >>> > > >>> > > >>> > zhangli...@apache.org 于2020年2月15日周六 > 下午5:59写道： > >>> > > >>> >> Remain tasks: > >>> >> > >>> >> - Remove author information in java code. [TODO] > >>> >> > >>> >> - Some remain codes[1] still using the old package name > >>> >> `io.shardingsphere`, we plan to rename them as `io.opensharding`. > >>> [TODO] > >>> >> > >>> >> - Major contributors sign ICLA. [DONE] > >>> >> > >>> >> - Discuss PMC list. [DONE] > >>> >> > >>> >> > >>> >> [1] https://github.com/OpenSharding > >>> >> > >>> >> -- > >>> >> > >>> >> Liang Zhang (John) > >>> >> Apache ShardingSphere & Dubbo > >>> >> > >>> >> > >>> >> zhangli...@apache.org 于2020年2月15日周六 > 下午5:57写道： > >>> >> > >>> >> > > I am OK to remove them from the PMC list. But maybe keep them in > >>> the > >>> >> > committer? At least, they used to contribute to the community a > lot. > >>> >> > > >>> >> > Agree. > >>> >> > > >>> >> > -- > >>> >> > > >>> >> > Liang Zhang (John) > >>> >> > Apache ShardingSphere & Dubbo > >>> >> > > >>> >> > > >>> >> > Sheng Wu 于2020年2月15日周六 下午2:12写道： > >>> >> > > >>> >> >> I am OK to remove them from the PMC list. But maybe keep them in > >>> the > >>> >> >> committer? At least, they used to contribute to the community a > >>> lot. > >>> >> >> > >>> >> >> Sheng Wu 吴晟 > >>> >> >> Twitter, wusheng1108 > >>> >> >> > >>> >> >>
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Hi I found one missing step. The incubator status page[1] requires to update. Including the news about new committer, PMC and release. [1] https://incubator.apache.org/projects/shardingsphere.html Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2020年2月15日周六 下午8:35写道： > I will change the name `io.shardingsphere` to `io.opensharding` in > OpenSharding. > > -- > > Zhang Yonglun > Apache ShardingSphere > > > zhangli...@apache.org 于2020年2月15日周六 下午5:59写道： > > > Remain tasks: > > > > - Remove author information in java code. [TODO] > > > > - Some remain codes[1] still using the old package name > > `io.shardingsphere`, we plan to rename them as `io.opensharding`. [TODO] > > > > - Major contributors sign ICLA. [DONE] > > > > - Discuss PMC list. [DONE] > > > > > > [1] https://github.com/OpenSharding > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > zhangli...@apache.org 于2020年2月15日周六 下午5:57写道： > > > > > > I am OK to remove them from the PMC list. But maybe keep them in the > > > committer? At least, they used to contribute to the community a lot. > > > > > > Agree. > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > > > > > Sheng Wu 于2020年2月15日周六 下午2:12写道： > > > > > >> I am OK to remove them from the PMC list. But maybe keep them in the > > >> committer? At least, they used to contribute to the community a lot. > > >> > > >> Sheng Wu 吴晟 > > >> Twitter, wusheng1108 > > >> > > >> > > >> zhangli...@apache.org 于2020年2月15日周六 下午1:53写道： > > >> > > >> > Ling Yue and Yongsheng Peng have no response for the invitation and > > >> they do > > >> > not interest during ShardingSphere incubating, how about remove them > > >> from > > >> > PMC and committer list? > > >> > Other person will be the member of ShardingSphere PMC. > > >> > > > >> > Any suggestion? > > >> > > > >> > -- > > >> > > > >> > Liang Zhang (John) > > >> > Apache ShardingSphere & Dubbo > > >> > > > >> > > > >> > zhangli...@apache.org 于2020年2月15日周六 > 下午1:48写道： > > >> > > > >> > > The invitation has finished, I paste the result here: > > >> > > > > >> > > Invitation result: > > >> > > > > >> > > Like to be the member of ShardingSphere PMC: > > >> > > > > >> > > - Liang Zhang > > >> > > - Hongtao Gao > > >> > > - Sheng Wu > > >> > > - Juan Pan > > >> > > - Jun Zhao > > >> > > - Yi Yang > > >> > > - Yonglun Zhang > > >> > > - Gosling Von > > >> > > - Gosling Von > > >> > > - QingYang Chen > > >> > > - Willem Jiang > > >> > > - Hongjun Du > > >> > > - Xiaoguang Ma > > >> > > - Hao Cao > > >> > > > > >> > > No response: > > >> > > > > >> > > - Yongsheng Peng > > >> > > - Ling Yue > > >> > > > > >> > > > > >> > > -- > > >> > > > > >> > > Liang Zhang (John) > > >> > > Apache ShardingSphere & Dubbo > > >> > > > > >> > > > > >> > > Hongtao Gao 于2020年2月12日周三 上午10:28写道： > > >> > > > > >> > >> I agree with that, the current important task to gather all > members > > >> to > > >> > >> build a group and I have replied to that mail. > > >> > >> > > >> > >> And I'm going to share my work through the public channels, for > > >> > instance, > > >> > >> mail list and issue. Let more members know what am I doing or > will > > >> do. > > >> > >> > > >> > >> Thanks, Hongtao > > >> > >> > > >> > >> Craig Russell 于2020年2月12日周三 上午12:30写道： > > >> > >> > > >> > >> > Hi Hon
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
I am OK to remove them from the PMC list. But maybe keep them in the committer? At least, they used to contribute to the community a lot. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月15日周六 下午1:53写道： > Ling Yue and Yongsheng Peng have no response for the invitation and they do > not interest during ShardingSphere incubating, how about remove them from > PMC and committer list? > Other person will be the member of ShardingSphere PMC. > > Any suggestion? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhangli...@apache.org 于2020年2月15日周六 下午1:48写道： > > > The invitation has finished, I paste the result here: > > > > Invitation result: > > > > Like to be the member of ShardingSphere PMC: > > > > - Liang Zhang > > - Hongtao Gao > > - Sheng Wu > > - Juan Pan > > - Jun Zhao > > - Yi Yang > > - Yonglun Zhang > > - Gosling Von > > - Gosling Von > > - QingYang Chen > > - Willem Jiang > > - Hongjun Du > > - Xiaoguang Ma > > - Hao Cao > > > > No response: > > > > - Yongsheng Peng > > - Ling Yue > > > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > Hongtao Gao 于2020年2月12日周三 上午10:28写道： > > > >> I agree with that, the current important task to gather all members to > >> build a group and I have replied to that mail. > >> > >> And I'm going to share my work through the public channels, for > instance, > >> mail list and issue. Let more members know what am I doing or will do. > >> > >> Thanks, Hongtao > >> > >> Craig Russell 于2020年2月12日周三 上午12:30写道： > >> > >> > Hi Hongtao Gao, > >> > > >> > Obviously I was unaware of your contributions to the community. The > >> > important thing is to review all contributions and decide as a group. > >> > > >> > Best regards, > >> > Craig > >> > > >> > > On Feb 10, 2020, at 10:43 PM, Hongtao Gao > >> wrote: > >> > > > >> > > Hi Craig > >> > > My current work is more on propagation of ShardingSphere, including > >> > > off-site meetings and talks in some professional conferences (There > >> will > >> > be > >> > > one in June 2020). > >> > > > >> > > And next week I will send a proposal in dev mail list about the k8s > >> > > controller of shardingshpere, which is talked with some of PMC > >> members on > >> > > COSCon'19. > >> > > > >> > > So I think we should keep my PMC position, Thanks a lot. > >> > > > >> > > Craig Russell 于2020年2月11日周二 下午12:57写道： > >> > > > >> > >> Hi, > >> > >> > >> > >> Maybe I'm misreading the sheet but it looks like Ling Yue and > Hongtao > >> > Gao > >> > >> have not contributed anything to the project. It looks like they > have > >> > not > >> > >> been active on mail lists either. If this is true, I'd probably > >> remove > >> > them > >> > >> from the proposed PMC. Include them as committers if they had > >> > contributions > >> > >> before incubating. > >> > >> > >> > >> Yongsheng Peng did contribute a PR so I would not drop him from the > >> PMC. > >> > >> > >> > >> Finally, I would include all of the PPMC and committers who did > >> > contribute > >> > >> during the incubation process. > >> > >> > >> > >> Just a suggestion: If you want only people who are paying > attention, > >> you > >> > >> could start a doc with the graduation proposal and ask folks on the > >> dev@ > >> > >> list to add their names if they are interested in becoming part of > >> the > >> > PMC. > >> > >> > >> > >> Craig > >> > >> > >> > >>> On Feb 6, 2020, at 8:47 AM, zhangli...@apache.org wrote: > >> > >>> > >> > >>> I agree to remove Yongsheng Peng and always welcome him come back > >> when > >> > he > >> > >>> feel free. > >> > >>
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Agree. I think Liang asked the PPMC about whether any of them wants to step down or keep in the PMC team. Let's wait for their response. Sheng Wu 吴晟 Twitter, wusheng1108 Craig Russell 于2020年2月12日周三 上午12:29写道： > Hi Sheng Wu, > > No objection from me. The important thing is to review all contributions > and decide as a group. > > Best regards, > Craig > > > On Feb 10, 2020, at 10:50 PM, Sheng Wu > wrote: > > > > Craig Russell mailto:apache@gmail.com>> > 于2020年2月11日周二 下午12:57写道： > > > >> Hi, > >> > >> Maybe I'm misreading the sheet but it looks like Ling Yue and Hongtao > Gao > >> have not contributed anything to the project. It looks like they have > not > >> been active on mail lists either. If this is true, I'd probably remove > them > >> from the proposed PMC. Include them as committers if they had > contributions > >> before incubating. > >> > >> Yongsheng Peng did contribute a PR so I would not drop him from the PMC. > >> > > > > This is PR[1]. Fix one license and notice. > > > > Peng is a personal friend to me. > > But wearing the PPMC hat, I don't think this PR is good enough for a PMC. > > From my check, ShardingSphere main repo has 106 contributors, 68 > > contributors have more than one commit. Clearly, we haven't 68~100 PMC > > members or committers. > > I think unless he showing up to share more contributions, we should not > set > > the bar lower for him than others. > > > > > > [1] https://github.com/apache/incubator-shardingsphere/pull/2078 < > https://github.com/apache/incubator-shardingsphere/pull/2078> > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > >> > >> Finally, I would include all of the PPMC and committers who did > contribute > >> during the incubation process. > >> > >> Just a suggestion: If you want only people who are paying attention, you > >> could start a doc with the graduation proposal and ask folks on the dev@ > >> list to add their names if they are interested in becoming part of the > PMC. > >> > >> Craig > >> > >>> On Feb 6, 2020, at 8:47 AM, zhangli...@apache.org wrote: > >>> > >>> I agree to remove Yongsheng Peng and always welcome him come back when > he > >>> feel free. > >>> > >>> Other initial PPMC had contributed before ShardingSphere go to > >> incubator, I > >>> prefer keep them and let them as PMC in future. > >>> > >>> -- > >>> > >>> Liang Zhang (John) > >>> Apache ShardingSphere & Dubbo > >>> > >>> > >>> Sheng Wu 于2020年2月6日周四 下午7:44写道： > >>> > >>>> Hi > >>>> > >>>> From my reading of this data, all initial PPMC and current committers > >>>> are/were contributing to the project a lot with only one exception, > >>>> Yongsheng Peng. > >>>> He is SkyWalking's PMC, used to ask contributions to the > >> ShardingSphere, so > >>>> he was added when the project joined the incubator. But during the > >> journey, > >>>> he didn't do that. I think it makes sense to remove him. > >>>> > >>>> What do others think? > >>>> > >>>> Sheng Wu 吴晟 > >>>> Twitter, wusheng1108 > >>>> > >>>> > >>>> zhangli...@apache.org 于2020年2月6日周四 下午5:28写道： > >>>> > >>>>> Sure, please see google excel doc. [1] > >>>>> > >>>>> [1] > >>>>> > >>>>> > >>>> > >> > https://docs.google.com/spreadsheets/d/19U4t0rAnLbQW02qZlZ1lwZCB7sZxGUiMMmv8zEpee9g/edit?usp=sharing > >>>>> > >>>>> -- > >>>>> > >>>>> Liang Zhang (John) > >>>>> Apache ShardingSphere & Dubbo > >>>>> > >>>>> > >>>>> Sheng Wu 于2020年2月6日周四 下午5:14写道： > >>>>> > >>>>>> Liang > >>>>>> > >>>>>> Could you change this to a google excel doc? The email is hard to > >> read. > >>>>>> > >>>>>> Sheng Wu 吴晟 > >>>>>> Twitter, wusheng1108 > >>>>>> > >>>>>> > >>>>>
Re: [IMPORTANT][PPMC] Invitation to be ShardingSphere PMC member
I would like to stay in the PMC team. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月11日周二 下午3:41写道： > Dear ShardingSphere PPMC members, > > ShardingSphere community is discussing the graduation of ShardingSphere to > be a Top Level project of Apache Software Foundation in the dev mailing > list[1]. > As one of the steps towards graduation, the community needs to set up list > of Project Management Committees (PMC) members after graduation, which will > be included in the graduation resolution. > > The role of the PMC is included as follows[2]: > > ”The role of the PMC from a Foundation perspective is oversight. The > main role of the PMC is not code and not coding - but to ensure that > all legal issues are addressed, that procedure is followed, and that > each and every release is the product of the community as a whole. > That is key to our litigation protection mechanisms. > > Secondly the role of the PMC is to further the long term development > and health of the community as a whole, and to ensure that balanced > and wide scale peer review and collaboration does happen. Within the > ASF we worry about any community which centers around a few > individuals who are working virtually uncontested. We believe that > this is detrimental to quality, stability, and robustness of both code > and long term social structures.“ > > If you'd like to be the member of ShardingSphere PMC, please respond > YES to this thread by replying to dev@shardingsphere.apache.org no later > than > 2020-02-14 (Friday). > If you are not subscribing the private list, please remember to > subscribe to the private@ list. > > > [1] > > https://lists.apache.org/thread.html/rf6a2cec7143395ac0126dcb13f331fbc87b680eaca015d50d7793172%40%3Cdev.shardingsphere.apache.org%3E > [2] http://www.apache.org/foundation/how-it-works.html#pmc > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Craig Russell 于2020年2月11日周二 下午12:57写道： > Hi, > > Maybe I'm misreading the sheet but it looks like Ling Yue and Hongtao Gao > have not contributed anything to the project. It looks like they have not > been active on mail lists either. If this is true, I'd probably remove them > from the proposed PMC. Include them as committers if they had contributions > before incubating. > > Yongsheng Peng did contribute a PR so I would not drop him from the PMC. > This is PR[1]. Fix one license and notice. Peng is a personal friend to me. But wearing the PPMC hat, I don't think this PR is good enough for a PMC. >From my check, ShardingSphere main repo has 106 contributors, 68 contributors have more than one commit. Clearly, we haven't 68~100 PMC members or committers. I think unless he showing up to share more contributions, we should not set the bar lower for him than others. [1] https://github.com/apache/incubator-shardingsphere/pull/2078 Sheng Wu 吴晟 Twitter, wusheng1108 > > Finally, I would include all of the PPMC and committers who did contribute > during the incubation process. > > Just a suggestion: If you want only people who are paying attention, you > could start a doc with the graduation proposal and ask folks on the dev@ > list to add their names if they are interested in becoming part of the PMC. > > Craig > > > On Feb 6, 2020, at 8:47 AM, zhangli...@apache.org wrote: > > > > I agree to remove Yongsheng Peng and always welcome him come back when he > > feel free. > > > > Other initial PPMC had contributed before ShardingSphere go to > incubator, I > > prefer keep them and let them as PMC in future. > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > Sheng Wu 于2020年2月6日周四 下午7:44写道： > > > >> Hi > >> > >> From my reading of this data, all initial PPMC and current committers > >> are/were contributing to the project a lot with only one exception, > >> Yongsheng Peng. > >> He is SkyWalking's PMC, used to ask contributions to the > ShardingSphere, so > >> he was added when the project joined the incubator. But during the > journey, > >> he didn't do that. I think it makes sense to remove him. > >> > >> What do others think? > >> > >> Sheng Wu 吴晟 > >> Twitter, wusheng1108 > >> > >> > >> zhangli...@apache.org 于2020年2月6日周四 下午5:28写道： > >> > >>> Sure, please see google excel doc. [1] > >>> > >>> [1] > >>> > >>> > >> > https://docs.google.com/spreadsheets/d/19U4t0rAnLbQW02qZlZ1lwZCB7sZxGUiMMmv8zEpee9g/edit?usp=sharing > >>> > >>> -- > >>> > >>> Liang Zhang (John) > >>> Apache ShardingSphere & Dubbo > >>> > >>> > >>> Sheng Wu 于2020年2月6日周四 下午5:14写道： > >>> > >>>> Liang > >>>> > >>>> Could you change this to a google excel doc? The email is hard to > read. > >>>> > >>>> Sheng Wu 吴晟 > >>>> Twitter, wusheng1108 > >>>> > >>>> > >>>> zhangli...@apache.org 于2020年2月6日周四 下午5:12写道： > >>>> > >>>>> The statistics after incubator: > >>>>> > >>>>> PPMCs: > >>>>> > >>>>> | *Name*| *Mails* | *Assigned Issues* | *Merged PRs* | > >>> *Code > >>>>> ++* | *Code --* | *Doc ++* | *Doc --* | > >>>>> | - | --- | - | | > >>>>> - | - | | | > >>>>> | Hao Cao | 6 | 2 | 14 | > >>> 1,278 > >>>>> | 44| 5| 5| > >>>>> | Hongjun Du| 12 | 38| 67 | > >>> 38,788 > >>>>> | 33,670| 2| 0| > >>>>> | Hongtao Gao | 2 | 0 | 0| 0 > >>>>> | 0 | 0| 0| > >>>>> | Juan Pan | 167 | 85| 319 | > >>> 91,675 > >>>>> | 71,611| 1,300,919| 1,284,356| > >>>>> | Jun Zhao | 46 | 76| 130 | > >>>> 166,356 > >>>>> | 170,890 | 2,138| 2,122| > >>>>> | Liang Zhang | 279 | 130
Re: [DISCUSS] 4.0.1 stable version release plan
Thanks for the feedback, good to me. Sheng Wu 吴晟 Twitter, wusheng1108 zhaojun 于2020年2月10日周一 上午9:37写道： > > Agree with the principle. > > Do we have substantial changes? From changelog, literally, there is. > > I have review these optimize code, the code change scope is small, > so I think it was not a substantial changes. > > -- > Zhao Jun (cherrylzhao) > Apache ShardingSphere & ServiceComb > >
Re: [DISCUSS] 4.0.1 stable version release plan
zhaojun 于2020年2月10日周一 上午9:17写道： > Hi, Sheng and guangyuan > > Thanks for kind remind, also I have just google the principle of version > specification. > 4.0.1 is mainly for bug fix and there is no substantial improvements > happened. > Agree with the principle. Do we have substantial changes? From changelog, literally, there is. Sheng Wu 吴晟 Twitter, wusheng1108 > > 2nd version number means new feature or substantial improvements are > introduced. > > -- > Zhao Jun (cherrylzhao) > Apache ShardingSphere & ServiceComb > > > On Feb 9, 2020, at 5:43 PM, Sheng Wu wrote: > > > > A question, traditionally, the 3rd version number means bug fix, but the > > changelogs include enhancement. > > Do we set the 2nd version number for new feature only? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年2月9日周日 下午5:34写道： > > > >> +1. > >> Great. There are no missing tasks from my side. > >> > >> -- > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> zhaojun 于2020年2月9日周日 下午3:44写道： > >> > >>> Hi, ShardingSphere community, > >>> > >>> I’d like to be the release manager of 4.0.1 version. > >>> We have done some bug fixes and performance optimization in past month > >>> based on 4.0.0. > >>> If there is no other requirement, I think we can start to release 4.0.1 > >>> recently. > >>> > >>> > >>> ## Bug fixes > >>> > >>> 3975 oracle insert SQL could not work in encrypt mode > >>> 3997 proxy for PostgreSQL decode parameters error in all types except > >>> String > >>> 4022 none sharding strategy could not config in spring-boot > >>> 4052 plain column could not get from resultSet in sharding-encrypt > mode > >>> 4173 wasNull field was wrong in GroupByStreamMergeResult > >>> > >>> > >>> ## Enhancement > >>> > >>> 3956 using guava cache to improve parsing performance > >>> 4004 optimize COM_STM_EXECUTE of MySQL to support sysbench > >>> 4054 optimize antlr performance using two-stage parsing strategy > >>> 4205 add class filter constructor to restrict the illegal class from > >> YAML > >>> > >>> Thanks to these contributors for their code commits. > >>> - tuohai666, xiyelife, SteNicholas, KomachiSion, beckhampu, > >> plazmdk > >>> > >>> Any other task missing here? Please feel free to let me know. > >>> > >>> -- > >>> Zhao Jun (cherrylzhao) > >>> Apache ShardingSphere & ServiceComb > >> > >
Re: [DISCUSS] 4.0.1 stable version release plan
A question, traditionally, the 3rd version number means bug fix, but the changelogs include enhancement. Do we set the 2nd version number for new feature only? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月9日周日 下午5:34写道： > +1. > Great. There are no missing tasks from my side. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhaojun 于2020年2月9日周日 下午3:44写道： > > > Hi, ShardingSphere community, > > > > I’d like to be the release manager of 4.0.1 version. > > We have done some bug fixes and performance optimization in past month > > based on 4.0.0. > > If there is no other requirement, I think we can start to release 4.0.1 > > recently. > > > > > > ## Bug fixes > > > > 3975 oracle insert SQL could not work in encrypt mode > > 3997 proxy for PostgreSQL decode parameters error in all types except > > String > > 4022 none sharding strategy could not config in spring-boot > > 4052 plain column could not get from resultSet in sharding-encrypt mode > > 4173 wasNull field was wrong in GroupByStreamMergeResult > > > > > > ## Enhancement > > > > 3956 using guava cache to improve parsing performance > > 4004 optimize COM_STM_EXECUTE of MySQL to support sysbench > > 4054 optimize antlr performance using two-stage parsing strategy > > 4205 add class filter constructor to restrict the illegal class from > YAML > > > > Thanks to these contributors for their code commits. > > - tuohai666, xiyelife, SteNicholas, KomachiSion, beckhampu, > plazmdk > > > > Any other task missing here? Please feel free to let me know. > > > > -- > > Zhao Jun (cherrylzhao) > > Apache ShardingSphere & ServiceComb >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Hi >From my reading of this data, all initial PPMC and current committers are/were contributing to the project a lot with only one exception, Yongsheng Peng. He is SkyWalking's PMC, used to ask contributions to the ShardingSphere, so he was added when the project joined the incubator. But during the journey, he didn't do that. I think it makes sense to remove him. What do others think? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月6日周四 下午5:28写道： > Sure, please see google excel doc. [1] > > [1] > > https://docs.google.com/spreadsheets/d/19U4t0rAnLbQW02qZlZ1lwZCB7sZxGUiMMmv8zEpee9g/edit?usp=sharing > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月6日周四 下午5:14写道： > > > Liang > > > > Could you change this to a google excel doc? The email is hard to read. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年2月6日周四 下午5:12写道： > > > > > The statistics after incubator: > > > > > > PPMCs: > > > > > > | *Name*| *Mails* | *Assigned Issues* | *Merged PRs* | > *Code > > > ++* | *Code --* | *Doc ++* | *Doc --* | > > > | - | --- | - | | > > > - | - | | | > > > | Hao Cao | 6 | 2 | 14 | > 1,278 > > > | 44| 5| 5| > > > | Hongjun Du| 12 | 38| 67 | > 38,788 > > > | 33,670| 2| 0| > > > | Hongtao Gao | 2 | 0 | 0| 0 > > > | 0 | 0| 0| > > > | Juan Pan | 167 | 85| 319 | > 91,675 > > > | 71,611| 1,300,919| 1,284,356| > > > | Jun Zhao | 46 | 76| 130 | > > 166,356 > > > | 170,890 | 2,138| 2,122| > > > | Liang Zhang | 279 | 130 | 164 | > > > 1,198,935 | 1,245,278 | 691,617 | 54,337 | > > > | Ling Yue | 0 | 0 | 0| 0 > > > | 0 | 0| 0| > > > | Qingyang Chen | 9 | 10| 8| > 24,115 > > > | 18,901| 237 | 0| > > > | Sheng Wu | 175 | 1 | 2| 18 > > > | 1 | 0| 0| > > > | Xiaoguang Ma | 1 | 2 | 17 | > 7,279 > > > | 4,741 | 173 | 60 | > > > | Yi Yang | 56 | 83| 101 | > 24,556 > > > | 13,150| 1,289| 217 | > > > | Yonglun Zhang | 87 | 126 | 124 | > > 103,754 > > > | 65,066| 18,733 | 18,249 | > > > | Yongsheng Peng| 3 | 0 | 1| 262 > > > | 0 | 0| 0| > > > > > > Committers: > > > > > > | *Name*| *Mails* | *Assigned Issues* | *Merged PRs* | > *Code > > > ++* | *Code --* | *Doc ++* | *Doc --* | > > > | - | --- | - | | > > > - | - | | | > > > | Guangyuan Wang| 28 | 5 | 21 | > 6,130 > > > | 2,458 | 290 | 190 | > > > | Haisheng Sun | 18 | 20| 26 | > 4,791 > > > | 1,877 | 12 | 8| > > > | Xiaofeng Jiang| 5 | 21| 31 | > 29,296 > > > | 291 | 0| 0| > > > | Qi Wang | 5 | 21| 62 | > 24,040 > > > | 10,437| 1,978| 1,968| > > > | Ya Li | 0 | 6 | 21 | > 6,070 > > > | 1,282 | 55 | 34 | > > > | Yanan Zhao| 0 | 10| 23 | > 82,293 > > > | 3,864 | 0| 897 | > > > | Wen Ouyang| 2 | 9 | 19 | 673 > > > | 11| 2| 0| > > > | Zhiyi Yan | 6 | 4 | 18 | > 10,693 > > > | 2,117 | 13 | 11 | > > > | ZongLei Dong | 20 | 7 | 21 | > 3,637 > > > | 3,520 | 20 | 18 | > > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Liang Could you change this to a google excel doc? The email is hard to read. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年2月6日周四 下午5:12写道： > The statistics after incubator: > > PPMCs: > > | *Name*| *Mails* | *Assigned Issues* | *Merged PRs* | *Code > ++* | *Code --* | *Doc ++* | *Doc --* | > | - | --- | - | | > - | - | | | > | Hao Cao | 6 | 2 | 14 | 1,278 > | 44| 5| 5| > | Hongjun Du| 12 | 38| 67 | 38,788 > | 33,670| 2| 0| > | Hongtao Gao | 2 | 0 | 0| 0 > | 0 | 0| 0| > | Juan Pan | 167 | 85| 319 | 91,675 > | 71,611| 1,300,919| 1,284,356| > | Jun Zhao | 46 | 76| 130 | 166,356 > | 170,890 | 2,138| 2,122| > | Liang Zhang | 279 | 130 | 164 | > 1,198,935 | 1,245,278 | 691,617 | 54,337 | > | Ling Yue | 0 | 0 | 0| 0 > | 0 | 0| 0| > | Qingyang Chen | 9 | 10 | 8 | 24,115 > | 18,901| 237 | 0| > | Sheng Wu | 175 | 1 | 2| 18 > | 1 | 0| 0| > | Xiaoguang Ma | 1 | 2 | 17 | 7,279 > | 4,741 | 173 | 60 | > | Yi Yang | 56 | 83| 101 | 24,556 > | 13,150| 1,289| 217 | > | Yonglun Zhang | 87 | 126 | 124 | 103,754 > | 65,066| 18,733 | 18,249 | > | Yongsheng Peng| 3 | 0 | 1| 262 > | 0 | 0| 0| > > Committers: > > | *Name*| *Mails* | *Assigned Issues* | *Merged PRs* | *Code > ++* | *Code --* | *Doc ++* | *Doc --* | > | - | --- | - | | > - | - | | | > | Guangyuan Wang| 28 | 5 | 21 | 6,130 > | 2,458 | 290 | 190 | > | Haisheng Sun | 18 | 20| 26 | 4,791 > | 1,877 | 12 | 8| > | Xiaofeng Jiang| 5 | 21| 31 | 29,296 > | 291 | 0| 0| > | Qi Wang | 5 | 21| 62 | 24,040 > | 10,437| 1,978| 1,968| > | Ya Li | 0 | 6 | 21 | 6,070 > | 1,282 | 55 | 34 | > | Yanan Zhao| 0 | 10| 23 | 82,293 > | 3,864 | 0| 897 | > | Wen Ouyang| 2 | 9 | 19 | 673 > | 11| 2| 0| > | Zhiyi Yan | 6 | 4 | 18 | 10,693 > | 2,117 | 13 | 11 | > | ZongLei Dong | 20 | 7 | 21 | 3,637 > | 3,520 | 20 | 18 | > > The statistics before incubator: > > | *Name*| *Code ++* | *Code --* | > | - | - | - | > | Hao Cao | 136,639 | 112,458 | > | Hongjun Du| 63,910| 54,490| > | Hongtao Gao | 15,523| 20,038| > | Juan Pan | 102,269 | 93,376 | > | Jun Zhao | 24,483| 22,539| > | Liang Zhang | 818,555 | 892,431 | > | Ling Yue | 404 | 213 | > | Qingyang Chen | 3,900 | 1,205 | > | Sheng Wu | 21| 21| > | Xiaoguang Ma | 15,138| 6,025 | > | Yi Yang | 4,600 | 1,840 | > | Yonglun Zhang | 14,171| 8,645 | > > Our community care about now and future, we respect history too. Thank you > for every PPMC and committer. > > Please feel free to discuss about the PMC list for graduation. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月6日周四 下午1:54写道： > > > zhangli...@apache.org 于2020年2月6日周四 上午2:00写道： > > > > > Before I list all PPMCs and committers, we need to discuss the rule of > > how > > > to define `inactive` PPMC. > > > > > > The rules maybe: > > > > > > - Stop contribution after ShardingSphere goto incubator. > > > > > > > If there are initial PPMCs staying in this way, I prefer to keep them as > > committer only. > > > &
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
zhangli...@apache.org 于2020年2月6日周四 上午2:00写道： > Before I list all PPMCs and committers, we need to discuss the rule of how > to define `inactive` PPMC. > > The rules maybe: > > - Stop contribution after ShardingSphere goto incubator. > If there are initial PPMCs staying in this way, I prefer to keep them as committer only. > - Rare contribution after ShardingSphere goto incubator. We need to > define how to define `rare` too. > - Stop contribution during past period until now. The definition of > `during past period` maybe one year or half year. > I prefer at least one year(or equal 2, the whole incubator journey). If they still contribute anything from time to time, even talk at the Conference/Meetup in public, I hope we should trust them and keep them in final PMCs. > > If we decide follow these rules, we may let these PPMCs as committers. > > And do we need to discuss the rules to upgrade committers to PMC? > Any suggestions? > If no objection, we could just do it. Let's list this as a default in the resolution. Liang, after you have the stat, we could exclude `Stop contribution after ShardingSphere goto incubator` people from the final PMC list. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年2月5日周三 下午9:28写道： > > > Zonglei Dong 于2020年2月5日周三 下午9:19写道： > > > > > Hi Sheng, Liang, > > > > > > > > > As a committer, I want to take on greater responsibility, make more > > > contribution to ShardingSphere and take better practice for Apache Way > in > > > the future. > > > > > > > > > I understand some permissions only for PMC(or PPMC), e.g release new > > > version, Does there are any difference between PMC and committer? > > > > > > > For release, the committer is enough to go for a release, you just need > > PMC's vote to make release official. > > > > As an active PMC member should > > 1. Watching the project to follow the Apache way > > 2. Watching the branding issue, and work on the issues if find it(such as > > talk with other committer/contributor or 3rd party) > > 3. Find and promote new committer and PMC member > > For more, read https://www.apache.org/dev/pmc.html > > > > Also, in the Apache, we don't(also shouldn't) require people always > active. > > You could do these in part-time, or when you have time. > > > > > > > > > > > > > > > Thanks. > > > Best wishes. > > > > > > > > > Zonglei Dong > > > Apache ShardingSphere > > > > > > > > > On 02/5/2020 20:34，Sheng Wu wrote： > > > I had the impression that inactive PPMC will be excluded to become PMC. > > > ALL in or not? > > > > > > Do you have the list? I think if some of them stop contributing to the > > > project after joining the incubator, I could exclude those. > > > > > > I nominate myself as project VP because my responsibility is monthly > > > report > > > to incubator, and I will in charge of to report to ASF in future. > > > > > > +1 > > > > > > I would like to keep all PPMC members to PMC, and keep all current > > > committers as committers too. > > > > > > Personally, I prefer to move all committers to PMC. I trust they will > > > follow the more experienced PMC's suggestions and they wouldn't break > the > > > ASF rules intentionally. > > > > > > To All committer(but not PMC) > > > What do you think? I would like to support their own decision. > > > > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > Juan Pan 于2020年2月5日周三 下午6:55写道： > > > > > > I would like to keep all PPMC members to PMC, and keep all current > > > committers as committers too. > > > > > > > > > I had the impression that inactive PPMC will be excluded to become PMC. > > > ALL in or not? > > > > > > > > > Juan Pan (Trista) > > > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > > E-mail: panj...@apache.org > > > > > > > > > > > > > > > On 02/5/2020 17:38，zhangli...@apache.org wrote： > > > I want discuss about project VP, PMC and committer list after > graduation. > > > I would like to keep all PPMC members to PMC, and keep all current > > > committers as committers too. > > > The almost committers are new guys for Sh
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Zonglei Dong 于2020年2月5日周三 下午9:19写道： > Hi Sheng, Liang, > > > As a committer, I want to take on greater responsibility, make more > contribution to ShardingSphere and take better practice for Apache Way in > the future. > > > I understand some permissions only for PMC(or PPMC), e.g release new > version, Does there are any difference between PMC and committer? > For release, the committer is enough to go for a release, you just need PMC's vote to make release official. As an active PMC member should 1. Watching the project to follow the Apache way 2. Watching the branding issue, and work on the issues if find it(such as talk with other committer/contributor or 3rd party) 3. Find and promote new committer and PMC member For more, read https://www.apache.org/dev/pmc.html Also, in the Apache, we don't(also shouldn't) require people always active. You could do these in part-time, or when you have time. > > > Thanks. > Best wishes. > > > Zonglei Dong > Apache ShardingSphere > > > On 02/5/2020 20:34，Sheng Wu wrote： > I had the impression that inactive PPMC will be excluded to become PMC. > ALL in or not? > > Do you have the list? I think if some of them stop contributing to the > project after joining the incubator, I could exclude those. > > I nominate myself as project VP because my responsibility is monthly > report > to incubator, and I will in charge of to report to ASF in future. > > +1 > > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. > > Personally, I prefer to move all committers to PMC. I trust they will > follow the more experienced PMC's suggestions and they wouldn't break the > ASF rules intentionally. > > To All committer(but not PMC) > What do you think? I would like to support their own decision. > > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Juan Pan 于2020年2月5日周三 下午6:55写道： > > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. > > > I had the impression that inactive PPMC will be excluded to become PMC. > ALL in or not? > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 02/5/2020 17:38，zhangli...@apache.org wrote： > I want discuss about project VP, PMC and committer list after graduation. > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. > The almost committers are new guys for ShardingSphere, they may need more > experiences for open source community governance, we can vote committers to > PMC one by one after graduation. > I nominate myself as project VP because my responsibility is monthly report > to incubator, and I will in charge of to report to ASF in future. > > Any suggestion? > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhangli...@apache.org 于2020年1月20日周一 下午3:26写道： > > Got it, it means those threads are not block for our graduation, and > could be done anytime. > > Yes > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan 于2020年1月20日周一 上午10:14写道： > > Got it, it means those threads are not block for our graduation, and > could be done anytime. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/19/2020 10:37，Sheng Wu wrote： > As far as those docs and examples already in the Apache repos, I think > those are irrelavent. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Juan Pan 于2020年1月19日周日 上午10:30写道： > > +1 Agreeing to put graduation into our upcoming agenda. BTW, do you think > we need finish the work discussed in other thread, like moving doc and > example repos to ShardingSphere repo? > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/17/2020 23:39，zhangli...@apache.org wrote： > I list remain issues here: > > 1. Remove author information in java code, copyright should belong to ASF. > 2. Some remain codes[1] still using the old package name > `io.shardingsphere`, we plan to rename them as `io.opensharding`. > <https://github.com/OpenSharding>3. Let the major contributors to sign > ICLA > if they haven't singed yet. > > Please complement the list if I missing anything. > > [1] https://github.com/OpenSharding > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年1月17日周五 下午6:01写道： > > F
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
> I had the impression that inactive PPMC will be excluded to become PMC. ALL in or not? Do you have the list? I think if some of them stop contributing to the project after joining the incubator, I could exclude those. > I nominate myself as project VP because my responsibility is monthly report > to incubator, and I will in charge of to report to ASF in future. +1 > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. Personally, I prefer to move all committers to PMC. I trust they will follow the more experienced PMC's suggestions and they wouldn't break the ASF rules intentionally. To All committer(but not PMC) What do you think? I would like to support their own decision. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年2月5日周三 下午6:55写道： > > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. > > > I had the impression that inactive PPMC will be excluded to become PMC. > ALL in or not? > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 02/5/2020 17:38，zhangli...@apache.org wrote： > I want discuss about project VP, PMC and committer list after graduation. > I would like to keep all PPMC members to PMC, and keep all current > committers as committers too. > The almost committers are new guys for ShardingSphere, they may need more > experiences for open source community governance, we can vote committers to > PMC one by one after graduation. > I nominate myself as project VP because my responsibility is monthly report > to incubator, and I will in charge of to report to ASF in future. > > Any suggestion? > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhangli...@apache.org 于2020年1月20日周一 下午3:26写道： > > Got it, it means those threads are not block for our graduation, and > could be done anytime. > > Yes > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan 于2020年1月20日周一 上午10:14写道： > > Got it, it means those threads are not block for our graduation, and > could be done anytime. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/19/2020 10:37，Sheng Wu wrote： > As far as those docs and examples already in the Apache repos, I think > those are irrelavent. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Juan Pan 于2020年1月19日周日 上午10:30写道： > > +1 Agreeing to put graduation into our upcoming agenda. BTW, do you think > we need finish the work discussed in other thread, like moving doc and > example repos to ShardingSphere repo? > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/17/2020 23:39，zhangli...@apache.org wrote： > I list remain issues here: > > 1. Remove author information in java code, copyright should belong to ASF. > 2. Some remain codes[1] still using the old package name > `io.shardingsphere`, we plan to rename them as `io.opensharding`. > <https://github.com/OpenSharding>3. Let the major contributors to sign > ICLA > if they haven't singed yet. > > Please complement the list if I missing anything. > > [1] https://github.com/OpenSharding > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年1月17日周五 下午6:01写道： > > From my perspective, we should. Like I said in another thread. > I think we should be ready to consider and filter whether we have left any > issue before graduation. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2020年1月17日周五 下午3:10写道： > > Hello community, > > > I'd like to talk about graduation as TLP for Apache > ShardingSphere(Incubator). > > > We were open source at 16th Jan 2016, and entered into ASF incubator in > 10th Nov 2018. During the past period in incubator, our community grow up > quickly. > > > I summarize some data below: > > > - There are 1301 emails sent by 159 people in dev mailing-list excepted > GitBox forwarded; > > - 2539 Issues created during ASF incubating, 2468 Issues resolved during > ASF incubating; > > - 1073 PRs created during ASF incubating, 918 PRs merged during ASF > incubating; > > - There are 89 contributors for now; > > - There are 4 versions released successfully conformant to Apache release > policy by 3 release managers; > > - There are 2 new PPMCs and 8 new committers were invited to join the > community. > > > We had already finished the Podling Maturity Assessment for > ShardingSphere[1], the 34 items are all passed. > > > We had resolved all branding issues which include Logo, GitHub repo, > document, website and DockerHub image. > > > > Can we talk about when will start to consider about graduate? > > > [1] > https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md > > > -- > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
As far as those docs and examples already in the Apache repos, I think those are irrelavent. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年1月19日周日 上午10:30写道： > +1 Agreeing to put graduation into our upcoming agenda. BTW, do you think > we need finish the work discussed in other thread, like moving doc and > example repos to ShardingSphere repo? > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/17/2020 23:39，zhangli...@apache.org wrote： > I list remain issues here: > > 1. Remove author information in java code, copyright should belong to ASF. > 2. Some remain codes[1] still using the old package name > `io.shardingsphere`, we plan to rename them as `io.opensharding`. > <https://github.com/OpenSharding>3. Let the major contributors to sign > ICLA > if they haven't singed yet. > > Please complement the list if I missing anything. > > [1] https://github.com/OpenSharding > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年1月17日周五 下午6:01写道： > > From my perspective, we should. Like I said in another thread. > I think we should be ready to consider and filter whether we have left any > issue before graduation. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2020年1月17日周五 下午3:10写道： > > Hello community, > > > I'd like to talk about graduation as TLP for Apache > ShardingSphere(Incubator). > > > We were open source at 16th Jan 2016, and entered into ASF incubator in > 10th Nov 2018. During the past period in incubator, our community grow up > quickly. > > > I summarize some data below: > > > - There are 1301 emails sent by 159 people in dev mailing-list excepted > GitBox forwarded; > > - 2539 Issues created during ASF incubating, 2468 Issues resolved during > ASF incubating; > > - 1073 PRs created during ASF incubating, 918 PRs merged during ASF > incubating; > > - There are 89 contributors for now; > > - There are 4 versions released successfully conformant to Apache release > policy by 3 release managers; > > - There are 2 new PPMCs and 8 new committers were invited to join the > community. > > > We had already finished the Podling Maturity Assessment for > ShardingSphere[1], the 34 items are all passed. > > > We had resolved all branding issues which include Logo, GitHub repo, > document, website and DockerHub image. > > > > Can we talk about when will start to consider about graduate? > > > [1] > https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md > > > -- > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
>From my perspective, we should. Like I said in another thread. I think we should be ready to consider and filter whether we have left any issue before graduation. Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年1月17日周五 下午3:10写道： > Hello community, > > > I'd like to talk about graduation as TLP for Apache > ShardingSphere(Incubator). > > > We were open source at 16th Jan 2016, and entered into ASF incubator in > 10th Nov 2018. During the past period in incubator, our community grow up > quickly. > > > I summarize some data below: > > > - There are 1301 emails sent by 159 people in dev mailing-list excepted > GitBox forwarded; > > - 2539 Issues created during ASF incubating, 2468 Issues resolved during > ASF incubating; > > - 1073 PRs created during ASF incubating, 918 PRs merged during ASF > incubating; > > - There are 89 contributors for now; > > - There are 4 versions released successfully conformant to Apache release > policy by 3 release managers; > > - There are 2 new PPMCs and 8 new committers were invited to join the > community. > > > We had already finished the Podling Maturity Assessment for > ShardingSphere[1], the 34 items are all passed. > > > We had resolved all branding issues which include Logo, GitHub repo, > document, website and DockerHub image. > > > > Can we talk about when will start to consider about graduate? > > > [1] > https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md > > > -- > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo >
Re: The 2019 Summary of ShardingSphere community
Congrats to the whole community, and be honored as a part of the team. Happy Chinese new year to everyone. And in my mind, after the vacation of many of us, we could start the discussion about graduation. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年1月16日周四 下午8:42写道： > Hello community, > > > > Although our 2020 journey has begun, it is worth reviewing what we did > during last year and sharing the great progress we made with everyone in > community. Here are some roughly interesting data from January 2019 to > December 2019. > > > Compared with 513 PRs in gitHub during 2018, 870+ PRs were merged into our > dev branch last year. > > > GitHub stars increased by 50%, compared to 6k at the beginning of 2019. > > > 4 versions released successfully conformant to Apache release policy. > > > 2 PPMCs and 8 committers were invited to join our community. > > > 62 contributors did contribution for our community last year. This figure > in 2018 was about 29. > > > Although those figures are merely part of community data, it is the clear > evidence that we made a great progress during 2019. All those grow-up are > thanks to everyone in our community! > > > Special thanks to Craig, Willem, Gosling and Justin. What you shared in > Apache meetups shed lights on how to make our community active and diverse > and gave us much of help. > > > Many thanks to our PPMCs and committers. Your efforts made our community > run pretty in order. > > > Last but not least, many thanks to contributors and subscribers. You are > important force to ShardingSphere community. > > > In further, there are a lot of work and improvement need to do. Hope we > can keep carrying on with passion and make our community more 'Apache way'. > > > Any comment, suggestion, opinion are welcomed here, please step farword to > say whatever you want! > > > Warm greetings to you and your family, hope you could become who you are. > > > Trista > > > > > > > > > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > >
Re: [ANNOUNCE] Apache ShardingSphere 4.0.0 available
Hi Yonglun Do we need to create an issue to track the SkyWalking plugin update for ss 4.0? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年1月13日周一 下午5:44写道： > Hi all, > > Apache ShardingSphere (incubating) Team is glad to announce the first > release of Apache ShardingSphere Incubating 4.0.0. > > ShardingSphere is an open-source ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, Sharding-JDBC & Sharding-Proxy. > They both provide functions of data sharding, distributed transaction and > database orchestration, applicable in a variety of situations such as Java > isomorphism, heterogeneous language. > Aiming at reasonably making full use of the computation and storage > capacity of the database in a distributed system, ShardingSphere defines > itself as a middleware, rather than a totally new type of database. > As the cornerstone of many enterprises, relational database still takes a > huge market share. > Therefore, at the current stage, we prefer to focus on its increment > instead of a total overturn. > > Download Links: > https://shardingsphere.apache.org/document/current/en/downloads/ > > Release Notes: > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > Website: https://shardingsphere.apache.org/ > > ShardingSphere Resources: > - Issue: https://github.com/apache/incubator-shardingsphere/issues/ > - Mailing list: dev@shardingsphere.apache.org > - Documents: https://shardingsphere.apache.org/document/current/ > > > > - Apache ShardingSphere (incubating) Team > > > = > *Disclaimer* > > Apache ShardingSphere (incubating) is an effort undergoing incubation at > The Apache Software Foundation (ASF), sponsored by the Apache Incubator > PMC. > Incubation is required of all newly accepted projects until a further > review indicates that the infrastructure, > communications, and decision making process have stabilized in a manner > consistent with other successful ASF projects. > While incubation status is not necessarily a reflection of the completeness > or stability of the code, > it does indicate that the project has yet to be fully endorsed by the ASF. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2
Got it. +1 binding Checked 1. Incubating in names 2. Compiling pass. 3. GPG checked 4. sha512 exist 5. LICENSE and NOTICE exist. Good luck and glad to see the stable release will be available soon Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2020年1月2日周四 下午12:38写道： > Sorry, I can not find the old secret key, so we can not reuse the old > public key for now. > The only way is use the current key to check the gpg signature. Please > reimport the `KEYS` file to validate the signature for now. > > It is unnecessary to re-release version. How about continue to vote on this > thread? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Willem Jiang 于2020年1月2日周四 下午12:08写道： > > > No, I don't think using the KEYS file can keep good track of the > > public key, it doesn't support the revoke operation. > > It's better to use the public Key server to host the public key and we > > can know if the key is revoked or not. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Jan 2, 2020 at 12:04 PM Juan Pan wrote: > > > > > > That means once one key was used for one release, it could not be > > deleted from KEYS files anymore no matter it is great on or not, right? > > > > > > > > > Juan Pan (Trista) > > > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > > E-mail: panj...@apache.org > > > > > > > > > > > > > > > On 01/2/2020 12:00，Willem Jiang wrote： > > > If someone use the compromised private to sign a new release, we > > > should be able to tell if the public key is revoked. > > > If we just delete the key from the KEY file, it's hard to tell if the > > > public key is valid or not. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Thu, Jan 2, 2020 at 11:55 AM Juan Pan wrote: > > > > > > Hi Willem, > > > > > > > > > Just for curiosity, if the old key was used for one release and now is > > compromised, how about the release signed by this old and compromised > key? > > > Since this release exists in our release list and if anyone downloads > it > > from our website and intends to check it again with the bad key. > > > > > > > > > Thanks, trista > > > > > > > > > Juan Pan (Trista) > > > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > > E-mail: panj...@apache.org > > > > > > > > > > > > > > > On 01/2/2020 11:29，Willem Jiang wrote： > > > If the private key is compromised[1] or if we cannot find the private > > > key, we should revoke the public KEY[2]. > > > Please keep your private key in a safe place. > > > > > > [1] > > > https://www.thesslstore.com/blog/heres-what-happens-when-your-private-key-gets-compromised/ > > > [3] > > > http://blog.chapagain.com.np/gpg-revoking-your-public-key-and-notifiying-key-server/ > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Thu, Jan 2, 2020 at 10:21 AM Sheng Wu > > wrote: > > > > > > You can't simply delete the old one. Because ShardingSphere has > existing > > > release based on that KEY :) > > > We could still continue in this way, but it should not be recommended > if > > > your old key is still available. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > Juan Pan 于2020年1月2日周四 上午10:18写道： > > > > > > Hi Liang, > > > > > > > > > If you plan not to use the old one any more, deleting is is an > > alternative > > > to avoid confusion. If so, it is necessary to delete it in KEYS file > and > > > public key servers, IMO. > > > > > > > > > Juan Pan (Trista) > > > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > > E-mail: panj...@apache.org > > > > > > > > > > > > > > > On 01/1/2020 21:26，Sheng Wu wrote： > > > My concern is making people confused. The PGP could export and import > > from > > > the old laptop. You don't need a new one. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2
Yes, because the verification is introduced on the official website, download page, right? If we delete it, users will fail when we do the verification. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年1月2日周四 上午11:03写道： > Hi Sheng, > > > Thanks for your correction. > Just confirm, the key point is that the old key for 4.0.0-RC1 release > which passed the release vote but exists in our release list now could not > be deleted, right? In other words, only one certain release exists, the key > used for which must exist？ > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/2/2020 10:21，Sheng Wu wrote： > You can't simply delete the old one. Because ShardingSphere has existing > release based on that KEY :) > We could still continue in this way, but it should not be recommended if > your old key is still available. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Juan Pan 于2020年1月2日周四 上午10:18写道： > > Hi Liang, > > > If you plan not to use the old one any more, deleting is is an alternative > to avoid confusion. If so, it is necessary to delete it in KEYS file and > public key servers, IMO. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/1/2020 21:26，Sheng Wu wrote： > My concern is making people confused. The PGP could export and import from > the old laptop. You don't need a new one. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2020年1月1日周三 下午8:55写道： > > A question, why you have two pgp keys in the KEYS file? > > I change a computer, the 1st one is for the 4.0.0-RC1, the 4th one is for > this version. > Do you think we could remove the 1st one? because I will never use that gpp > key again, but do we need to keep it to make the 4.0.0-RC1 can be validate? > > ------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年1月1日周三 下午8:34写道： > > Hi Liang Zhang > > A question, why you have two pgp keys in the KEYS file? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2019年12月30日周一 下午9:44写道： > > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0 > > 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/ > > Maven 2 staging repository: > > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1029/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0/ > > Release Commit ID: > > > > > > https://github.com/apache/incubator-shardingsphere/commit/f81f4f03b1dd4b426adf1f29ffe93f9540ce6fc9 > > 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: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2
You can't simply delete the old one. Because ShardingSphere has existing release based on that KEY :) We could still continue in this way, but it should not be recommended if your old key is still available. Sheng Wu 吴晟 Twitter, wusheng1108 Juan Pan 于2020年1月2日周四 上午10:18写道： > Hi Liang, > > > If you plan not to use the old one any more, deleting is is an alternative > to avoid confusion. If so, it is necessary to delete it in KEYS file and > public key servers, IMO. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/1/2020 21:26，Sheng Wu wrote： > My concern is making people confused. The PGP could export and import from > the old laptop. You don't need a new one. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2020年1月1日周三 下午8:55写道： > > A question, why you have two pgp keys in the KEYS file? > > I change a computer, the 1st one is for the 4.0.0-RC1, the 4th one is for > this version. > Do you think we could remove the 1st one? because I will never use that gpp > key again, but do we need to keep it to make the 4.0.0-RC1 can be validate? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Sheng Wu 于2020年1月1日周三 下午8:34写道： > > Hi Liang Zhang > > A question, why you have two pgp keys in the KEYS file? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2019年12月30日周一 下午9:44写道： > > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0 > > 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/ > > Maven 2 staging repository: > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1029/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0/ > > Release Commit ID: > > > > > https://github.com/apache/incubator-shardingsphere/commit/f81f4f03b1dd4b426adf1f29ffe93f9540ce6fc9 > > 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: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2
Hi Liang Zhang A question, why you have two pgp keys in the KEYS file? Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2019年12月30日周一 下午9:44写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere (Incubating) > version 4.0.0 > > 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/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1029/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0/ > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/f81f4f03b1dd4b426adf1f29ffe93f9540ce6fc9 > > 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: opentracing dependency upgrade to 0.31.0
Hi Feedback on behalf of SkyWalking PMC and ShardingSphere PPMC. OpenTracing is not widely used today. And 0.31 breaks many APIs in 0.30, and causes a lot of confusion. SkyWalking community has no one following this update and no user feedback about this. An update, OpenTracing and OpenCensus projects are merging into OpenTelemetry. A lot of APIs are there... Not sure what are the purposes even I am in the core team of OpenTracing. Anyway, SkyWalking and other APMs could provide auto instrumentation very easily for ShardingSphere. There is no point to add workload to upgrade to 0.31 and break the ecosystem. Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2019年12月25日周三 上午11:42写道： > Hi sanmu, > > 1. ShardingSphere now keeps consistent with SkyWalking use the ot 0.30.0. > 2. Yes, there's no spi now. But I thinks #2478 will not influence you when > using 0.31.0. > 3. Welcome you to submit a PR. It will be perfect if you finish the test > ahead. > > Sanmu Wang 于2019年12月25日周三 上午10:58写道： > > > Hi, > > > > I'm trying to adapt sharding sphere to my company inner APM service( > lowest > > opentracing version supported is 0.31.0 ), however opentracing dependency > > is 0.30.0 and I didn't found any spi implementation for > > sharding-opentracing module(checked this issue > > https://github.com/apache/incubator-shardingsphere/issues/2478). > > *Is there any plan to upgrade opentracing dependency to 0.31.0 > officially?* > > (Perhaps I can supply PR on this). > > > > Thank you! > > > > > -- > > > Zhang Yonglun > Apache ShardingSphere >
Re: Discussion of pluggable platform of ShardingSphere
+1 Love the idea. Just feeling the project name(Sharding) will be the bottleneck :P Sheng Wu 吴晟 Twitter, wusheng1108 zhangli...@apache.org 于2019年12月9日周一 下午1:30写道： > 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
zhaojun 于2019年12月9日周一 上午10:21写道： > @Sheng > > Maybe you have misunderstood what i have said. > I meant if we have not an acceptance-test framework, maybe we will spend > another several months to process release work. > This is a critical problems we should face with. > No very critical I think :) Agree that, it is important and ease the PPMC/committer team concerns when doing the release. For 4.0.0, I think we should be ready to go. We are as same as all other libraries, could send 4.0.1, 4.0.2, if we are really facing serious bug. My point it only, let's finish no stable version status of ss, it has last one year, it is not good for users. Sheng Wu 吴晟 Twitter, wusheng1108 > > -- > Zhao Jun (cherrylzhao) > Apache Sharding-Sphere & ServiceComb > > > On Dec 8, 2019, at 10:50 PM, 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, &
Re: 4.0.0 stable version release plan
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: 4.0.0 stable version release plan
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(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 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
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: What is the update of ShardingSphere new version plugin?
Zhang Yonglun 于2019年12月2日周一 下午5:28写道： > OK. I think RC1 and RC2 could share the same plugin, RC3 and 4.0.0 will > share a same plugin. > I'll test RC2 and develop RC3 plugin next week with Haitao or Zesi. That > bug also will be fixed together. > I think the migration of plugin test cases can also be finished in the next > week. > Thanks for the update. I am forwarding this info to SkyWalking dev ML. Sheng Wu 吴晟 Twitter, wusheng1108 > > Zhang Yonglun > Apache ShardingSphere > > > zhangli...@apache.org 于2019年12月2日周一 下午5:15写道： > > > We can keep all rc versions even after 4.0 version released. > > So I'd like to add all plugins later. > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > Zhang Yonglun 于2019年12月2日周一 下午4:35写道： > > > > > Sorry, I meant there's only one shardingsphere 4.0.0 plugin finally for > > > 4.x, because all other 4.x versions are RC versions. > > > > > > > > > Zhang Yonglun > > > Apache ShardingSphere > > > > > > > > > Sheng Wu 于2019年12月2日周一 下午3:51写道： > > > > > > > So, ShardingSphere will abandon all existing plugins for all old > > > versions? > > > > What do you mean about only one plugin? > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > > > > Zhang Yonglun 于2019年12月2日周一 下午3:49写道： > > > > > > > > > Yes, there's only one shardingsphere 4.0.0 plugin finally. > > > > > > > > > > > > > > > Zhang Yonglun > > > > > Apache ShardingSphere > > > > > > > > > > > > > > > Sheng Wu 于2019年12月2日周一 下午2:59写道： > > > > > > > > > > > So, shardingsphere will give up the plugin for RC3, am I right? > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > Zhang Yonglun 于2019年12月2日周一 上午9:52写道： > > > > > > > > > > > > > Hi Sheng, > > > > > > > > > > > > > > As I know ShardingSphere-4.0.0 will be released soon. Once the > > > > release > > > > > > > launch, all the RC releases plugin get useless. > > > > > > > So I prefer to deal with these issues you mentioned in the new > > > > release. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Zhang Yonglun > > > > > > > Apache ShardingSphere > > > > > > > > > > > > > > > > > > > > > Sheng Wu 于2019年12月1日周日 下午3:46写道： > > > > > > > > > > > > > > > Hi ShardingSphere community, especially for Yonglun, Juan > > > > > > > > > > > > > > > > The ShardingSphere internal APIs related to instrumentation > > have > > > > been > > > > > > > > changed in RC3, so this issue[1] created to track the > progress. > > > > Could > > > > > > > > anyone sync to me, what is status? And what is the ETA? > > Including > > > > > > > > 1. ShardingSphere plugin needs to move into the current test > > > > > framework > > > > > > as > > > > > > > > step 1[2] > > > > > > > > 2. A high possibility of ShardingSphere plugin bug[3] > requires > > > the > > > > > > > > feedback. Does ShardingSphere community know anything about > > this > > > > one? > > > > > > > This > > > > > > > > is not likely a SkyWalking bug. > > > > > > > > > > > > > > > > [1] https://github.com/apache/skywalking/issues/3777 > > > > > > > > [2] https://github.com/apache/skywalking/issues/3583 > > > > > > > > [3] https://github.com/apache/skywalking/issues/3984 > > > > > > > > > > > > > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: What is the update of ShardingSphere new version plugin?
Juan Pan 于2019年12月2日周一 下午4:27写道： > Hi Sheng and Yonglun, > > > Keep in mind i do not know ShardingSphere plugin well, here is my > understanding. > > > ShardingSphere plugin for Skywalking is based on legacy version of > ShardingSphere, so there is no problem if user adopt legacy ShardingSphere > + any version Skywalking. Now the point is whether we should provide > enhancement to make ShardingSphere plugin compatible with latest version of > ShardingSphere, right? > Yes. This happened before RC3 released and should be a bug for RC1 or RC2. If you don't intend to fix, please reply to the issue, then I could close it, and ask the user to wait for a new plugin and new release. Sheng Wu 吴晟 Twitter, wusheng1108 > However ISSUE[1] is likely to be a bug for current ShardingSphere plugin. > > > @Liang, what do you think? > > > [1] https://github.com/apache/skywalking/issues/3984 > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 12/2/2019 15:50，Sheng Wu wrote： > So, ShardingSphere will abandon all existing plugins for all old versions? > What do you mean about only one plugin? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Zhang Yonglun 于2019年12月2日周一 下午3:49写道： > > Yes, there's only one shardingsphere 4.0.0 plugin finally. > > > Zhang Yonglun > Apache ShardingSphere > > > Sheng Wu 于2019年12月2日周一 下午2:59写道： > > So, shardingsphere will give up the plugin for RC3, am I right? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Zhang Yonglun 于2019年12月2日周一 上午9:52写道： > > Hi Sheng, > > As I know ShardingSphere-4.0.0 will be released soon. Once the release > launch, all the RC releases plugin get useless. > So I prefer to deal with these issues you mentioned in the new release. > > > > > Zhang Yonglun > Apache ShardingSphere > > > Sheng Wu 于2019年12月1日周日 下午3:46写道： > > Hi ShardingSphere community, especially for Yonglun, Juan > > The ShardingSphere internal APIs related to instrumentation have been > changed in RC3, so this issue[1] created to track the progress. Could > anyone sync to me, what is status? And what is the ETA? Including > 1. ShardingSphere plugin needs to move into the current test > framework > as > step 1[2] > 2. A high possibility of ShardingSphere plugin bug[3] requires the > feedback. Does ShardingSphere community know anything about this one? > This > is not likely a SkyWalking bug. > > [1] https://github.com/apache/skywalking/issues/3777 > [2] https://github.com/apache/skywalking/issues/3583 > [3] https://github.com/apache/skywalking/issues/3984 > > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > >
Re: What is the update of ShardingSphere new version plugin?
So, ShardingSphere will abandon all existing plugins for all old versions? What do you mean about only one plugin? Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2019年12月2日周一 下午3:49写道： > Yes, there's only one shardingsphere 4.0.0 plugin finally. > > > Zhang Yonglun > Apache ShardingSphere > > > Sheng Wu 于2019年12月2日周一 下午2:59写道： > > > So, shardingsphere will give up the plugin for RC3, am I right? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Zhang Yonglun 于2019年12月2日周一 上午9:52写道： > > > > > Hi Sheng, > > > > > > As I know ShardingSphere-4.0.0 will be released soon. Once the release > > > launch, all the RC releases plugin get useless. > > > So I prefer to deal with these issues you mentioned in the new release. > > > > > > > > > > > > > > > Zhang Yonglun > > > Apache ShardingSphere > > > > > > > > > Sheng Wu 于2019年12月1日周日 下午3:46写道： > > > > > > > Hi ShardingSphere community, especially for Yonglun, Juan > > > > > > > > The ShardingSphere internal APIs related to instrumentation have been > > > > changed in RC3, so this issue[1] created to track the progress. Could > > > > anyone sync to me, what is status? And what is the ETA? Including > > > > 1. ShardingSphere plugin needs to move into the current test > framework > > as > > > > step 1[2] > > > > 2. A high possibility of ShardingSphere plugin bug[3] requires the > > > > feedback. Does ShardingSphere community know anything about this one? > > > This > > > > is not likely a SkyWalking bug. > > > > > > > > [1] https://github.com/apache/skywalking/issues/3777 > > > > [2] https://github.com/apache/skywalking/issues/3583 > > > > [3] https://github.com/apache/skywalking/issues/3984 > > > > > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > >
