Re: [VOTE] Release Apache ShardingSphere 5.1.0 [round 4]
Hi, +1 I checked: - signatures and hashes are fine - LICENSE and NOTICE are fine - All source have ASF headers - No unexpected binary files - Can compile from source -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere Haoran Meng 于2022年2月9日周三 19:03写道： > > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere version 5.1.0 > > Release notes: > https://github.com/apache/shardingsphere/blob/5.1.0/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/5.1.0/ > > Maven 2 staging repository: > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1077/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere/tree/5.1.0/ > > Release Commit ID: > https://github.com/apache/shardingsphere/commit/938a4bcc553d350ca5936fed36965ee0c0a0c1ad > > 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/ > > GPG user ID: > menghaoran > > 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. > > -- > Best, > Haoran Meng > Apache ShardingSphere
Re: [ANNOUNCE] New committer: Thanoshan MV
Welcome on board! -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere Juan Pan 于2021年11月17日周三 上午10:10写道： > Hello community, > > > The Project Management Committee (PMC) for Apache ShardingSphere > has invited Thanoshan MV to become a committer, and we are pleased to > announce that he has accepted. > > > Thanoshan MV helped proofread a large chunk of parser files and provided > his help to the community. Thanks for your contributions. Hope see your > further interactions with the community! > > > Fellows, could we have your welcome to our new committer? > > > Regards, > Trista > > -- > Juan Pan(Trista), Twitter: @tristaZero > >
Re: [VOTE] Release Apache ShardingSphere ElasticJob UI 3.0.0
+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. -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere 吴伟杰 于2021年7月15日周四 上午11:04写道： > 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: [VOTE] Release Apache ShardingSphere 5.0.0-beta
+1 binding Please note that the year in the NOTICE file is still 2020, you may want to update it after this release. I have 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. -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere Zhang Yonglun 于2021年6月15日周二 上午11:47写道： > Kindly reminder, please list what you have checked before vote. > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere > > > Juan Pan 于2021年6月13日周日 下午1:21写道： > >> Hello ShardingSphere Community, >> >> >> This is a call for vote to release Apache ShardingSphere version >> 5.0.0-beta >> >> >> 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-beta/ >> >> >> Maven 2 staging repository: >> >> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1061/org/apache/shardingsphere/ >> >> >> Git tag for the release: >> https://github.com/apache/shardingsphere/tree/5.0.0-beta/ >> >> >> Release Commit ID: >> >> https://github.com/apache/shardingsphere/commit/9bb3dfd975c88344786e86c2a712fec218085bbc >> >> >> 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: >> panjuan >> >> >> 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. >> >> >> >> -- >> Juan Pan(Trista), Apache ShardingSphere PMC >> Twitter, @trista86934690 >> >>
Re: [VOTE] Release Apache ShardingSphere 5.0.0-beta
Kindly reminder, please list what you have checked before vote. -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere Juan Pan 于2021年6月13日周日 下午1:21写道： > Hello ShardingSphere Community, > > > This is a call for vote to release Apache ShardingSphere version 5.0.0-beta > > > 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-beta/ > > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1061/org/apache/shardingsphere/ > > > Git tag for the release: > https://github.com/apache/shardingsphere/tree/5.0.0-beta/ > > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/9bb3dfd975c88344786e86c2a712fec218085bbc > > > 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: > panjuan > > > 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. > > > > -- > Juan Pan(Trista), Apache ShardingSphere PMC > Twitter, @trista86934690 > >
Re: [VOTE] Release Apache ShardingSphere ElasticJob UI 3.0.0-RC1
+1 binding 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. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年12月29日周二 下午12:32写道： > +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. > > I find some minor problem, we can fix them at next release. > > 1. mvnw's file permission is not correct in mac os, we need to change the > assembly file to fix it. > 2. We are missing licenses of `jsr305-3.0.2`, > `geronimo-jms_1.1_spec-1.1.1`, `geronimo-jpa_2.2_spec-1.1`, > `geronimo-jta_1.1_spec-1.1.1` in > `apache-shardingsphere-elasticjob-3.0.0-RC1-lite-ui-bin.tar.gz`. I checked > them, the licenses of them are all compatible with Apache 2.0. > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere > > > > Hongtao Gao 于2020年12月28日周一 上午8:15写道： > > > +1 (binding) > > > > I had checked the below items: > > 1. asc,*sha512 files are correct. > > 2. Build from source code successfully. > > 3. Source and binary packages contain LICENSE and NOTICE files. > > 4. Checks source files license headers. > > > > Good luck > > > > > > 吴伟杰 于2020年12月27日周日 下午12:14写道： > > > > > Hello ShardingSphere Community, > > > > > > This is a call for vote to release Apache ShardingSphere ElasticJob UI > > > version 3.0.0-RC1 > > > > > > 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-RC1/ > > > > > > Git tag for the release: > > > https://github.com/apache/shardingsphere-elasticjob-ui/tree/3.0.0-RC1/ > > > > > > Release Commit ID: > > > > > > > > > https://github.com/apache/shardingsphere-elasticjob-ui/commit/d46c9bc9ebc500506badefbc9aaa24e89c72f395 > > > > > > 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 user ID: > > > wuweijie > > > > > > 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. > > > > > > -- > > > > > > Sincerely, > > > Weijie Wu (TeslaCN) > > > Apache ShardingSphere > > > > > >
Re: [VOTE] Release Apache ShardingSphere ElasticJob-3.0.0-RC1
+1 binding 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. -- Zhang Yonglun Apache ShardingSphere Juan Pan 于2020年12月24日周四 下午9:37写道： > My +1 binding, checking items are the following, > > > > > [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. > > > > > > --- > Email：panj...@apache.org > Juan Pan(Trista) Apache ShardingSphere > > > On 12/19/2020 11:37，吴伟杰 wrote： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere > ElasticJob-3.0.0-RC1 > > 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-RC1/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1059/org/apache/shardingsphere/elasticjob/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob/tree/3.0.0-RC1/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob/commit/e3607ee692001692128cf23efe66ee39dc1c277a > > 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/ > > GPG user ID: > wuweijie > > 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. > > -- > > Sincerely, > Weijie Wu (TeslaCN) > Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere UI 5.0.0-alpha [Round 2]
+1 I have 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. -- Zhang Yonglun Apache ShardingSphere Haoran Meng 于2020年11月17日周二 下午7:48写道： > +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. > > Juan Pan 于2020年11月17日周二 上午9:58写道： > > > Hello ShardingSphere Community, > > > > > > This is a call for vote to release Apache ShardingSphere UI version > > 5.0.0-alpha > > > > > > Release notes: > > https://github.com/apache/shardingsphere-ui/blob/master/RELEASE-NOTES.md > > > > > > The release candidates: > > > > > https://dist.apache.org/repos/dist/dev/shardingsphere/shardingsphere-ui-5.0.0-alpha/ > > > > > > Git tag for the release: > > https://github.com/apache/shardingsphere-ui/tree/5.0.0-alpha/ > > > > > > Release Commit ID: > > > > > https://github.com/apache/shardingsphere-ui/commit/4d90dbaff9d8f3d334c8104ab289bea6b33fdb9b > > > > > > 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_ui/ > > > > > > GPG user ID: > > panjuan > > > > > > 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. > > > > > > Juan Pan (Trista) > > > > Senior DBA & PMC of Apache ShardingSphere > > E-mail: panj...@apache.org > > > > > > > > > > -- > Haoran Meng > menghaora...@gmail.com >
Re: [VOTE] Release Apache ShardingSphere 5.0.0-alpha
+1 binding [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. -- Zhang Yonglun Apache ShardingSphere Juan Pan 于2020年11月3日周二 下午12:29写道： > Hello ShardingSphere Community, > > > This is a call for vote to release Apache ShardingSphere version > 5.0.0-alpha. > > > 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-alpha/ > > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1058/org/apache/shardingsphere/ > > > Git tag for the release: > https://github.com/apache/shardingsphere/tree/5.0.0-alpha > > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/5dc690c2227571e83beada277dbb2dfb43c29427 > > > 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: > panjuan > > > 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. > > > > > Juan Pan (Trista) > > Senior DBA & PMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > >
Re: [VOTE] Release Apache ShardingSphere ElasticJob UI 3.0.0-beta
+1 binding [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. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年10月26日周一 下午1:23写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere ElasticJob UI > version 3.0.0-beta > > 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-beta/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob-ui/tree/3.0.0-beta/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob-ui/commit/e515054bbb165667fd34fda528f7bce15e94a23b > > 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 user ID: > zhangliang > > 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. > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere ElasticJob-3.0.0-beta [Round 4]
+1 binding [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] No compiled archives bundled in source archive. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年10月31日周六 下午10:58写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere > ElasticJob-3.0.0-beta > > 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-beta/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1056/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob/tree/3.0.0-beta/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob/commit/a842f4c86b38b2c3fa8ca611fb0724e5a47a36c8 > > 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/ > > GPG user ID: > zhangliang > > 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. > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: [VOTE] Release Apache ElasticJob UI 3.0.0-alpha
+1 binding. I have checked the following items: [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. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年8月11日周二 下午4:33写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere ElasticJob UI > version 3.0.0-alpha > > 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-alpha/ > > Git tag for the release: > > https://github.com/apache/shardingsphere-elasticjob-ui/tree/shardingsphere-elasticjob-ui-3.0.0-alpha/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob-ui/commit/174661dc77366eb8ab0742ac61ab0f5c84a60f2c > > 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 user ID: > zhangliang > > 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. > > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: [VOTE] Release Apache ShardingSphere ElasticJob-3.0.0-alpha
+1 binding. I have checked the following items: [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. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年8月5日周三 上午1:39写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere > ElasticJob-3.0.0-alpha > > 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-alpha/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1052/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere-elasticjob/tree/3.0.0-alpha/ > > Release Commit ID: > > https://github.com/apache/shardingsphere-elasticjob/commit/11ca056e5d58825a102981e6e25703b6748ca890 > > 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/ > > GPG user ID: > zhangliang > > 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. > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: SO slow to insert 5K record one time using Sharding-JDBC
It is the parsing module cost so much time. You can update the Sharding-JDBC to 4.1.0 or above to solve the problem. Please refer to the release notes of 4.1.0: https://github.com/apache/shardingsphere/releases/tag/4.1.0 -- Zhang Yonglun Apache ShardingSphere Terry Zhang 于2020年8月4日周二 下午6:37写道： > Hi, ShardingSphere community, > > > > We are using Sharding-Sphere 4.0.RC2 in our project for a long time. > Recently, we are encountering a serious issue struggling us. When we try to > insert 5K records one time into one table, it takes about 40 seconds. > However, when the execution time is about 0.11 second according to MySQL > Audit log. > > > > To figure our the root reason, we try to disable ShardingSphere and use > native JDBC instead, the result is very positive. It is so quick to execute > the same SQL. It is about 0.2s. > > > > Based on above findings, we think ShardingJDBC may cause it happen. > > > > To solve it, we are finding the possible solution. Here is our solution, > as not all of MySQL tables need to use sharding feature. we have those > non-sharding tables keep to use the native JDBC, not use ShardingJDBC. To > implement it, we try to find the way to implement it according to the > official document, unfortunately, we don’t find the best way. > > > > How to implement our solution? Alternatively, any other solution to > resolve it? > > > > To help to understand it easily ,here is some information for the > reference. > > > > The format of SQL DML like this-- > > INSERT INTO tbl_orders (id,f2,f3,) VALUES (1,xx,xx,...), > (2,xx,xx,...), (3,xx,xx,...), ...,(5000,xx,xx,...). > > Please note, the table tbl_orders is a non-sharding table. > > > > -- Java > > Java 1.8 > > > > MySQL--- > > MySQL 5.7 > > > > --OS -- > > CentOS 7.2 > > > > > > > > Terry
Re: [DISCUSS] Archive elasticjob-cloud
Any comments? -- Zhang Yonglun Apache ShardingSphere Zhang Yonglun 于2020年7月15日周三 上午10:59写道： > We should archive the following repo: > > https://github.com/apache/shardingsphere-elasticjob-cloud > > All codes of this repo have been merged into > shardingsphere-elasticjob-lite, so we don't need this repo any more. > > -- > > Zhang Yonglun > Apache ShardingSphere >
[DISCUSS] Archive elasticjob-cloud
We should archive the following repo: https://github.com/apache/shardingsphere-elasticjob-cloud All codes of this repo have been merged into shardingsphere-elasticjob-lite, so we don't need this repo any more. -- Zhang Yonglun Apache ShardingSphere
Re: [DISCUSS] Rename ShardingSphere GitHub/GitBox repo
Hi Zonglei, elasticjob-cloud will be merged into elasticjob-lite, so there's only one elasticjob after that. Please refer to https://github.com/apache/shardingsphere-elasticjob-lite/issues/999 . -- Zhang Yonglun Apache ShardingSphere Zonglei Dong 于2020年7月9日周四 下午4:39写道： > Hi Yonglun, > > > Why do we need to change the repo's name? > > > If we remove the suffix, how to make a difference with > "shardingsphere-elasticjob-cloud" repo? > > > Thanks. > > -- > > Zonglei Dong > Apache ShardingSphere > > > > > > At 2020-07-09 15:23:39, "Zhang Yonglun" wrote: > >Hi community, > > > >I'd like to rename the elasticjob repo below. Any comments? > > > >From: > >https://github.com/apache/shardingsphere-elasticjob-lite > > > >To: > >https://github.com/apache/shardingsphere-elasticjob > > > >-- > > > >Zhang Yonglun > >Apache ShardingSphere >
Re: Discuss ElasticJob lite 3.0.0-alpha release
Is the elastic-job-lite-console module included in this release? If so the License issue( https://github.com/apache/shardingsphere-elasticjob-lite/issues/759) of front-end should be resolved before start releasing. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年7月7日周二 下午12:54写道： > Hi All, > > I want to discuss about ElasticJob lite 3.0.0-alpha release. > We have already develop ElasticJob for a month. > I am glad to see our community are active and excellent. > > Now we can discuss the release scope of the 1st apache release. > I prefer to name the 1st version as ElasticJob lite 3.0.0-alpha, which to > let users test it. > > The scope include: > > 1. New Job API for simplify configuration; > 2. New Job for customize job type dynamically; > 3. New spring namespace; > 4. One-off Bootstrap supported; > 5. Decouple Job executor and core module; > 6. Decouple event tracing module and core module; > 7. More database type supported of event tracing; > 8. Adjust snapshot service from Job level to Register center level. > 9. Upgrade Java version to JDK 8 and update some dependencies version. > 10. Fixes some bugs. > > Any thing else for the new release? > > -- > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere >
Re: [DISCUSS] Rename ShardingSphere GitHub/GitBox repo
Hi Zonglei, We have already merged docs and examples to the two main repos. As to whether we can merge cloud to lite, it depends. -- Zhang Yonglun Apache ShardingSphere Zonglei Dong <598363...@qq.com> 于2020年6月17日周三 上午11:38写道： > +1, Great! > > > There is another problem, can we merge those four repos to one repo, or in > the future? > > > > > --原始邮件------ > 发件人:"Zhang Yonglun" 发送时间:2020年6月17日(星期三) 上午10:59 > 收件人:"dev" > 主题:[DISCUSS] Rename ShardingSphere GitHub/GitBox repo > > > > Hi community, > > I'd like to rename these elastic-job repos below, just like what we did for > sharding-sphere before. Any comments? > > From: > https://github.com/apache/shardingsphere-elastic-job-lite > https://github.com/apache/shardingsphere-elastic-job-cloud > https://github.com/apache/shardingsphere-elastic-job-example > https://github.com/apache/shardingsphere-elastic-job-doc > > To: > https://github.com/apache/shardingsphere-elasticjob-lite > https://github.com/apache/shardingsphere-elasticjob-cloud > https://github.com/apache/shardingsphere-elasticjob-example > https://github.com/apache/shardingsphere-elasticjob-doc > > -- > > Zhang Yonglun > Apache ShardingSphere
[DISCUSS] Rename ShardingSphere GitHub/GitBox repo
Hi community, I'd like to rename these elastic-job repos below, just like what we did for sharding-sphere before. Any comments? From: https://github.com/apache/shardingsphere-elastic-job-lite https://github.com/apache/shardingsphere-elastic-job-cloud https://github.com/apache/shardingsphere-elastic-job-example https://github.com/apache/shardingsphere-elastic-job-doc To: https://github.com/apache/shardingsphere-elasticjob-lite https://github.com/apache/shardingsphere-elasticjob-cloud https://github.com/apache/shardingsphere-elasticjob-example https://github.com/apache/shardingsphere-elasticjob-doc -- Zhang Yonglun Apache ShardingSphere
Re: Consider to remove the incubator release?
Deleted. We can still find these releases in the archive repository https://archive.apache.org/dist/incubator/shardingsphere/ . -- Zhang Yonglun Apache ShardingSphere Zhang Yonglun 于2020年6月11日周四 下午12:04写道： > Agree. Incubator releases are no longer recommended public use. > > According to https://infra.apache.org/mirrors , I will delete the whole > directory > https://dist.apache.org/repos/dist/release/incubator/shardingsphere/ . > > Any comments? > > -- > > Zhang Yonglun > Apache ShardingSphere > > > Sheng Wu 于2020年6月10日周三 下午10:25写道： > >> 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: [VOTE] Release Apache ShardingSphere UI 4.1.1
+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. -- Zhang Yonglun Apache ShardingSphere KimmKing 于2020年6月9日周二 上午3:30写道： > Hello ShardingSphere Community, > > > > > This is a call for vote to release Apache ShardingSphere UI version 4.1.1. > > > > > Release notes: > > > https://github.com/apache/shardingsphere/blob/master/shardingsphere-ui/RELEASE-NOTES.md > > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/shardingsphere/shardingsphere-ui-4.1.1/ > > > > > Git tag for the release: > > https://github.com/apache/shardingsphere/tree/shardingsphere-ui-4.1.1/ > > > > > Release Commit ID: > > > https://github.com/apache/shardingsphere/commit/87a34228da5a787d925e89ab1942d6f5cda4fa8b > > > > > 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_ui/ > > > > > GPG user ID: > > kimmking > > > > > 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: About count query in sharding-proxy 4.0.0-RC2
4.0.0-RC2 is too old. Can you change ther Proxy version to 4.1.1 just released? You can download from https://shardingsphere.apache.org/document/current/en/downloads/ . -- Zhang Yonglun Apache ShardingSphere Kai Yu 于2020年6月11日周四 下午4:19写道： > Hi: >We test again, the cost use Proxy to route to only one database : > > “select count(*) from member where merchant_id = 'dwj'” > > the cost is : > 4.32 sec > > its looks like the same cost of count query to one server（ db0 or db1） > ,like this. > > so , the same question > query cost 25s with 16databases, why? > ________ > 发件人: Zhang Yonglun > 发送时间: 2020年6月4日 17:27 > 收件人: dev > 主题: Re: About count query in sharding-proxy 4.0.0-RC2 > > Get it. What about the cost use Proxy to route to only one database? > Actually merging just consume little time. > > -- > > Zhang Yonglun > Apache ShardingSphere > > > Kai Yu 于2020年6月4日周四 下午4:56写道： > > > hi: > >thx for your replay, > >our machine'environment is aliyun RDS 4C8G > > The 16 machines have same environment, it means one RDS one database,We > > have 16 RDS. > > Every databases have one table named 'member', the table have almost two > > million rows, it means 16databases total have > > thirty million rows . > > > > we connect to every server（from db0 to db15） , execute count sql is > > “select count(*) from member where merchant_id = 'dwj'” > > the cost is : > > > db0 (4.97 sec) > > > db1 (4.83 sec) > > > db2 (5.23 sec) > > > db3 (4.94 sec) > > > db4 (5.12 sec) > > > db5 (5.86 sec) > > > db6 (5.31 sec) > > > db7 (5.03 sec) > > > db8 (5.37 sec) > > > db9 (5.66 sec) > > > db9 (5.75 sec) > > > db10 (5.49 sec) > > > db11 (5.11 sec) > > > db12 (4.98 sec) > > > db13 (5.72 sec) > > > db14 (5.33 sec) > > > db15 (5.15 sec) > > ________ > > 发件人: Zhang Yonglun > > 发送时间: 2020年6月4日 14:03 > > 收件人: dev > > 主题: Re: About count query in sharding-proxy 4.0.0-RC2 > > > > If so, I suggest you connect all 16 databases and record the time cost > for > > each. > > Also, please show your hardware environment. > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > Kai Yu 于2020年6月3日周三 下午5:23写道： > > > > > Hi: > > >before i send last email ,i didn't add this props, > > > after I add props in server.yml , by the config like this: > > > max.connections.size.per.query: 64 > > > acceptor.size: 64 > > > executor.size: 64 > > > the count query sql cost 25s > > > > > > I changed props ,increase to 128 or 256 ,the count query sql cost still > > > between 24-26s > > > > > > > > > Is this situation normal ? > > > > > > Is there a way to continue improve this ? thanks > > > > > > 发件人: Kai Yu > > > 发送时间: 2020年6月3日 15:16 > > > 收件人: dev@shardingsphere.apache.org > > > 主题: About count query in sharding-proxy 4.0.0-RC2 > > > > > > Hi ALL : > > > we have a project used 16 databases (db0 ...db15)，we used > > > sharding-proxy 4.0.0-RC2 , > > > and config the sharding.xml like this: > > > schemaName: ty-basic-member > > > dataSources: > > > db0: > > > url: jdbc:mysql://xxx:3306/db0?useSSL=false > > > username: root > > > password: root > > > connectionTimeoutMilliseconds: 3 > > > idleTimeoutMilliseconds: 6 > > > maxLifetimeMilliseconds: 180 > > > maxPoolSize: 65 > > > ... > > > db15: > > > url: jdbc:mysql://xxx:3306/db15?useSSL=false > > > username: root > > > password: root > > > connectionTimeoutMilliseconds: 3 > > > idleTimeoutMilliseconds: 6 > > > maxLifetimeMilliseconds: 180 > > > maxPoolSize: 65 > > > > > > shardingRule: > > > tables: > > > member: > > > actualDataNodes: > > > > > > dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member > > > databaseStrategy: > > > complex: > > > algorithmClassName: > > > com.toonyoo.app.sharding.
Re: Consider to remove the incubator release?
Agree. Incubator releases are no longer recommended public use. According to https://infra.apache.org/mirrors , I will delete the whole directory https://dist.apache.org/repos/dist/release/incubator/shardingsphere/ . Any comments? -- Zhang Yonglun Apache ShardingSphere Sheng Wu 于2020年6月10日周三 下午10:25写道： > 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?
Done. Become better now. Yes, the Infra told me the same way. Thanks for reminding me. -- Zhang Yonglun Apache ShardingSphere Sheng Wu 于2020年6月10日周三 上午11:49写道： > 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?
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: [VOTE] Release Apache ShardingSphere 4.1.1
binding +1, I checked [X] Download links are valid. [X] Checksums and GPG signatures are valid. [X] Source code distributions have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. [X] All files have license headers if necessary. [X] No compiled archives bundled in source archive. -- Zhang Yonglun Apache ShardingSphere KimmKing 于2020年6月5日周五 上午7:06写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere version 4.1.1 > > Release notes: > https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.1/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1051/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere/tree/4.1.1/ > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/96375f420074a8a4cba5307f1a308f3a87b3c7bf > > 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: > kimmking > > 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: About count query in sharding-proxy 4.0.0-RC2
Get it. What about the cost use Proxy to route to only one database? Actually merging just consume little time. -- Zhang Yonglun Apache ShardingSphere Kai Yu 于2020年6月4日周四 下午4:56写道： > hi: >thx for your replay, >our machine'environment is aliyun RDS 4C8G > The 16 machines have same environment, it means one RDS one database,We > have 16 RDS. > Every databases have one table named 'member', the table have almost two > million rows, it means 16databases total have > thirty million rows . > > we connect to every server（from db0 to db15） , execute count sql is > “select count(*) from member where merchant_id = 'dwj'” > the cost is : > > db0 (4.97 sec) > > db1 (4.83 sec) > > db2 (5.23 sec) > > db3 (4.94 sec) > > db4 (5.12 sec) > > db5 (5.86 sec) > > db6 (5.31 sec) > > db7 (5.03 sec) > > db8 (5.37 sec) > > db9 (5.66 sec) > > db9 (5.75 sec) > > db10 (5.49 sec) > > db11 (5.11 sec) > > db12 (4.98 sec) > > db13 (5.72 sec) > > db14 (5.33 sec) > > db15 (5.15 sec) > > 发件人: Zhang Yonglun > 发送时间: 2020年6月4日 14:03 > 收件人: dev > 主题: Re: About count query in sharding-proxy 4.0.0-RC2 > > If so, I suggest you connect all 16 databases and record the time cost for > each. > Also, please show your hardware environment. > > -- > > Zhang Yonglun > Apache ShardingSphere > > > Kai Yu 于2020年6月3日周三 下午5:23写道： > > > Hi: > >before i send last email ,i didn't add this props, > > after I add props in server.yml , by the config like this: > > max.connections.size.per.query: 64 > > acceptor.size: 64 > > executor.size: 64 > > the count query sql cost 25s > > > > I changed props ,increase to 128 or 256 ,the count query sql cost still > > between 24-26s > > > > > > Is this situation normal ? > > > > Is there a way to continue improve this ? thanks > > > > 发件人: Kai Yu > > 发送时间: 2020年6月3日 15:16 > > 收件人: dev@shardingsphere.apache.org > > 主题: About count query in sharding-proxy 4.0.0-RC2 > > > > Hi ALL : > > we have a project used 16 databases (db0 ...db15)，we used > > sharding-proxy 4.0.0-RC2 , > > and config the sharding.xml like this: > > schemaName: ty-basic-member > > dataSources: > > db0: > > url: jdbc:mysql://xxx:3306/db0?useSSL=false > > username: root > > password: root > > connectionTimeoutMilliseconds: 3 > > idleTimeoutMilliseconds: 6 > > maxLifetimeMilliseconds: 180 > > maxPoolSize: 65 > > ... > > db15: > > url: jdbc:mysql://xxx:3306/db15?useSSL=false > > username: root > > password: root > > connectionTimeoutMilliseconds: 3 > > idleTimeoutMilliseconds: 6 > > maxLifetimeMilliseconds: 180 > > maxPoolSize: 65 > > > > shardingRule: > > tables: > > member: > > actualDataNodes: > > > dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member > > databaseStrategy: > > complex: > > algorithmClassName: > > com.toonyoo.app.sharding.proxy.ProxyDBShardingAlgorithm > > shardingColumns: merchant_id,member_id > > logicTable: member > > > > there is a table named member, it has 3kw rows, then we test the query > > like this : > > case 1 > > we connect to the sharding-proxy application (like ip:3307 ) on > server > > , execute count sql: > > MySQL [ty-basic-member]> select count(*) from member where merchant_id = > > 'dwj'; > > +--+ > > | count(*) | > > +--+ > > | 34202355 | > > +--+ > > 1 row in set (37.59 sec) > > > > case 2 > >we connect to db0 on server , executecount sql: > > MySQL [db0]> select count(*) from member where merchant_id = 'dwj'; > > +--+ > > | count(*) | > > +--+ > > | 2217826 | > > +--+ > > 1 row in set (5.49 sec) > > > > > > we found the count query cost 37s with 16 database , > > we think the proxy component deal the 16database's query may cost 5s > like > > count query on db0 ，looks like Parallel ,we dont know why. > > > > Can you provide some technical details underlying principle for us to > > understand? > > thanks > > >
Re: About count query in sharding-proxy 4.0.0-RC2
Please refer to the docement of Execute Engine: https://shardingsphere.apache.org/document/current/en/features/sharding/principle/execute/ and Merge Engine: https://shardingsphere.apache.org/document/current/en/features/sharding/principle/merge/ -- Zhang Yonglun Apache ShardingSphere Kai Yu 于2020年6月3日周三 下午6:05写道： > hi > we think the count query from 16databases , in the end ,it seems every > database result to sum by sharding-proxy in memory ,we think it so fast. > for example , db0 count query cost 5s, by the sharding-proxy count > query cost 25s with 16databases, to deal with the count result need 20s > (25s-5s)? >we really want to know what the proxy do after the count query ? why > cost another 20s+? > thanks > > 发件人: Kai Yu > 发送时间: 2020年6月3日 17:23 > 收件人: dev@shardingsphere.apache.org > 主题: 回复: About count query in sharding-proxy 4.0.0-RC2 > > Hi: >before i send last email ,i didn't add this props, > after I add props in server.yml , by the config like this: > max.connections.size.per.query: 64 > acceptor.size: 64 > executor.size: 64 > the count query sql cost 25s > > I changed props ,increase to 128 or 256 ,the count query sql cost still > between 24-26s > > > Is this situation normal ? > > Is there a way to continue improve this ? thanks > > 发件人: Kai Yu > 发送时间: 2020年6月3日 15:16 > 收件人: dev@shardingsphere.apache.org > 主题: About count query in sharding-proxy 4.0.0-RC2 > > Hi ALL : > we have a project used 16 databases (db0 ...db15)，we used > sharding-proxy 4.0.0-RC2 , > and config the sharding.xml like this: > schemaName: ty-basic-member > dataSources: > db0: > url: jdbc:mysql://xxx:3306/db0?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > ... > db15: > url: jdbc:mysql://xxx:3306/db15?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > > shardingRule: > tables: > member: > actualDataNodes: > dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member > databaseStrategy: > complex: > algorithmClassName: > com.toonyoo.app.sharding.proxy.ProxyDBShardingAlgorithm > shardingColumns: merchant_id,member_id > logicTable: member > > there is a table named member, it has 3kw rows, then we test the query > like this : > case 1 > we connect to the sharding-proxy application (like ip:3307 ) on server > , execute count sql: > MySQL [ty-basic-member]> select count(*) from member where merchant_id = > 'dwj'; > +--+ > | count(*) | > +--+ > | 34202355 | > +--+ > 1 row in set (37.59 sec) > > case 2 >we connect to db0 on server , executecount sql: > MySQL [db0]> select count(*) from member where merchant_id = 'dwj'; > +--+ > | count(*) | > +--+ > | 2217826 | > +--+ > 1 row in set (5.49 sec) > > > we found the count query cost 37s with 16 database , > we think the proxy component deal the 16database's query may cost 5s like > count query on db0 ，looks like Parallel ,we dont know why. > > Can you provide some technical details underlying principle for us to > understand? > thanks >
Re: About count query in sharding-proxy 4.0.0-RC2
If so, I suggest you connect all 16 databases and record the time cost for each. Also, please show your hardware environment. -- Zhang Yonglun Apache ShardingSphere Kai Yu 于2020年6月3日周三 下午5:23写道： > Hi: >before i send last email ,i didn't add this props, > after I add props in server.yml , by the config like this: > max.connections.size.per.query: 64 > acceptor.size: 64 > executor.size: 64 > the count query sql cost 25s > > I changed props ,increase to 128 or 256 ,the count query sql cost still > between 24-26s > > > Is this situation normal ? > > Is there a way to continue improve this ? thanks > > 发件人: Kai Yu > 发送时间: 2020年6月3日 15:16 > 收件人: dev@shardingsphere.apache.org > 主题: About count query in sharding-proxy 4.0.0-RC2 > > Hi ALL : > we have a project used 16 databases (db0 ...db15)，we used > sharding-proxy 4.0.0-RC2 , > and config the sharding.xml like this: > schemaName: ty-basic-member > dataSources: > db0: > url: jdbc:mysql://xxx:3306/db0?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > ... > db15: > url: jdbc:mysql://xxx:3306/db15?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > > shardingRule: > tables: > member: > actualDataNodes: > dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member > databaseStrategy: > complex: > algorithmClassName: > com.toonyoo.app.sharding.proxy.ProxyDBShardingAlgorithm > shardingColumns: merchant_id,member_id > logicTable: member > > there is a table named member, it has 3kw rows, then we test the query > like this : > case 1 > we connect to the sharding-proxy application (like ip:3307 ) on server > , execute count sql: > MySQL [ty-basic-member]> select count(*) from member where merchant_id = > 'dwj'; > +--+ > | count(*) | > +--+ > | 34202355 | > +--+ > 1 row in set (37.59 sec) > > case 2 >we connect to db0 on server , executecount sql: > MySQL [db0]> select count(*) from member where merchant_id = 'dwj'; > +--+ > | count(*) | > +--+ > | 2217826 | > +--+ > 1 row in set (5.49 sec) > > > we found the count query cost 37s with 16 database , > we think the proxy component deal the 16database's query may cost 5s like > count query on db0 ，looks like Parallel ,we dont know why. > > Can you provide some technical details underlying principle for us to > understand? > thanks >
Re: About count query in sharding-proxy 4.0.0-RC2
In server.yaml, followling props effect the concurrency, you can have a try. max.connections.size.per.query: 64 acceptor.size: 64 executor.size: 64 -- Zhang Yonglun Apache ShardingSphere Kai Yu 于2020年6月3日周三 下午3:16写道： > Hi ALL : > we have a project used 16 databases (db0 ...db15)，we used > sharding-proxy 4.0.0-RC2 , > and config the sharding.xml like this: > schemaName: ty-basic-member > dataSources: > db0: > url: jdbc:mysql://xxx:3306/db0?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > ... > db15: > url: jdbc:mysql://xxx:3306/db15?useSSL=false > username: root > password: root > connectionTimeoutMilliseconds: 3 > idleTimeoutMilliseconds: 6 > maxLifetimeMilliseconds: 180 > maxPoolSize: 65 > > shardingRule: > tables: > member: > actualDataNodes: > dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member > databaseStrategy: > complex: > algorithmClassName: > com.toonyoo.app.sharding.proxy.ProxyDBShardingAlgorithm > shardingColumns: merchant_id,member_id > logicTable: member > > there is a table named member, it has 3kw rows, then we test the query > like this : > case 1 > we connect to the sharding-proxy application (like ip:3307 ) on server > , execute count sql: > MySQL [ty-basic-member]> select count(*) from member where merchant_id = > 'dwj'; > +--+ > | count(*) | > +--+ > | 34202355 | > +--+ > 1 row in set (37.59 sec) > > case 2 >we connect to db0 on server , executecount sql: > MySQL [db0]> select count(*) from member where merchant_id = 'dwj'; > +--+ > | count(*) | > +--+ > | 2217826 | > +--+ > 1 row in set (5.49 sec) > > > we found the count query cost 37s with 16 database , > we think the proxy component deal the 16database's query may cost 5s like > count query on db0 ，looks like Parallel ,we dont know why. > > Can you provide some technical details underlying principle for us to > understand? > thanks >
Re: [Vote] ElasticJob donation
+1 binding -- Zhang Yonglun Apache ShardingSphere 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: [DISCUSS]About a hotfix release version 4.1.1
+1. I will carry two other PRs to 4.1.1 for Sharding-Proxy fixed in 5.0.0. #3555, fix postgresql proxy return redundant command complete packet https://github.com/apache/shardingsphere/pull/5178 #3556, affect rows is always zero when using sharding-proxy postgresq https://github.com/apache/shardingsphere/pull/5194 -- Zhang Yonglun Apache ShardingSphere 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: Re: Fwd: Fwd: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』
I would like to be one of the mentors. -- Zhang Yonglun Apache ShardingSphere KimmKing 于2020年5月13日周三 下午1:48写道： > That sound great. I am joining too. > > > > > > 在 2020-05-07 11:30:18，"蒋晓峰" 写道： > >Sound great, I’d like to join to be a mentor! > > > >On Thu, May 7, 2020 at 10:24 AM Juan Pan wrote: > > > >> Sound great, I’d like to join to be a mentor! > >> > >> > >> Juan Pan (Trista) > >> > >> Senior DBA & PPMC of Apache ShardingSphere(Incubating) > >> E-mail: panj...@apache.org > >> > >> > >> > >> > >> 在2020年05月6日 20:32，zhangli...@apache.org 写道： > >> Hi PMC members and committers, > >> > >> ShardingSphere has applied the Institute of SoftwareChinese Academy of > >> Sciences > >> Summer of Code 2020. This is a China locate event like GSoC, but for > >> Chinese college students and in Chinese. > >> > >> They have replied to accept our application. After that, we will need > >> mentors and tasks suitable for college students, > >> especially for Computer Science and Software Engineer master candidates. > >> > >> Anyone especially committer, who wants to be the official mentor, please > >> let me know. > >> > >> If you have willing to do this, please reply to this. > >> > >> Brief > >> > >> ShardingSphere community request our PMC member/committer to join the > >> mentor team voluntarily. This program could have several mentors from > the > >> community. > >> > >> The mentors should be > >> > >> 1. Be familiar with the project. > >> 2. Be a committer or PMC member > >> 3. Have some available time to mentor students in 3 months. Several > hours > >> per week > >> Every mentor could propose 3(max) tasks with details, which could be > >> suitable for the colleague and master candidate. > >> 4. PMC should evaluate and assist the mentors to do their works, if some > >> ones need them. > >> 5. Have time to evaluate the results. > >> > >> [1] https://isrc.iscas.ac.cn/summer2020/#/ > >> > >> -- > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> -- Forwarded message - > >> 发件人： 暑期2020 组委会 > >> Date: 2020年5月6日周三 下午4:02 > >> Subject: 回复: Fwd: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』 > >> To: 张亮 > >> Cc: zhangli...@apache.org > >> > >> > >> 张亮老师， > >> > >> 您好，感谢您对“开源软件所供应链点亮计划-暑期2020”活动的关注，欢迎 ShardingSphere项目社区参与“暑期2020”活动。 > >> > >> “暑期2020“活动详情及常见问题见活动官网：https://isrc.iscas.ac.cn/summer2020/#/qa > >> > >> 在参与活动过程中如有问题，请随时联系。 > >> > >> 谢谢! > >> > >> > >> > >> “开源软件供应链点亮计划-暑期2020“工作组 > >> > >> > >> > >> *发件人: *张亮 > >> *发送时间: *2020年5月4日 9:55 > >> *收件人: *summer2020 > >> *主题: *Fw:Fwd: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』 > >> > >> > >> > >> > >> > >> > >> > >> 转发邮件信息 > >> 发件人："zhangli...@apache.org" > >> 发送日期：2020-05-04 09:52:31 > >> 收件人：terrym...@163.com > >> 主题：Fwd: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』 > >> > >> > >> > >> > >> -- > >> > >> > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> > >> > >> > >> -- Forwarded message - > >> 发件人： *zhangli...@apache.org * < > >> zhangli...@apache.org> > >> Date: 2020年5月3日周日 下午11:14 > >> Subject: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』 > >> To: > >> > >> > >> > >> 开源软件供应链点亮计划2020，组委会 > >> > >> 你好，我是Apache ShardingSphere项目VP和PMC成员。我代表社区，申请加入『开源软件供应链点亮计划2020』 > >> 申请通过后，此邮件会发送给项目管理委员会，并邀请更多的导师加入。 > >> > >> > >> > >> -- > >> > >> English Version > >> Hi, I am the VP and PMC member of Apache ShardingSphere. I am on behalf > of > >> the > >> community to request joining the event `开源软件供应链点亮计划2020`. > >> If we passed this, I will forward this application to the whole PMC > team, > >> and request more mentors besides myself. > >> > >> -- > >> > >> > >> > >> # 项目基本信息和联系方式 > >> > >> > >> > >> 1. 社区名称：Apache ShardingSphere > >> 2. 社区官方网址：https://shardingsphere.apache.org/ > >> 3. 社区Logo文件： > >> https://shardingsphere.apache.org/document/current/img/logo_v2.png > >> 4. 社区简短描述（30 字以内）：Apache软件基金会顶级项目，分布式数据库中间件 > >> 5. 社区成段描述： > >> > >> Apache ShardingSphere 是一套开源的分布式数据库中间件解决方案组成的生态圈，它由Sharding-JDBC、 > >> Sharding-Proxy和Sharding-Sidecar（规划中）这3 > >> 款相互独立，却又能够混合部署配合使用的产品组成。它们均提供标准化的数据分片、分布式事务和数据库治理功能，可适用于如Java > >> 同构、异构语言、云原生等各种多样化的应用场景。 > >> > >> ShardingSphere > >> > >> > 定位为关系型数据库中间件，旨在充分合理地在分布式的场景下利用关系型数据库的计算和存储能力，而并非实现一个全新的关系型数据库。它通过关注不变，进而抓住事物本质。关系型数据库当今依然占有巨大市场，是各个公司核心业务的基石，未来也难于撼动，我们目前阶段更加关注在原有基础上的增量，而非颠覆。 > >> > >> > >> 6. 社区邮件列表（用于帮助学生了解社区，一般为开发者邮箱列表）： d...@shardingsphere.org.apache > >> 7. 社区官方公共联系邮箱：d...@shardingsphere.org.apache > >> 8. 社区 “暑期2020” 项目列表页面链接（可选，可在页面准备好后再告知）： > >> https://shardingsphere.apache.org/index_zh.html > >> 9. 技术标签：分布式、数据库、中间件 > >> 10. 专注领域：Java后端、关系型数据库 > >> > >> > >> > >> > >> > >> 项目官网：https://shardingsphere.apache.org/ > >> GitHub：https://github.com/apache/shardingsphere > >> 联系邮箱：zhangli...@apache.org > >> 联系人：张亮 > >> > >> > >> > >> -- > >> > >> > >> > >> Liang Zhang (John) > >> Apache ShardingSphere & Dubbo > >> >
[ANNOUNCE] Apache ShardingSphere UI 4.1.0 available
Hi all, Apache ShardingSphere Team is glad to announce the new release of Apache ShardingSphere UI 4.1.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/shardingsphere/blob/master/shardingsphere-ui/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 -- Zhang Yonglun Apache ShardingSphere
[RESULT][VOTE] Release Apache ShardingSphere UI 4.1.0
We’ve received 3 +1 binding votes and 0 +1 non-binding vote: +1 binding, Liang Zhang +1 binding, Juan Pan +1 binding, Jun Zhao Thank you everyone for taking the time to review the release and help us. I will process to publish the release and send ANNOUNCE. -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere UI 4.1.0
The vote to release Apache ShardingSphere UI 4.1.0 has passed. 3 PMC member +1 binding votes: Liang Zhang Juan Pan Jun Zhao Thank you everyone for taking the time to review the release and help us. -- Zhang Yonglun Apache ShardingSphere zhaojun 于2020年5月9日周六 下午6:12写道： > +1, binding > > > 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. > > Regards, > cherrylzhao > --- > Email：zhao...@apache.org > Jun Zhao(cherrylzhao) Apache ShardingSphere > > > Juan Pan 于2020年5月9日周六 上午10:32写道： > > > +1, binding > > > > > > Here is my check list > > [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. > > > > > > Juan Pan (Trista) > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > E-mail: panj...@apache.org > > > > > > > > > > On 04/27/2020 11:11，Zhang Yonglun wrote： > > Please install ShardingSphere source code ( > > > > > https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/apache-shardingsphere-4.1.0-src.zip > > ) > > before verification. > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > Zhang Yonglun 于2020年4月26日周日 下午6:29写道： > > > > Hello ShardingSphere Community, > > > > This is a call for vote to release Apache ShardingSphere UI version 4.1.0 > > > > Release notes: > > > > > > > https://github.com/apache/shardingsphere/blob/master/shardingsphere-ui/RELEASE-NOTES.md > > > > The release candidates: > > > > > > > https://dist.apache.org/repos/dist/dev/shardingsphere/shardingsphere-ui-4.1.0/ > > > > Git tag for the release: > > > > > > > https://github.com/apache/shardingsphere/releases/tag/shardingsphere-ui-4.1.0 > > > > Release Commit ID: > > > > > > > https://github.com/apache/shardingsphere/commit/dc24fa288dc38f4c439812dd3ae26feba2ce8963 > > > > 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/ > > > > 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. > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > >
[ANNOUNCE] Apache ShardingSphere 4.1.0 available
Hi all, Apache ShardingSphere Team is glad to announce the new release of Apache ShardingSphere 4.1.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/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 -- Zhang Yonglun Apache ShardingSphere
[RESULT][VOTE] Release Apache ShardingSphere 4.1.0
We’ve received 4 +1 binding votes and 2 +1 non-binding vote: +1 binding, Liang Zhang +1 binding, Jun Zhao +1 binding, Yi Yang +1 binding, Juan Pan +1 non-binding, Jinwei Qin +1 non-binding, Haoran Meng Thank you everyone for taking the time to review the release and help us. I will process to publish the release and send ANNOUNCE. -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere 4.1.0 Round 2
The vote to release Apache ShardingSphere 4.1.0 has passed. 4 PMC member +1 binding votes: Liang Zhang Jun Zhao Yi Yang Juan Pan 2 community +1 non-binding vote: Jinwei Qin Haoran Meng Thank you everyone for taking the time to review the release and help us. -- Zhang Yonglun Apache ShardingSphere Zhang Yonglun 于2020年4月27日周一 下午3:53写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere version 4.1.0 > round 2. > > Release notes: > https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1049/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere/releases/tag/4.1.0 > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/7725abc520421f78f7586a8dc07e451978f64c9c > > 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: > zhangyonglun > > 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. > > -- > > Zhang Yonglun > Apache ShardingSphere >
[VOTE] Release Apache ShardingSphere 4.1.0 Round 2
Hello ShardingSphere Community, This is a call for vote to release Apache ShardingSphere version 4.1.0 round 2. Release notes: https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1049/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/shardingsphere/releases/tag/4.1.0 Release Commit ID: https://github.com/apache/shardingsphere/commit/7725abc520421f78f7586a8dc07e451978f64c9c 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: zhangyonglun 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. -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere 4.1.0
The issue has been resolved. This thread should be terminated. I'll create the round 2 vote later. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年4月23日周四 上午10:36写道： > -1, sorry to say that, but just like Jun said, we need to remove docs and > example from the source code. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhaojun 于2020年4月23日周四 上午10:05写道： > > > Hi, Yonglun > > > > i found the src.zip is too big (36M), examples and docs should be > removed. > > when i startup the sharding-proxy, the log is as blew: > > > > --- > > > > Starting the Sharding-Proxy ... > > The classpath is > > > .:..:/Users/zhaojun/export/ss-release/4.1.0/apache-shardingsphere-4.1.0-sharding-proxy-bin/lib/*:/Users/zhaojun/export/ss-release/4.1.0/apache-shardingsphere-4.1.0-sharding-proxy-bin/lib/*:/Users/zhaojun/export/ss-release/4.1.0/apache-shardingsphere-4.1.0-sharding-proxy-bin/ext-lib/* > > Please check the STDOUT file: > > > /Users/zhaojun/export/ss-release/4.1.0/apache-shardingsphere-4.1.0-sharding-proxy-bin/logs/stdout.log > > > > > > i think we should revise the context, ext-lib and .. have not supported > by > > previous versions, and lib path have duplicated print out. > > > > -- > > Zhao Jun (cherrylzhao) > > Apache ShardingSphere & ServiceComb > > > > > > > On Apr 22, 2020, at 11:21 PM, Zhang Yonglun > > wrote: > > > > > > Hello ShardingSphere Community, > > > > > > This is a call for vote to release Apache ShardingSphere version 4.1.0 > > > > > > Release notes: > > > https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md > > > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/ > > > > > > Maven 2 staging repository: > > > > > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1048/org/apache/shardingsphere/ > > > > > > Git tag for the release: > > > https://github.com/apache/shardingsphere/tree/4.1.0/ > > > > > > Release Commit ID: > > > > > > https://github.com/apache/shardingsphere/commit/e7d3b80f6aad349e95ce173017b69c25c848eee9 > > > > > > Keys to verify the Release Candidate: > > > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS.txt > > > > > > 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 > > > > > > PMC vote is +1 binding, all others is +1 non-binding. > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > > > > [ ] Checksums and PGP signatures are valid. > > > > > > [ ] DISCLAIMER is included. > > > > > > [ ] 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. > > > > > > -- > > > > > > Zhang Yonglun > > > Apache ShardingSphere > > > > > > >
Re: [VOTE] Release Apache ShardingSphere UI 4.1.0
Please install ShardingSphere source code ( https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/apache-shardingsphere-4.1.0-src.zip) before verification. -- Zhang Yonglun Apache ShardingSphere Zhang Yonglun 于2020年4月26日周日 下午6:29写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere UI version 4.1.0 > > Release notes: > > https://github.com/apache/shardingsphere/blob/master/shardingsphere-ui/RELEASE-NOTES.md > > The release candidates: > > https://dist.apache.org/repos/dist/dev/shardingsphere/shardingsphere-ui-4.1.0/ > > Git tag for the release: > > https://github.com/apache/shardingsphere/releases/tag/shardingsphere-ui-4.1.0 > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/dc24fa288dc38f4c439812dd3ae26feba2ce8963 > > 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/ > > 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. > > -- > > Zhang Yonglun > Apache ShardingSphere >
[VOTE] Release Apache ShardingSphere UI 4.1.0
Hello ShardingSphere Community, This is a call for vote to release Apache ShardingSphere UI version 4.1.0 Release notes: https://github.com/apache/shardingsphere/blob/master/shardingsphere-ui/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/shardingsphere/shardingsphere-ui-4.1.0/ Git tag for the release: https://github.com/apache/shardingsphere/releases/tag/shardingsphere-ui-4.1.0 Release Commit ID: https://github.com/apache/shardingsphere/commit/dc24fa288dc38f4c439812dd3ae26feba2ce8963 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/ 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. -- Zhang Yonglun Apache ShardingSphere
[VOTE] Release Apache ShardingSphere 4.1.0
Hello ShardingSphere Community, This is a call for vote to release Apache ShardingSphere version 4.1.0 Release notes: https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/shardingsphere/4.1.0/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1048/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/shardingsphere/tree/4.1.0/ Release Commit ID: https://github.com/apache/shardingsphere/commit/e7d3b80f6aad349e95ce173017b69c25c848eee9 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS.txt 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 PMC vote is +1 binding, all others is +1 non-binding. Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] 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. -- Zhang Yonglun Apache ShardingSphere
Re: Re: [DISCUSS] 4.1.0 release plan
Thanks for your comments. I'll update the RELEASE-NOTES.md -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年4月22日周三 下午6:25写道： > The LeafKeyGenerator has already removed > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Zhang Yonglun 于2020年4月22日周三 下午5:49写道： > > > After append new items, the release notes 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 > > - The docker of Sharding-Proxy supports loading external lib packages > > - Support integration with Spring using @ShardingTransactionType > > - Enhance ShardingDataSource to compatiable with Seata in micro-sevice > > distribution transaction > > > > 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 > > - Fix a long-time problem of adding schema dynamically in Sharding-UI > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > KimmKing 于2020年4月3日周五 上午9:16写道： > > > > > Hello, jun, > > > PR#5050 fix a long-time bug for adding schema dynamically in > sharing-ui. > > > It's nessesary to include tag 4.1.0 and added to release-note. > > > > > > At 2020-04-02 13:02:28, "赵俊" wrote: > > > >Hi, community > > > > > > > >In master branch, since PR#4945 have changed the KeyGenerator API. > > > >So we plan to create 4.1.0-release branch based on 43d3426 commit, > > > >PRs after 43d3426 we will change it to 5.0.0 milestone. > > > > > > > >If you have any question please feel free to let me know. > > > > > > > >-- > > > >Zhao Jun (cherrylzhao) > > > >Apache ShardingSphere & ServiceComb > > > > > > > > > > > >> On Mar 17, 2020, at 1:15 PM, sushixiang wrote: > > > >> > > > >> Sounds great. > > > >> > > > >> > > > >> And I want to know 'Upgrade to Java 8' has already be finished yet? > If > > > not, I want to join. > > > >> > > > >> > > > >> > > > >> > > > >> --Original-- > > > >> From:"Zhang Yonglun" > > >> Date:Tue, Mar 17, 2020 12:30 PM > > > >> To:"dev" > > >> > > > >> Subject:[DISCUSS] 4.1.0 release plan > > > >> > > > >> > > > >> > > > >> 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: Re: [DISCUSS] 4.1.0 release plan
After append new items, the release notes 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 - The docker of Sharding-Proxy supports loading external lib packages - Support integration with Spring using @ShardingTransactionType - Enhance ShardingDataSource to compatiable with Seata in micro-sevice distribution transaction 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 - Fix a long-time problem of adding schema dynamically in Sharding-UI -- Zhang Yonglun Apache ShardingSphere KimmKing 于2020年4月3日周五 上午9:16写道： > Hello, jun, > PR#5050 fix a long-time bug for adding schema dynamically in sharing-ui. > It's nessesary to include tag 4.1.0 and added to release-note. > > At 2020-04-02 13:02:28, "赵俊" wrote: > >Hi, community > > > >In master branch, since PR#4945 have changed the KeyGenerator API. > >So we plan to create 4.1.0-release branch based on 43d3426 commit, > >PRs after 43d3426 we will change it to 5.0.0 milestone. > > > >If you have any question please feel free to let me know. > > > >-- > >Zhao Jun (cherrylzhao) > >Apache ShardingSphere & ServiceComb > > > > > >> On Mar 17, 2020, at 1:15 PM, sushixiang wrote: > >> > >> Sounds great. > >> > >> > >> And I want to know 'Upgrade to Java 8' has already be finished yet? If > not, I want to join. > >> > >> > >> > >> > >> --Original-- > >> From:"Zhang Yonglun" >> Date:Tue, Mar 17, 2020 12:30 PM > >> To:"dev" >> > >> Subject:[DISCUSS] 4.1.0 release plan > >> > >> > >> > >> 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] 4.1.0 release plan
Hi Juan, I think we should include this fix in release notes. Thanks. -- Zhang Yonglun Apache ShardingSphere 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] 4.1.0 release plan
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] 4.1.0 release plan
-- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年3月17日周二 下午5:43写道： > The tasks we need to discuss: > > > - Support scaling for shardingsphere > > This is alpha version, we need to discuss do binary release or just for > source release. > > The binary release is ready. It's time to release both releases. > > - Optimization for Sharing Parser with ANTLR Visitor for MySQL > > It is for all databases dialect, not for MySQL only. > Get it. > > > - Parsing SubQuery > > Not finished yet, we need to talk about excluding this feature. > Yes, you are right. > > > - Upgrade to Java 8 > > OK. > > > - Redesign class domain of parser module > > - Create database protocol module > > - Create new module for shardingsphere-sql-parse-binder > > We are not publishing them as independent modules, maybe user do not care > about these features. > OK. I'll exclude them. > > > - Refactor orchestration center interface > > - Improve integrate SQL parser test engine > > OK. > > > - Decouple UI and ShardingSphere > > Not finish yet, it is better to finish this feature before release. > Yes, Haoran is now working for this. I'll start to release after he finish. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Zhang Yonglun 于2020年3月17日周二 下午2:05写道： > > > That was already finished. Thanks. > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > sushixiang 于2020年3月17日周二 下午1:15写道： > > > > > Sounds great. > > > > > > > > > And I want to know 'Upgrade to Java 8' has already be finished yet? If > > > not, I want to join. > > > > > > > > > > > > > > > --Original-- > > > From:"Zhang Yonglun" > > Date:Tue, Mar 17, 2020 12:30 PM > > > To:"dev" > > > > > Subject:[DISCUSS] 4.1.0 release plan > > > > > > > > > > > > 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] 4.1.0 release plan
Thanks Liang. I'll sync up the comments to the release notes. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年3月17日周二 下午5:43写道： > The tasks we need to discuss: > > > - Support scaling for shardingsphere > > This is alpha version, we need to discuss do binary release or just for > source release. > > > - Optimization for Sharing Parser with ANTLR Visitor for MySQL > > It is for all databases dialect, not for MySQL only. > > > - Parsing SubQuery > > Not finished yet, we need to talk about excluding this feature. > > > - Upgrade to Java 8 > > OK. > > > - Redesign class domain of parser module > > - Create database protocol module > > - Create new module for shardingsphere-sql-parse-binder > > We are not publishing them as independent modules, maybe user do not care > about these features. > > > - Refactor orchestration center interface > > - Improve integrate SQL parser test engine > > OK. > > > - Decouple UI and ShardingSphere > > Not finish yet, it is better to finish this feature before release. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Zhang Yonglun 于2020年3月17日周二 下午2:05写道： > > > That was already finished. Thanks. > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > sushixiang 于2020年3月17日周二 下午1:15写道： > > > > > Sounds great. > > > > > > > > > And I want to know 'Upgrade to Java 8' has already be finished yet? If > > > not, I want to join. > > > > > > > > > > > > > > > --Original-- > > > From:"Zhang Yonglun" > > Date:Tue, Mar 17, 2020 12:30 PM > > > To:"dev" > > > > > Subject:[DISCUSS] 4.1.0 release plan > > > > > > > > > > > > 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] 4.1.0 release plan
That was already finished. Thanks. -- Zhang Yonglun Apache ShardingSphere sushixiang 于2020年3月17日周二 下午1:15写道： > Sounds great. > > > And I want to know 'Upgrade to Java 8' has already be finished yet? If > not, I want to join. > > > > > --Original------ > From:"Zhang Yonglun" Date:Tue, Mar 17, 2020 12:30 PM > To:"dev" > Subject:[DISCUSS] 4.1.0 release plan > > > > 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
[DISCUSS] 4.1.0 release plan
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: Is ShardingSphere(version 4.0.0/4.0.1) adapt to skywalking agent？
Hi Sanmu, Just as Sheng said, I'll provide the new plugin when I am available. I'll reply you the plan when I'm ready. -- Zhang Yonglun Apache ShardingSphere 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: [VOTE] Graduate Apache ShardingSphere (incubating)
+1 -- Zhang Yonglun Apache ShardingSphere 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)
Hi Liang, Yes, you are right, fixed. I have also double checked all files to make sure there are no more problems now. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年2月27日周四 上午12:01写道： > Hi, Yonglun > > I still find apache website url in OpenSharding repo[1], we should remove > them too. > > [1] > https://github.com/OpenSharding/opensharding-spi-impl/blob/master/pom.xml > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Zhang Yonglun 于2020年2月26日周三 下午11:18写道： > > > Hi Justin, > > > > Are you changing code to the package "io.opensharding" inside the project > > > or outside of it? I'm unclear what you are changing here. > > > > > > We changed the package name inside the project via the commit > > > > > https://github.com/OpenSharding/opensharding-spi-impl/commit/b2db2c2ef131551ca7ee898794a13a835260182c > > > > and > > > > > https://github.com/OpenSharding/opensharding-spi-impl-example/commit/e906fa292364a2229bf18930462363c0a8d30bb5 > > . > > > > -- > > > > Zhang Yonglun > > Apache ShardingSphere > > > > > > Justin Mclean 于2020年2月26日周三 下午4:39写道： > > > > > Hi, > > > > > > > The 3 projects are ALv2, but some dependencies include LGPL (for > > example: > > > > hibernate[1]), and some similar codes (about SQL revert) are patent > > > > declared by other company, we cannot make decision merge or not for > > now. > > > > > > It might be best if they make that clear and that they contain things > > that > > > are not compatible with the apache license. > > > > > > > > > > > And I still don't see why you would change package name to > > > > "io.opensharding" that does imply a relationship between these two > > > projects. > > > > > > Are you changing code to the package "io.opensharding" inside the > project > > > or outside of it? I'm unclear what you are changing here. > > > > > > Thanks, > > > Justin > > > > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
Hi Justin, Are you changing code to the package "io.opensharding" inside the project > or outside of it? I'm unclear what you are changing here. We changed the package name inside the project via the commit https://github.com/OpenSharding/opensharding-spi-impl/commit/b2db2c2ef131551ca7ee898794a13a835260182c and https://github.com/OpenSharding/opensharding-spi-impl-example/commit/e906fa292364a2229bf18930462363c0a8d30bb5 . -- Zhang Yonglun Apache ShardingSphere Justin Mclean 于2020年2月26日周三 下午4:39写道： > Hi, > > > The 3 projects are ALv2, but some dependencies include LGPL (for example: > > hibernate[1]), and some similar codes (about SQL revert) are patent > > declared by other company, we cannot make decision merge or not for now. > > It might be best if they make that clear and that they contain things that > are not compatible with the apache license. > > > > > And I still don't see why you would change package name to > > "io.opensharding" that does imply a relationship between these two > projects. > > Are you changing code to the package "io.opensharding" inside the project > or outside of it? I'm unclear what you are changing here. > > Thanks, > Justin >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
> > - 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 >> >> >> >> >> >> 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
Re: shardingsphere pipeline holding build executors on builds.a.o
Thanks for your reminder, I will check this problem. -- Zhang Yonglun Apache ShardingSphere Sean Busbey 于2020年2月15日周六 上午9:24写道： > Hi folks > > something is up with the builds for shardingsphere PRs. Could y'all take a > look? you appear to be starving out the build queue. > > If you look at "Executor Status" on the side here: > > https://builds.apache.org/computer/ > > you'll see a bunch of shardingsphere builds. However, they're mostly jobs > that are marked elsewhere as complete. > > e.g. this build from yesterday is marked as failed in ~30 seconds: > > > https://builds.apache.org/view/S-Z/view/ServiceMix/job/shardingsphere-ci/1709/ > > but if you look at the pipeline stages it's still been running for the > last day and a half. afaict it's still running: > > > https://builds.apache.org/view/S-Z/view/ServiceMix/job/shardingsphere-ci/1709/flowGraphTable/ > > If you look at build host H34 it is indeed still holding an executor slot: > > https://builds.apache.org/computer/H34/ > > >
Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)
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 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
Re: [IMPORTANT][PPMC] Invitation to be ShardingSphere PMC member
YES -- Zhang Yonglun Apache ShardingSphere 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: [DISCUSS] merge docs and example repos into trunk repo
incubator-shardingsphere-doc has been merged into incubator-shardingsphere/docs via https://github.com/apache/incubator-shardingsphere/pull/4226 -- Zhang Yonglun Apache ShardingSphere guangyuan wang 于2020年1月20日周一 下午4:58写道： > I think it's a good idea. As I am a contributor whose first contribution in > the sharding sphere is the modification in docs. > This will encourage the contributor to participate in the sharding sphere, > especially for those new players. > > Zhiyi Yan 于2020年1月17日周五 下午3:49写道： > > > +1. Good idea! > > It makes easier to find examples. > > > > - > > Zhiyi Yan (Zhyee) > > Apache ShardingSphere > > > > > > zhangli...@apache.org 于2020年1月17日周五 下午12:16写道： > > > > > Hi ShardingSphere community, > > > > > > I'd like to discuss about merge docs[1] and examples[2] repos into the > > > trunk repo[3]. > > > > > > The benefit is encourage potential contributors begin from docs and > > > examples. Docs and examples are same important with source codes, it > is a > > > good way to decrease the bar to participant the community. > > > > > > After merging, the structure of project may be: > > > > > > ``` > > > -- src > > > -- docs > > > -- examples > > > ``` > > > > > > Any suggestions? > > > > > > > > > [1] https://github.com/apache/incubator-shardingsphere-doc > > > [2] https://github.com/apache/incubator-shardingsphere-example > > > [3] https://github.com/apache/incubator-shardingsphere > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: [DISCUSS] 4.0.1 stable version release plan
I have merged all my 5.0.0 PRs to 4.0.1. I suggest all committers check theirs to avoid miss. 5.0.0 #3861, PostgreSQL Proxy read parameters error in all types except String #3968, Ambiguous description of COM_STMT_EXECUTE in MySQL protocol #4042, Use the two-stage parsing strategy recall travis #4182, ignore showLike context in show columns 4.0.1 #3861, carry pr#3863 from dev to 4.0.1 #3968, carry pr#3969 from dev to 4.0.1 #4042, carry pr#4045 to 4.0.1 (kimmking) add travis config #4203 #4182, ignore showLike context in show columns -- Zhang Yonglun Apache ShardingSphere 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)
+1. The statistics reflects the activity of PPMC. -- Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2020年2月6日周四 上午11:28写道： > I can statistics some data for all PPMCs and committers, which can > include count of mails, issues, pull requests, code addition and deletion > after we goto incubator, and can statistics last contribution time, does > the statistics enough? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhangli...@apache.org 于2020年2月6日周四 上午1:59写道： > > > 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. > > - 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. > > > > 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? > > > > -- > > > > 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) >
Re: Re: use sharding-proxy, query is slow
Can you tell me how many hosts or how may MySQL instance there are first?
I think the performance is not about the server.yaml configuration.
--
Zhang Yonglun
Apache ShardingSphere
Daniel Yu 于2020年1月20日周一 下午12:39写道：
> ok， we will checkout the env load，it may be some performance problem
>
> another question，we have no experience on the server.yaml and
> Performance Tuning about this config,
> can you give some advice as you see in our server.yaml?
>
>
>
> yukai...@outlook.com
>
> From: Zhang Yonglun<mailto:zhangyong...@apache.org>
> Date: 2020-01-20 12:24
> To: dev<mailto:dev@shardingsphere.apache.org>
> Subject: Re: Re: use sharding-proxy, query is slow
> The hostname xxx you omitted is what I want to see. Just tell me how many
> hosts or how may MySQL instance there are.
> Show me the 'load' on any host of MySQL instance when query. If a query
> with key costs 8s, the load will be very high.
>
> --
>
> Zhang Yonglun
> Apache ShardingSphere
>
>
> Daniel Yu 于2020年1月20日周一 下午12:14写道：
>
> > Hi:
> >thx for you reply.
> >
> > 1. What's the cost when mysql client query database1 directly without
> > sharding-proxy? (use member_id as where condition)
> > it cost 8 seconds
> > the cost means the SQL query time spent, i use the command like " mysql
> > -u -p xxx" on mysql server, and i run the sql ,it print the cost
> result.
> >
> > 2. Is 'member_id' the primary key?
> > yes , the member_id is primary key , before sharding it is primary key,
> > after sharding to 16 databases, it is still primary key .
> >
> > 3. Please show me the config-sharding.yaml and server.yaml.
> > I omitted some cotent
> >
> > the config-sharding.yaml :
> > dataSources:
> > db0:
> > url: jdbc:mysql://xxx:3306/db0?useSSL=false
> > username: xxx
> > password: xxx
> > connectionTimeoutMilliseconds: 3
> > idleTimeoutMilliseconds: 6
> > maxLifetimeMilliseconds: 180
> > maxPoolSize: 65
> > ...
> > db15:
> > url: jdbc:mysql://xxx:3306/db1?useSSL=false
> > username: root
> > password: root
> > connectionTimeoutMilliseconds: 3
> > idleTimeoutMilliseconds: 6
> > maxLifetimeMilliseconds: 180
> > maxPoolSize: 65
> >
> > shardingRule:
> > tables:
> > member:
> > actualDataNodes: db${0..15}.member
> > databaseStrategy:
> > complex:
> > shardingColumns: member_id
> > algorithmClassName:
> > com.toonyoo.shardingjdbc.algorithm.ComplexAlorithm
> >
> > the server.yaml:
> > authentication:
> > users:
> > root:
> > password: xxx
> > props:
> > max.connections.size.per.query: 32
> > acceptor.size: 32
> > executor.size: 32
> > proxy.frontend.flush.threshold: 256
> > sql.show: false
> >
> > yukai...@outlook.com
> >
> > From: Zhang Yonglun<mailto:zhangyong...@apache.org>
> > Date: 2020-01-20 11:51
> > To: dev<mailto:dev@shardingsphere.apache.org>
> > Subject: Re: use sharding-proxy, query is slow
> > 1. What's the cost when mysql client query database1 directly without
> > sharding-proxy? (use member_id as where condition)
> > 2. Is 'member_id' the primary key?
> > 3. Please show me the config-sharding.yaml and server.yaml.
> >
> > --
> >
> > Zhang Yonglun
> > Apache ShardingSphere
> >
> >
> > Daniel Yu 于2020年1月20日周一 上午11:17写道：
> >
> > > Hi :
> > > we have a table 'member' with 160,000,000 rows ,
> > >
> > > sharding key is member_id
> > > after sharding the database to 16 databases, the 'member' 's table
> > > struct is same in 16 databases,
> > > one database the 'member' table have 10,000,000 rows
> > >
> > > we query data by SQL "select * from member where member_id =
> > 'abc'
> > > " on database 1 ,it cost 8s,
> > >
> > >
> > >when i used proxy query on 16 databases by the same sql , it cost
> > > 60s , as far as I know the proxy used threadpool to Parallel execution
> > the
> > > query , but the query is slow , why?
> > >
> > >
> > >
> >
>
Re: Re: use sharding-proxy, query is slow
The hostname xxx you omitted is what I want to see. Just tell me how many
hosts or how may MySQL instance there are.
Show me the 'load' on any host of MySQL instance when query. If a query
with key costs 8s, the load will be very high.
--
Zhang Yonglun
Apache ShardingSphere
Daniel Yu 于2020年1月20日周一 下午12:14写道：
> Hi:
>thx for you reply.
>
> 1. What's the cost when mysql client query database1 directly without
> sharding-proxy? (use member_id as where condition)
> it cost 8 seconds
> the cost means the SQL query time spent, i use the command like " mysql
> -u -p xxx" on mysql server, and i run the sql ,it print the cost result.
>
> 2. Is 'member_id' the primary key?
> yes , the member_id is primary key , before sharding it is primary key,
> after sharding to 16 databases, it is still primary key .
>
> 3. Please show me the config-sharding.yaml and server.yaml.
> I omitted some cotent
>
> the config-sharding.yaml :
> dataSources:
> db0:
> url: jdbc:mysql://xxx:3306/db0?useSSL=false
> username: xxx
> password: xxx
> connectionTimeoutMilliseconds: 3
> idleTimeoutMilliseconds: 6
> maxLifetimeMilliseconds: 180
> maxPoolSize: 65
> ...
> db15:
> url: jdbc:mysql://xxx:3306/db1?useSSL=false
> username: root
> password: root
> connectionTimeoutMilliseconds: 3
> idleTimeoutMilliseconds: 6
> maxLifetimeMilliseconds: 180
> maxPoolSize: 65
>
> shardingRule:
> tables:
> member:
> actualDataNodes: db${0..15}.member
> databaseStrategy:
> complex:
> shardingColumns: member_id
> algorithmClassName:
> com.toonyoo.shardingjdbc.algorithm.ComplexAlorithm
>
> the server.yaml:
> authentication:
> users:
> root:
> password: xxx
> props:
> max.connections.size.per.query: 32
> acceptor.size: 32
> executor.size: 32
> proxy.frontend.flush.threshold: 256
> sql.show: false
>
> yukai...@outlook.com
>
> From: Zhang Yonglun<mailto:zhangyong...@apache.org>
> Date: 2020-01-20 11:51
> To: dev<mailto:dev@shardingsphere.apache.org>
> Subject: Re: use sharding-proxy, query is slow
> 1. What's the cost when mysql client query database1 directly without
> sharding-proxy? (use member_id as where condition)
> 2. Is 'member_id' the primary key?
> 3. Please show me the config-sharding.yaml and server.yaml.
>
> --
>
> Zhang Yonglun
> Apache ShardingSphere
>
>
> Daniel Yu 于2020年1月20日周一 上午11:17写道：
>
> > Hi :
> > we have a table 'member' with 160,000,000 rows ,
> >
> > sharding key is member_id
> > after sharding the database to 16 databases, the 'member' 's table
> > struct is same in 16 databases,
> > one database the 'member' table have 10,000,000 rows
> >
> > we query data by SQL "select * from member where member_id =
> 'abc'
> > " on database 1 ,it cost 8s,
> >
> >
> >when i used proxy query on 16 databases by the same sql , it cost
> > 60s , as far as I know the proxy used threadpool to Parallel execution
> the
> > query , but the query is slow , why?
> >
> >
> >
>
Re: use sharding-proxy, query is slow
1. What's the cost when mysql client query database1 directly without sharding-proxy? (use member_id as where condition) 2. Is 'member_id' the primary key? 3. Please show me the config-sharding.yaml and server.yaml. -- Zhang Yonglun Apache ShardingSphere Daniel Yu 于2020年1月20日周一 上午11:17写道： > Hi : > we have a table 'member' with 160,000,000 rows , > > sharding key is member_id > after sharding the database to 16 databases, the 'member' 's table > struct is same in 16 databases, > one database the 'member' table have 10,000,000 rows > > we query data by SQL "select * from member where member_id = 'abc' > " on database 1 ,it cost 8s, > > >when i used proxy query on 16 databases by the same sql , it cost > 60s , as far as I know the proxy used threadpool to Parallel execution the > query , but the query is slow , why? > > >
[DISCUSS] Change the default branch to 'master' in GitHub
Hi all, I am planning to change the default branch from 'dev' to 'master'. The 'dev' branch may be deleted after a period of time. To finish this job, we need the help of Apache Jira: 1. branch name, **master**. Request for open the branch protection. The branch should not allow push directly. 2. branch name , **dev**. Request for **close** the branch protection. 3. Change default branch to **master** Please help to review theses operations. -- Zhang Yonglun Apache ShardingSphere
Re: The 2019 Summary of ShardingSphere community
Impressive progress. Thanks for the statistics. -- Zhang Yonglun Apache ShardingSphere 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: [DISCUSS] merge docs and example repos into trunk repo
+1 -- Zhang Yonglun Apache ShardingSphere zhaojun 于2020年1月17日周五 下午1:09写道： > +1 > > -- > Zhao Jun (cherrylzhao) > Apache ShardingSphere & ServiceComb > > > On Jan 17, 2020, at 12:18 PM, Raigor Jiang wrote: > > > > It will be nice! agree +1 > > > > > > > > > > On 01/17/2020 12:15，zhangli...@apache.org wrote： > > Hi ShardingSphere community, > > > > I'd like to discuss about merge docs[1] and examples[2] repos into the > > trunk repo[3]. > > > > The benefit is encourage potential contributors begin from docs and > > examples. Docs and examples are same important with source codes, it is a > > good way to decrease the bar to participant the community. > > > > After merging, the structure of project may be: > > > > ``` > > -- src > > -- docs > > -- examples > > ``` > > > > Any suggestions? > > > > > > [1] https://github.com/apache/incubator-shardingsphere-doc > > [2] https://github.com/apache/incubator-shardingsphere-example > > [3] https://github.com/apache/incubator-shardingsphere > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > >
Re: [ANNOUNCE] Apache ShardingSphere 4.0.0 available
Hi Sheng, I will create a new issue and provide plugin for ShardingSphere 4.0.0 later. -- Zhang Yonglun Apache ShardingSphere Sheng Wu 于2020年1月13日周一 下午11:15写道： > 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: [ANNOUNCE] New committer: Xiaofeng Jiang
Congratulations! -- Zhang Yonglun Apache ShardingSphere avalon566 于2020年1月8日周三 下午10:05写道： > Congratulations! > > > > YangWen Ou(avalon566) > Apache ShardingSphere > On 1/8/2020 14:02，Juan Pan wrote： > Hi everyone, > > TheProjectManagementCommittee(PMC)forApache ShardingSphere hasinvited > Xiaofeng Jiang tobecomeacommitterandwearepleasedtoannouncethathehasaccepted. > > Xiaofeng is being active in ShardingSphere community, and we are glad to > see his more interactions with community in the future. > > > Welcome Xiaofeng, and please enjoy your journey.:) > > > Best wishes, > Trista > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > >
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2
+1 Checked: Download links are valid. PGP checked. DISCLAIMER is included. LICENSE and NOTICE files are correct for each ShardingSphere repo. All files have license headers if necessary. mvn install succeed. -- Zhang Yonglun Apache ShardingSphere Juan Pan 于2020年1月2日周四 下午6:44写道： > +1, it is ok for me > > > My check list, > > Download links are valid. > Checksums and PGP signatures are valid. > DISCLAIMER is included. > LICENSE and NOTICE files are correct for each ShardingSphere repo. > All files have license headers if necessary. > Install source files successfully. > > > Juan Pan (Trista) > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > E-mail: panj...@apache.org > > > > > On 01/2/2020 12:37，zhangli...@apache.org wrote： > 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 > > > 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写道： &g
Re: opentracing dependency upgrade to 0.31.0
I agree with you. -- Zhang Yonglun Apache ShardingSphere Sheng Wu 于2019年12月25日周三 下午3:32写道： > 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: opentracing dependency upgrade to 0.31.0
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: 4.0.0 stable version release plan
ringboot and mybatis framework.
>
>
> sharding-proxy version: dev
> mysql-version: 5.7
> java-version:jdk8
> OS: window10
>
>
> I've set up this issue#3725(
> https://github.com/apache/incubator-shardingsphere/issues/3725)
> configuration：
> config-sharding.yaml
> schemaName: sharding_db
>
> dataSources:
> ds_0:
> url: jdbc:mysql://127.0.0.1:3306/demo_ds_0?serverTimezone=UTC=false
> username: root
> password:
> connectionTimeoutMilliseconds: 3
> idleTimeoutMilliseconds: 6
> maxLifetimeMilliseconds: 180
> maxPoolSize: 50
> ds_1:
> url: jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC=false
> username: root
> password:
> connectionTimeoutMilliseconds: 3
> idleTimeoutMilliseconds: 6
> maxLifetimeMilliseconds: 180
> maxPoolSize: 50
>
> shardingRule:
> tables:
> t_order:
> actualDataNodes: ds_${0..1}.t_order_${0..1}
> tableStrategy:
> inline:
> shardingColumn: order_id
> algorithmExpression: t_order_${order_id % 2}
> keyGenerator:
> type: SNOWFLAKE
> column: order_id
> t_order_item:
> actualDataNodes: ds_${0..1}.t_order_item_${0..1}
> tableStrategy:
> inline:
> shardingColumn: order_id
> algorithmExpression: t_order_item_${order_id % 2}
> keyGenerator:
> type: SNOWFLAKE
> column: order_item_id
> bindingTables:
> - t_order,t_order_item
> broadcastTables:
> - t_address
> defaultDatabaseStrategy:
> inline:
> shardingColumn: user_id
> algorithmExpression: ds_${user_id % 2}
> defaultTableStrategy:
> none:
> server.yaml
> authentication:
> users:
> root:
> password: root
> sharding:
> password: sharding
> authorizedSchemas: sharding_db
>
> props:
> max.connections.size.per.query: 1
> acceptor.size: 16 # The default value is available processors count * 2.
> executor.size: 16 # Infinite by default.
> proxy.frontend.flush.threshold: 128 # The default value is 128.
> # LOCAL: Proxy will run with LOCAL transaction.
> # XA: Proxy will run with XA transaction.
> # BASE: Proxy will run with B.A.S.E transaction.
> proxy.transaction.type: LOCAL
> proxy.opentracing.enabled: false
> query.with.cipher.column: true
> sql.show: false
>
>
> Running example(
>
> https://github.com/apache/incubator-shardingsphere-example/blob/dev/sharding-proxy-example/sharding-proxy-boot-mybatis-example/src/main/java/org/apache/shardingsphere/example/proxy/spring/boot/mybatis/SpringBootStarterExample.java
> )
>
>
>
>
>
>
>
>
>
>
> On 12/9/2019 11:45，Zhang Yonglun wrote：
> Liang,
>
> You are right. I'll create a schedule for performance test.
>
>
> Zhang Yonglun
> Apache ShardingSphere
>
>
> zhangli...@apache.org 于2019年12月9日周一 上午11:34写道：
>
> Acceptance test framework will be established soon.
> The proposal is to assert the project is OK basically. we don't expect it
> can assert all function details.
> We prefer using uint tests and integrated test engine to assert all
> function details, it is fine now.
>
> So, IMO, we can establish the acceptance test framework asynchronically.
> We just waiting the first result of performance test to decide whether we
> can release now.
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> zhaojun 于2019年12月9日周一 上午11:10写道：
>
> It looks good to me, but it’s better we have a mechanism to verify
> whether
> 4.0.0 is stable or not.
>
> --
> Zhao Jun (cherrylzhao)
> Apache Sharding-Sphere & ServiceComb
>
> On Dec 9, 2019, at 10:53 AM, Sheng Wu
> wrote:
>
> 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 r
Re: Schedule for Performance Test display
I agree with you. The performance data is the most important aspect, should be finished before others. Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2019年12月9日周一 下午2:31写道： > These 3 tasks are good enough for finish all performance test issue. I > think they should not as block issues of release. > How about change the block issue as know the actual performance data? > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Zhang Yonglun 于2019年12月9日周一 下午12:47写道： > > > Hi, > > > > Since the performance test display is so important that has impacted the > > 4.0.0 release. All the work below should be finished by the end of this > > week. > > > > 1. Add a scenario for Master-Slave. r/w to the same database compare with > > r/w split. > > 2. Describe the testing scenario in detail, including node(s) SQL routed, > > request concurrency, data volume. > > 3. Document for the performance test. Others can reproduce this test > > following this document. > > > > Any suggestions? > > > > > > > > Zhang Yonglun > > Apache ShardingSphere > > >
Schedule for Performance Test display
Hi, Since the performance test display is so important that has impacted the 4.0.0 release. All the work below should be finished by the end of this week. 1. Add a scenario for Master-Slave. r/w to the same database compare with r/w split. 2. Describe the testing scenario in detail, including node(s) SQL routed, request concurrency, data volume. 3. Document for the performance test. Others can reproduce this test following this document. Any suggestions? Zhang Yonglun Apache ShardingSphere
Re: 4.0.0 stable version release plan
Liang, You are right. I'll create a schedule for performance test. Zhang Yonglun Apache ShardingSphere zhangli...@apache.org 于2019年12月9日周一 上午11:34写道： > Acceptance test framework will be established soon. > The proposal is to assert the project is OK basically. we don't expect it > can assert all function details. > We prefer using uint tests and integrated test engine to assert all > function details, it is fine now. > > So, IMO, we can establish the acceptance test framework asynchronically. > We just waiting the first result of performance test to decide whether we > can release now. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhaojun 于2019年12月9日周一 上午11:10写道： > > > It looks good to me, but it’s better we have a mechanism to verify > whether > > 4.0.0 is stable or not. > > > > -- > > Zhao Jun (cherrylzhao) > > Apache Sharding-Sphere & ServiceComb > > > > > On Dec 9, 2019, at 10:53 AM, Sheng Wu > wrote: > > > > > > 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, > > >>>>>>> > > >>>>&g
Re: What is the update of ShardingSphere new version plugin?
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. 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?
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?
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?
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: Sharding-Proxy for mgr/pxc
Not yet. Can I ask what's your MGR solution for now? Middleware or VIP? I have a Sharding-JDBC implementation prototype in my private repo: https://github.com/tuohai666/incubator-shardingsphere/tree/mgr We haven't decided when to merge. Zhang Yonglun Apache ShardingSphere Zero Dai 于2019年11月23日周六 下午1:14写道： > Does Sharding-Proxy support the mgr or pxc cluster? >
Re: (Resend)issues for Proxy with Postgres
Hi, For 1: If you can reproduce this problem, can you reply with the table structure? And I will reopen that issue. For 2: Can you provide more information? Like config and SQLs. For 3: Is data updated successfully? Please provide more information like config and SQLs. If you like, please open new issues on GitHub for 2 and 3. Zhang Yonglun Apache ShardingSphere Jiang Raigor 于2019年11月19日周二 上午10:51写道： > Hi, everyone, > > I found some issues with Sharding-Proxy when using postgres and collected > as follows: > > First, I prepared an environment like: > > https://github.com/apache/incubator-shardingsphere/issues/3419, > > my postgres version is 12.0, and use the latest Proxy source code. > (commit 962a9656 zhaojun on 2019-11-17 at 17:18) > > > The issues are: > > 1) Cannot find JDBC type '2003' in PostgreSQL column type (Existing) > > https://github.com/apache/incubator-shardingsphere/issues/3104 > > > 2) receiveErrorResponse for postgres client (new) > > When use JDBC client to insert record with Proxy, whether use Statement or > PreparedStatement, the Proxy can insert successful, > but the JDBC client receives error response. > > Error log of Statement: > org.postgresql.util.PSQLException: > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455) > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155) > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288) > at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430) > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356) > at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303) > at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289) > at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266) > at org.postgresql.jdbc.PgStatement.executeUpdate(PgStatement.java:246) > > > Error log of PreparedStatement: > org.postgresql.util.PSQLException: > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455) > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155) > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288) > at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430) > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356) > at > org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:168) > at > org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:135) > > 3) when update a record, response of num is 0 (new) > > When use JDBC client to update record with Proxy, it will success, but the > result num is 0; > Otherwise, if excute update SQL without Proxy, the result num is 1; > > I don't know if these issues need to be dealt with together? > > 获取 Outlook for Android<https://aka.ms/ghei36> >
Re: Sharding value must implements Comparable.
Hello, for English only, please translate, thank you. Zhang Yonglun Apache ShardingSphere 高伟 于2019年11月19日周二 下午1:11写道： > 您好，我项目中配置的分片策略是inline的策略，最近服务器报"Sharding value must implements > Comparable."这个错，但是本地怎么都复现不了，所以想求助社区 提供一些排查思路。感谢
Re: Sharding-Proxy for mgr/pxc
Not yet. Can I ask what's your MGR solution for now? Middleware or VIP? Zhang Yonglun Apache ShardingSphere Zero Dai 于2019年11月19日周二 下午1:11写道： > Does Sharding-Proxy support the mgr or pxc cluster? >
Re: [DISCUSS] The acceptance test
Welcome to discuss. Please start a new thread for the new topic. 郑云朋 于2019年11月13日周三 下午8:41写道： > 测试:shardsphere proxy > > > 环境: > mysql数据库5.6 >数据库：h1 h2 > 使用场景： > 两个数据库中表跨库关联查询 > > > -- > > 该邮件从移动设备发送 > > > --原始邮件-- > 发件人："Zhang Yonglun " 发送时间：2019年11月13日(星期三) 晚上8:28 > 收件人："dev" 主题：[DISCUSS] The acceptance test > --- > > Hi all, > > I'd like to setup an acceptance test environment which could cover the > basic scenarios for ShardingSphere. > > It focuses on function test but not performance test. We can test any tags > or branches of the GitHub repository. It's convenient to verify > the influence of a new feature, especially to releasing process. > > I suppose to setup the environment in https://builds.apache.org, and > install MySQL server in this cluster from the Docker Hub. Is it compliant > to just use MySQL? > > I think the test scenarios should include: > > Access: > Sharding-JDBC > Sharding-Proxy > > Mode: > Single routing > Database routing > Table routing > Full routing > MasterSlave > MasterSlave + Single routing > MasterSlave + Database routing > MasterSlave + Table routing > MasterSlave + Full routing > Encryption > Encryption + Single routing > Encryption + Database routing > Encryption + Table routing > Encryption + Full routing > > SQL: > INSERT > UPDATE > SELECT > DELETE > Access(2) * Mode(14) * SQL(4) = 112 secnarios > > > -- > Zhang Yonglun > Apache ShardingSphere -- Zhang Yonglun Apache ShardingSphere
Re: Add email signature
Done. zhangli...@apache.org 于2019年11月14日周四 下午12:06写道： > Hi ShardingSphere's community, > > In order to let everybody know who you are, could you add email signature? > > The format just like: > > ``` > -- > Your name, for example: John > The project you belong to(if you have), for example: Apache ShardingSphere > ``` > > All PPMCs and committers please make sure your email signature. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > -- Zhang Yonglun Apache ShardingSphere
Re: [DISCUSS] The acceptance test
Hi Willem and Sheng, Thanks a lot for your help. It's great you have already created mature testing procedure. I'll refer to your advice before I start to work. Sheng Wu 于2019年11月14日周四 上午9:09写道： > SkyWalking is using multiple types[1] of tests for every commit tests, it > is a kind of acceptance test. > > 1. Integration Tests, like ServiceComb's > 2. e2e tests, after recompiling the whole tar ball, run the real case and > check input/output[2][3] > 3. Component tests. In SkyWalking, they are agent plugin tests. You need to > go through different cases and verify the output. In SS, it means, > verifying the route dest and rewritten SQLs at mock DB sides. > > The whole test process is a long term to build, please set the priority, > these above are just material to give you some ideas. > > [1] > > https://github.com/apache/skywalking/blob/master/docs/en/guides/README.md#for-code-developer > [2] https://github.com/apache/skywalking/tree/master/test/e2e > [3] > > https://builds.apache.org/blue/organizations/jenkins/skywalking-e2e-2/detail/skywalking-e2e-2/1822/pipeline/ > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Willem Jiang 于2019年11月13日周三 下午9:48写道： > > > Please take the accept test[1] in ServiceComb Pack as an example, it's > > quite simple you just need to provide a date access API. > > Here is a Chinese blog[2] you can take a look at. > > > > [1] > > > https://github.com/apache/servicecomb-pack/tree/SCB-1587/acceptance-tests > > [2] > > > https://servicecomb.apache.org/cn/docs/how-to-do-microservice-accept-test/ > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Nov 13, 2019 at 8:28 PM Zhang Yonglun > > wrote: > > > > > > Hi all, > > > > > > I'd like to setup an acceptance test environment which could cover the > > > basic scenarios for ShardingSphere. > > > > > > It focuses on function test but not performance test. We can test any > > tags > > > or branches of the GitHub repository. It's convenient to verify > > > the influence of a new feature, especially to releasing process. > > > > > > I suppose to setup the environment in https://builds.apache.org, and > > > install MySQL server in this cluster from the Docker Hub. Is it > compliant > > > to just use MySQL? > > > > > > I think the test scenarios should include: > > > > > > Access: > > > Sharding-JDBC > > > Sharding-Proxy > > > > > > Mode: > > > Single routing > > > Database routing > > > Table routing > > > Full routing > > > MasterSlave > > > MasterSlave + Single routing > > > MasterSlave + Database routing > > > MasterSlave + Table routing > > > MasterSlave + Full routing > > > Encryption > > > Encryption + Single routing > > > Encryption + Database routing > > > Encryption + Table routing > > > Encryption + Full routing > > > > > > SQL: > > > INSERT > > > UPDATE > > > SELECT > > > DELETE > > > Access(2) * Mode(14) * SQL(4) = 112 secnarios > > > > > > > > > -- > > > Zhang Yonglun > > > Apache ShardingSphere > > > -- Zhang Yonglun Apache ShardingSphere
Re: [ANNOUNCE] New committer: Zhiyi Yan
Congratulations! Sion Yang 于2019年11月13日周三 上午11:29写道： > Congratulation and welcome to join us. > > -- > > Yi Yang(Sion) > Apache ShardingSphere > > > > At 2019-11-13 11:19:39, "Juan Pan" wrote: > >Hi folks, > > > >TheProjectManagementCommittee(PMC)forApache ShardingSphere > >hasinvited Zhiyi Yan tobecomeacommitterandwearepleasedtoannouncethat she > hasaccepted. > > > >Welcome Zhiyi and Look forward to continued interaction. > > > > > >please join me in congratulating Zhiyi. > > > > > >Best wishes, > >Trista > > > > > > Juan Pan > > > > > >panj...@apache.org > >Juan Pan(Trista), Apache ShardingSphere > > > -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Accept ShardingScaling Donation ROUND2
rc/default](https://bitbucket.org/asomov/snakeyaml/src/default) > > - guava 18.0: [ > > https://github.com/google/guava](https://github.com/google/guava) > > - netty-all 4.1.16.Final: [ > > https://github.com/netty/netty](https://github.com/netty/netty) > > - commons-dbcp2 2.7.0: [ > > > https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp) > > - commons-cli 1.4: [ > > > https://github.com/apache/commons-cli](https://github.com/apache/commons-cli) > > - log4j 1.2.17: [ > > https://github.com/apache/log4j](https://github.com/apache/log4j) > > - gson 2.8.6: [ > > https://github.com/google/gson](https://github.com/google/gson) > > > > > > > > > > ### MIT licenses > > > > > > - slf4j-api 1.7.28: [ > > https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) > > - slf4j-log4j12 1.7.28: [ > > https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) > > - lombok 1.18.4: [ > > > https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok) > > - mockito-core 2.7.21(scope test): [ > > https://github.com/mockito/mockito](https://github.com/mockito/mockito) > > - mockito-inline 2.7.21(scope test): [ > > https://github.com/mockito/mockito](https://github.com/mockito/mockito) > > > > > > ### EPL 1.0 licenses > > > > > > - junit 4.12(scope test): [ > > > https://github.com/junit-team/junit4](https://github.com/junit-team/junit4) > > > > > > ### BSD License > > > > > > - hamcrest-library 1.3(scope test): [ > > > https://github.com/hamcrest/JavaHamcrest](https://github.com/hamcrest/JavaHamcrest) > > > > > > ## Required Resources > > > > > > ### Git Repositories: > > > > > > - [ > > > https://github.com/avalon566/sharding-scaling.git](https://github.com/avalon566/sharding-scaling.git) > > > > > > ## Initial Committers > > > > > > - KomachiSion, 杨翊, Yi Yang, yan...@apache.org > > - avalon566, 欧阳文, Wen OuYang > > - dongzl, 董宗磊, ZongLei Dong > > - ssxlulu > > > > > > Yi Yang is already PPMC of ShardingSphere. > > Wen OuYang will become a committer of ShardingSphere if vote be accepted > > after donating. > > ZongLei Dong and ssxlulu will be only contributors. > > > > > > - [1] [ > > > https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling) > > - [2] [ > > > https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) > > > > > > > > > > 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 > > > > > > > > > > -- > > > > Yi Yang(Sion) > > Apache ShardingSphere > -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Accept ShardingScaling Donation
(https://github.com/qos-ch/slf4j) > - slf4j-log4j12 1.7.28: [ > https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) > - lombok 1.18.4: [ > https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok) > - mockito-core 2.7.21(scope test): [ > https://github.com/mockito/mockito](https://github.com/mockito/mockito) > - mockito-inline 2.7.21(scope test): [ > https://github.com/mockito/mockito](https://github.com/mockito/mockito) > > > ### EPL 1.0 licenses > > > - junit 4.12(scope test): [ > https://github.com/junit-team/junit4](https://github.com/junit-team/junit4) > > > ### BSD License > > > - hamcrest-library 1.3(scope test): [ > https://github.com/hamcrest/JavaHamcrest](https://github.com/hamcrest/JavaHamcrest) > > > ## Required Resources > > > ### Git Repositories: > > > - [ > https://github.com/avalon566/sharding-scaling.git](https://github.com/avalon566/sharding-scaling.git) > > > ## Initial Committers > > > - 杨翊, Yi Yang, yan...@apache.org > - 欧阳文, Wen OuYang > - 董宗磊, ZongLei Dong > > > Yi Yang is already PPMC of ShardingSphere. > Wen OuYang and ZongLei Dong will become a committer if vote be accepted > after donating. > > > - [1] [ > https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling) > - [2] [ > https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) > > > 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 > > > > > -- > > Yi Yang(Sion) > Apache ShardingSphere -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
ressed through constructor parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'encryptDataSource' defined in class path resource > [org/apache/shardingsphere/shardingjdbc/spring/boot/SpringBootConfiguration.class]: > Bean instantiation via factory method failed; nested exception is > org.springframework.beans.BeanInstantiationException: Failed to instantiate > [javax.sql.DataSource]: Factory method 'encryptDataSource' threw exception; > nested exception is java.sql.SQLDataException: Cannot determine value type > from string 'NO' > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:622) > ... 119 common frames omitted > > > > --原始邮件-- > 发件人:"Juan Pan" 发送时间:2019年11月11日(星期一) 晚上6:40 > 收件人:"dev@shardingsphere.apache.org" ;"b...@apache.org" ;"vongosl...@apache.org" ningji...@apache.org" > 主题:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND > 4 > > > > Hi everyone, > > > With the help and effort of our community, the previous issues were fixed > already. I am glad to invite everyone to move on to check and vote for our > 4.0.0-RC3 ROUND 4. > > > Release notes: > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ > > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ > > > Git tag for the release: > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ > > > Release Commit ID: > > https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d > > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > > Look at here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > > Please vote accordingly: > > > [ ] +1 approve > > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > Checklist for reference: > > > [ ] Download links are valid. > > > [ ] Checksums and PGP signatures are valid. > > > [ ] DISCLAIMER is included. > > > [ ] Source code artifacts have correct names matching the current release. > > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > > [ ] All files have license headers if necessary. > > > [ ] No compiled archives bundled in source archive. > > > > > Best wishes, > Trista > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere -- Zhang Yonglun Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
-1 For the cross platform issue, I have to give the -1 vote. Let's prepare the next round. Juan Pan 于2019年11月8日周五 下午3:46写道： > Kind suggestion, got it. > > > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/8/2019 15:34，Sheng Wu wrote： > Juan > > Try GitHub action first, it is faster, and doesn't require INFRA to setup. > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Juan Pan 于2019年11月8日周五 下午3:09写道： > > Yep, the feedback from three of folks convinced us that our release can > not install well on window platform. > > > I will handle this new issue ASAP, therefore i am sorry to tell everyone > vote for this release is delayed by a new issue, i.e across platform > exception, and please wait for next ROUND. > > > Thanks, Sheng, appveyor is exactly what we need. :) > > > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/8/2019 14:41，Sheng Wu wrote： > Look like an across platforms test fails. > A suggestions, SkyWalking is using appveyor[1] to do Windows compiling > check today. I think GitHub action also supports windows. > We should choose one. Because SkyWalking used to face the same issue, some > codes/tests are not working in Windows. > > > [1] https://ci.appveyor.com/project/ApacheSoftwareFoundation/skywalking/ > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > 王海涛 于2019年11月8日周五 下午2:36写道： > > Me too. In window 7, when I install the whole project , the same error was > occurred. > "Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.667 s > <<< FAILURE! - in > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest > > > assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest) > Time elapsed: 0.512 s <<< FAILURE!" > > -邮件原件- > 发件人: Zhang Yonglun [mailto:zhangyong...@apache.org] > 发送时间: 2019年11月8日 14:27 > 收件人: dev > 主题: Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3 > > OS: Windows7 > > JDK: 1.8.0_162" > > mvn install or run the single test case MySQLTimeServiceTest can cause > that failure. > > Juan Pan 于2019年11月8日周五 下午1:41写道： > > Hi Yonglun, > > > Thanks for your feedback. Actually, the exception you mentioned didn’t > happened to me, either i run `MySQLTimeServiceTest` separately or > installed the whole project. Can you provide more details about your > runtime environment or test procedure? > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/8/2019 13:25，Zhang Yonglun wrote： > I have installed the source code and a unit test failed: > > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 0.48 s <<< FAILURE! - in > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest > [ERROR] > > assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLT > imeServiceTest) > Time elapsed: 0.329 s <<< FAILURE! > java.lang.AssertionError > at > > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest.assert > InitDataSource(MySQLTimeServiceTest.java:48) > > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MySQLTimeServiceTest.assertInitDataSource:48 > > The root cause is the inputStream is not close then leading to a file > close failure. > > The source code: 55th line of MySQLTimeService.java > > > > linzesi 于2019年11月8日周五 上午10:32写道： > > > > +1. > > > checked list: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifacts have correct names matching the current > release. > [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. > [X] All files have license headers if necessary. > [X] No compiled archives bundled in source archive. > On 11/8/2019 10:24，董。<598363...@qq.com> wrote： > +1. > > > checked list: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifa
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
OS: Windows7 JDK: 1.8.0_162" mvn install or run the single test case MySQLTimeServiceTest can cause that failure. Juan Pan 于2019年11月8日周五 下午1:41写道： > Hi Yonglun, > > > Thanks for your feedback. Actually, the exception you mentioned didn’t > happened to me, either i run `MySQLTimeServiceTest` separately or > installed the whole project. Can you provide more details about your > runtime environment or test procedure? > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/8/2019 13:25，Zhang Yonglun wrote： > I have installed the source code and a unit test failed: > > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 0.48 s <<< FAILURE! - in > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest > [ERROR] > > assertInitDataSource(org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest) > Time elapsed: 0.329 s <<< FAILURE! > java.lang.AssertionError > at > > org.apache.shardingsphere.route.time.mysql.MySQLTimeServiceTest.assertInitDataSource(MySQLTimeServiceTest.java:48) > > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MySQLTimeServiceTest.assertInitDataSource:48 > > The root cause is the inputStream is not close then leading to a file close > failure. > > The source code: 55th line of MySQLTimeService.java > > > > linzesi 于2019年11月8日周五 上午10:32写道： > > > > +1. > > > checked list: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifacts have correct names matching the current release. > [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. > [X] All files have license headers if necessary. > [X] No compiled archives bundled in source archive. > On 11/8/2019 10:24，董。<598363...@qq.com> wrote： > +1. > > > checked list: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifacts have correct names matching the current release. > [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. > [X] All files have license headers if necessary. > [X] No compiled archives bundled in source archive. > > > > Best wishes. > > > --原始邮件-- > 发件人:"Sion Yang" 发送时间:2019年11月8日(星期五) 上午9:21 > 收件人:"dev" > 主题:Re:Re: [VOTE] Release Apache ShardingSphere (Incubating) > 4.0.0-RC3 ROUND 3 > > > > +1. > > I checked: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifacts have correct names matching the current release. > [X] 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. > > > > > -- > > Yi Yang(Sion) > Apache ShardingSphere > > > > At 2019-11-07 20:23:18, "zhangli...@apache.org" wrote: > +1. > > I checked: > > [X] Download links are valid. > [X] Checksums and PGP signatures are valid. > [X] DISCLAIMER is included. > [X] Source code artifacts have correct names matching the current > release. > [X] 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. > > -- > > Liang Zhang (John) > Apache ShardingSphere Dubbo > > > Juan Pan > Hi ShardingSphere Community, > > > I tried my best to solve the issues you raised, and went through > the check > list twice to avoid the confusion, but your review and vote on > this release > is important to us. Look forward to your attention and > interaction. > > > Release notes: > > > > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > <https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md> > < > https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > > > ; > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ > > <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/> > < > https://
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3
ngsphere/KEYS > > <https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS> > ; > > Look at here for how to verify this release candidate: > > https://shardingsphere.apache.org/community/en/contribute/release/ > > <https://shardingsphere.apache.org/community/en/contribute/release/> > ; > > The vote will be open for at least 72 hours or until necessary > number of > votes are reached. > > > Please vote accordingly: > > > [ ] +1 approve > > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > Checklist for reference: > > > [ ] Download links are valid. > > > [ ] Checksums and PGP signatures are valid. > > > [ ] DISCLAIMER is included. > > > [ ] Source code artifacts have correct names matching the current > release. > > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere > repo. > > > [ ] All files have license headers if necessary. > > > [ ] No compiled archives bundled in source archive. > > > > > Best wishes, > Trista > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > -- Zhang Yonglun Apache ShardingSphere
Re: [DISCUSS] The DataBase UNSIGNED INT and UNSIGNED BIGINT column return value discuss
Looks good to me. Sion Yang 于2019年10月17日周四 上午8:56写道： > It's sounds great. > > > > > -- > > Yi Yang(Sion) > Apache ShardingSphere > > > > At 2019-10-16 21:51:32, "董。" <598363...@qq.com> wrote: > >Hi ALL: > > > > We discuss a code implementation about a issue and a PR. > > > > > > the issue is: > https://github.com/apache/incubator-shardingsphere/issues/3231 > > > > > > the PR is: > https://github.com/apache/incubator-shardingsphere/pull/3288 > > > > > > We discuss the relationship between Database numeric (int & bigint) > column type and Java DataType. > > > > > > If Database column type is INT, we can use JDBC's ResultSet#getInt() > method, get the column data. > > > > > > But if the column type is UNSIGNED INT, the value maybe beyond Java's > Integer value range, so we shoudld use JDBC's ResultSet#getLong() method to > get the column data. > > > > > > So the result of discussion is: > > > > > > If column type is TINYINT & SMALLINT & SIGNED INT, we use JDBC's > ResultSet#getInt() method to get column data; > > If column type is UNSIGNED INT, we use JDBC's ResultSet#getLong() > method to get column data; > > If column type is SIGNED BIGINT, we use JDBC's ResultSet#getLong() > method to get column data; > > If column type is UNSIGNED BIGINT, we use JDBC's > ResultSet#getBigDemical() method to get column data and return BigInteger > Object. > -- Zhang Yonglun Apache ShardingSphere
Re: Suggest to add team page to our website
Hi Zesi, I found that neither the name nor the Github ID is in alphabet order, please have a check. I suggest use name to sort. Juan Pan 于2019年9月22日周日 下午3:35写道： > You're right, Sheng. > When a new committer appears, we should tell him or her to add his or her > name to this page. > > > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > On 09/21/2019 23:50, Sheng Wu wrote: > I think new committer should update their name by themselves, it should be > easy PR. > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > sunbufu 于2019年9月21日周六 下午10:52写道： > > > Hi, My name is Haisheng Sun(孙海生), My apache id and github id is sunbufu. > > > > Thank you. > > > > > > On 09/21/2019 22:38, Juan Pan wrote: > > Hi Guangyuan and Haisheng, > > > > Can u provide your name and Apache ID? It will help lzs to add your > > information to our team page. > > > > Thanks. > > > > Regards, > > Trista > > > > > > > > > > Juan Pan > > > > > > panj...@apache.org > > Juan Pan(Trista), Apache ShardingSphere > > On 09/21/2019 22:34, Juan Pan wrote: > > Thanks for your contribution, now we have ShardingSphere team page, it is > > great. But There are Chinese words on this page, so can u modify them? > > > > > > Moreover, two new committers joined in us last week, so i think their > > names should be on the committer list on this page as well. > > > > > > Can you add our two new committers to this page? > > > > > > Thinks a lot :) > > > > > > Regards, > > Trista > > > > > > Juan Pan > > > > > > panj...@apache.org > > Juan Pan(Trista), Apache ShardingSphere > > On 09/21/2019 13:45, lzs wrote: > > > > > > We added this team introduce page at > > https://shardingsphere.apache.org/community/en/team/ > > | | > > lzs > > | > > | > > geo...@163.com > > | > > 签名由网易邮箱大师定制 > > On 9/18/2019 14:44，lzs wrote： > > We're willing to do this.Thank you for your suggestion. > > > > > > | | > > lzs > > | > > | > > geo...@163.com > > | > > > > > > On 9/18/2019 14:29，zhangli...@apache.org wrote： > > Great, we should add this page > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > Sheng Wu 于2019年9月18日周三 下午1:55写道： > > > > Hi ShardingSphere > > > > As we have invited some new committers to the project, I suddenly > noticed, > > we don't have a team page, like this. http://skywalking.apache.org/team/ > > Listing our PPMC, mentors, committers and all other contributors. > > > > I think we should add that page. Any thoughts? > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 > > > > > -- Zhang Yonglun Apache ShardingSphere
new committer: Yanan Zhao
The Podling Project Management Committee (PPMC) for Apache ShardingSphere has invited Yanan Zhao to become a committer and we are pleased to announce that she has accepted. -- Zhang Yonglun Apache ShardingSphere
