Re: [VOTE] Graduate Apache ShardingSphere (incubating)
+1 — Haisheng Sun (sunbufu) Apache ShardingSphere On 03/5/2020 12:57，Zhang Yonglun wrote： +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:[DISCUSS] Change the default branch to 'master' in GitHub
+1 — Haisheng Sun (sunbufu) Apache ShardingSphere On 01/17/2020 13:47，Zhang Yonglun wrote： 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:[DISCUSS] merge docs and example repos into trunk repo
+1 It is easier to find example for new user. — Haisheng Sun (sunbufu) Apache ShardingSphere On 01/17/2020 14:28，Sion Yang wrote： Nice idea. This can reduce the difference between example and trunk repo. -- Yi Yang(Sion) Apache ShardingSphere At 2020-01-17 12:15:29, "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] New committer: Xiaofeng Jiang
Congratulations! — Haisheng Sun (sunbufu) Apache ShardingSphere On 01/8/2020 14:42，zhaojun wrote： Congratulations! -- Zhao Jun (cherrylzhao) Apache ShardingSphere & ServiceComb On Jan 8, 2020, at 2:02 PM, 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 I have checked the following items. Checklist for reference: [v] Download links are valid. [v] Checksums and PGP signatures are valid. [v] DISCLAIMER is included. [v] Source code artifacts have correct names matching the current release. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/31/2019 11:16，Sion Yang wrote： +1 I checked the LICENSE, NOTICE, Checksums, PGP signatures and installing source code. No problem happened. -- Yi Yang(Sion) Apache ShardingSphere At 2019-12-30 21:43:37, "zhangli...@apache.org" wrote: Hello ShardingSphere Community, This is a call for vote to release Apache ShardingSphere (Incubating) version 4.0.0 Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1029/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/f81f4f03b1dd4b426adf1f29ffe93f9540ce6fc9 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re: Discussion of which data should be put in the new registry center and which data should be put in the new config center
Hi. The follow is the full old registry center data. ``` ├──config ├ ├──authentication# Sharding-Proxy ├ ├──props # Properties configuration ├ ├──schema# Schema configuration ├ ├ ├──sharding_db# SchemaName configuration ├ ├ ├ ├──datasource # Datasource configuration ├ ├ ├ ├──rule# Sharding rule configuration ├ ├ ├──masterslave_db # SchemaName configuration ├ ├ ├ ├──datasource # Datasource configuration ├ ├ ├ ├──rule# Master-slave rule ├ ├ ├──encrypt_db # SchemaName configuration ├ ├ ├ ├──datasource # Datasource configuration ├ ├ ├ ├──rule# Encrypt rule ├──state ├ ├──instances ├ ├ ├──your_instance_ip_a@-@your_instance_pid_x ├ ├ ├──your_instance_ip_b@-@your_instance_pid_y ├ ├ ├── ├ ├──datasources ├ ├ ├──ds0 ├ ├ ├──ds1 ├ ├ ├── ``` — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/29/2019 02:32，Zonglei Dong wrote： For ConfigCenter, the config info for “Data Masking” should be included. Firstly, I think we should list all the info in the old RegistryCenter, then split which should be put into ConfigCenter or RegistryCenter. We can reference the offical document. https://shardingsphere.apache.org/document/current/cn/features/orchestration/config-center/ https://shardingsphere.apache.org/document/current/cn/features/orchestration/orchestration/ https://shardingsphere.apache.org/document/current/cn/features/orchestration/encrypt/ Zonglei Dong Apache ShardingSphere On 12/28/2019 20:54，guangyuan wang wrote： For "config" part, masterslave_db should be added. config ├──authentication# Sharding-Proxy authentication configuration ├──props # Properties configuration ├──schema# Schema configuration ├ ├──sharding_db# SchemaName configuration ├ ├ ├──datasource # Datasource configuration ├ ├ ├──rule# Sharding rule configuration ├ ├──masterslave_db # SchemaName configuration ├ ├ ├──datasource # Datasource configuration ├ ├ ├──rule# Master-slave rule configuration sunbufu 于2019年12月28日周六 下午1:48写道： Hi all. We are working on orchestration-5.x as plain ( https://github.com/apache/incubator-shardingsphere/issues/3185). And now, we get a question in step 3 to discussion with you. In step 3, we should replace the call relationship of old registry center by the call relationship of new registry center and new config center, and then we can delete the old registry center. In other words, we should put the data from old registry center in new registry center and new config center. So ** which data should be put in the new registry center and which data should be put in the new config center ? ** The follow is an example data from old registry center : ``` orchestration_ds config authentication props schema sharing_db datasource rule state datasources instances ``` I have discussed with Zonglei and Yuan. We think we can put `config` node in the new config center, cause `config` node include some config data, such as `authentication` have user’s password. the same reason we can put `state` node in the new registry center. But we are not sure about this, can you confirm it for me ? — Haisheng Sun (sunbufu) Apache ShardingSphere
Discussion of which data should be put in the new registry center and which data should be put in the new config center
Hi all. We are working on orchestration-5.x as plain (https://github.com/apache/incubator-shardingsphere/issues/3185). And now, we get a question in step 3 to discussion with you. In step 3, we should replace the call relationship of old registry center by the call relationship of new registry center and new config center, and then we can delete the old registry center. In other words, we should put the data from old registry center in new registry center and new config center. So ** which data should be put in the new registry center and which data should be put in the new config center ? ** The follow is an example data from old registry center : ``` orchestration_ds config authentication props schema sharing_db datasource rule state datasources instances ``` I have discussed with Zonglei and Yuan. We think we can put `config` node in the new config center, cause `config` node include some config data, such as `authentication` have user’s password. the same reason we can put `state` node in the new registry center. But we are not sure about this, can you confirm it for me ? — Haisheng Sun (sunbufu) Apache ShardingSphere
Re: [Discuss] sharding-orchestration module reconstruction
I misunderstood the meaning of yuan in last email. But after communicating with yuan on WeChat, we get a tentative agreement want to discuss with you . We need 2 main steps to do in reconstruct orchestration module. # 1 Replace old orchestration module with new orchestration module. ## 1.1 Remove the old modules. ## 1.2 Rename the new modules. ## 1.3 Modify references we can easy find. ## 1.4 Follow the error lead. # 2 Replace old registry call relations with new config center, registry center, distributed lock manager. About step 2, we still have a lot to do, such as which data should be manage by the new registry center. So we think we can discuss the step 2 in other email. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/12/2019 10:42，Juan Pan wrote： Take it easy. And FYI, maybe we could modify the internal of orchestration without changing API of orchestration. When the refactoring of orchestration finishes, API changes and behavior changes of callers comes. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 20:32，sunbufu wrote： I think this maybe not so hard, we can do this like follow. 1. Remove the old modules. 2. Rename the new modules. 3. Modify references we can easy find. 4.Follow the error lead. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/11/2019 16:14，guangyuan wang wrote： The modifications in sharding-orchestration are: 1. The RegistryCenter is changed to split into 3 interfaces: ConfigCenter, Registry Center, DistributedLockManagement. 2. The related implementation class is changed and initialization is changed. These changes mean the sharding-orchestration module will be totally changed. So we create two modules in the sharding-orchestration to replace old modules in the sharding-orchestration. And now I wanna make the replacing. But it's huge task, because many classes of the sharding-orchestration are called by other modules. I'd like to discuss the workflow of the replacing, to make this action safely be done without any unit test failure. Juan Pan 于2019年12月11日周三 下午4:02写道： Hi Yuan, I’d like to join in discussion, however i have no idea about what is going now, could you draft a workflow or schedule to give us a basic understanding about it. Based on that, maybe others could give some great suggestion or idea. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 14:28，guangyuan wang wrote： Hello everyone I'd like to reconstruct the sharding-orchestration module. So far as, we have develop a new sharding-orchestration-center module and sharding-orchestration-core-new module. I'd like to use them to replace the old ones. But It's really huge engineering. So I'd like to discuss the workflow of the reconstruction. Do you have any good suggestions?
Re: [Discuss] sharding-orchestration module reconstruction
I think this maybe not so hard, we can do this like follow. 1. Remove the old modules. 2. Rename the new modules. 3. Modify references we can easy find. 4.Follow the error lead. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/11/2019 16:14，guangyuan wang wrote： The modifications in sharding-orchestration are: 1. The RegistryCenter is changed to split into 3 interfaces: ConfigCenter, Registry Center, DistributedLockManagement. 2. The related implementation class is changed and initialization is changed. These changes mean the sharding-orchestration module will be totally changed. So we create two modules in the sharding-orchestration to replace old modules in the sharding-orchestration. And now I wanna make the replacing. But it's huge task, because many classes of the sharding-orchestration are called by other modules. I'd like to discuss the workflow of the replacing, to make this action safely be done without any unit test failure. Juan Pan 于2019年12月11日周三 下午4:02写道： Hi Yuan, I’d like to join in discussion, however i have no idea about what is going now, could you draft a workflow or schedule to give us a basic understanding about it. Based on that, maybe others could give some great suggestion or idea. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/11/2019 14:28，guangyuan wang wrote： Hello everyone I'd like to reconstruct the sharding-orchestration module. So far as, we have develop a new sharding-orchestration-center module and sharding-orchestration-core-new module. I'd like to use them to replace the old ones. But It's really huge engineering. So I'd like to discuss the workflow of the reconstruction. Do you have any good suggestions?
Re: Discussion of pluggable platform of ShardingSphere
+1 Good idea. It’s a good long-term planning for ShardingSphere. — Haisheng Sun (sunbufu) Apache ShardingSphere On 12/9/2019 18:43，Juan Pan wrote： Agree with Liang, Maybe there is no feature benefit apparently, however we make its architecture become…a structured plaza with many rooms. Consequently, more contributors could fill in specific implements for those rooms with less harms to this plaza, i.e our project. Oh, i have a great imagination, don’t you think so? :) Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 12/9/2019 14:13，Nicholas wrote： Hi guys, What features will be planned in pluggable platform? And how to assign features splits from sharding-core? Based on user concept，what does user benefit from this pluggable platform? Thanks, Nicholas Jiang On 2019/12/09 05:29:47, "zhangli...@apache.org" wrote: Hi, ShardingSphere community, More and more features are added into ShardingSphere now, as you know, the scope of ShardingSphere is no longer for sharding only. There are more and more features related with sharding, such as distributed transaction, distributed orchestration, observability and so on; and there are couple of features did not relate with sharding obviously, for example: encrypt, shadow data source, SQL audit and so on. I'd like to discuss about establishing a pluggable platform of ShardingSphere. The proposal of pluggable platform is decoupling all features and technical implementations, the benefits are: 1. Flexible for add new feature. 2. Reduce the negative effects if problem occur on one feature. 3. Provide a platform to make more contributors work together without interact on each other. I plan split all features from sharding-core first, and then use SPI to introduce features into the pluggable platform(same thing with sharding, sharding can be remove from main process too). The pluggable platform is a blank JDBC and database protocol finally, and provide assist technical features such as SQL parser and SQL rewrite. Any advice? -- Liang Zhang (John) Apache ShardingSphere & Dubbo
Re: Reconstruct sharding-orchestration module
Hi, In the result of discussion, orchestration-type is better than center-type. cause it is not good to introduce new concepts. — Haisheng Sun (sunbufu) Apache ShardingSphere On 11/27/2019 08:45, guangyuan wang wrote: Dear All As the registry center interface was used as distributed lock management and config center, I think it's better to split it into three parts, they are: config center, registry center, distributed lock management. And the configuration yml file, looks like these: spring: shardingsphere: orchestration: testname1: center-type: registry_center,distributed_lock_management instance-type: zookeeper server-lists: 192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003 namespace: testnamspace1 props: overwrite: false retry-interval-milliseconds: 10 time-to-live-seconds: 10 max-retries: 10 operation-timeout-milliseconds: 10 digest: testname2: center-type: configuration_center instance-type: apollo server-lists: 192.178.32.45:9001,192.178.32.45:9002,192.178.32.45:9003 namespace: testnamspace2 props: overwrite: true retry-interval-milliseconds: 10 time-to-live-seconds: 10 max-retries: 10 operation-timeout-milliseconds: 10 digest:
Re:[VOTE] Accept ShardingScaling Donation ROUND2
+1 | | sunbufu | | ??sunyoub...@163.com email??sunb...@apache.com | ?? On 11/13/2019 11:57??Cookie wrote?? +1 Ya Li l...@apache.org Ya Li(github:betterjava), Apache ShardingSphere ---- ??:"Sion Yang"https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%3Cdev.shardingsphere.apache.org%3E https://lists.apache.org/thread.html/a1ef4b44abe8f11273983e69c12becda12302aee852f7569c99a34d1@%3Cdev.shardingsphere.apache.org%3E Please accept the ShardingScaling podling into the Apache Incubator. The proposal can be found at https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal Here is the text of it: ## Abstract ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere Incubator[2]. It is designed to help users migrate data from origin database to ShardingSphere or scale out ShardingSphere data node more easily. It provides ability of migrant data, scaling out data nodes, etc. ## Proposal The goal of this proposal is to bring the existing ShardingScaling codebase and existing developers and community into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. This project started in Open Source on Github nearly 2 months. ShardingScaling is submitting this proposal to donate it to the Apache ShardingSphere Incubator under the Apache License, Version 2.0, in order to provide a visual management tool for ShardingSphere. These artifacts are currently available on GitHub at [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Background ShardingSphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. It is also widely adopted by many companies and organizations as a solution to process their massive amounts of data. But users have long lacked an easy-to-use way to migrate their data from origin database when they first started using ShardingSphere. Moreover, users have also lacked easy-to-use ways to expand data nodes when they use ShardingSphere for a while. So Wen OuYang created a scaling out component for ShardingSphere -- ShardingScaling. ## Current status After we pushed ShardingScaling in Github in an open source way, many users and developers have shown strong intentions to this. Yi Yang, ZongLei Dong and ssxlulu have contributed many features and codes. Current, ShardingScaling has implemented basic data migration and scaling out data nodes feature. ## Core developer Wen OuYang is an experienced open source developer. Yi Yang is an experienced open source developer and ShardingSphere PPMC. ## Donation source Github repo: [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling). ## Source and Intellectual Property Submission Plan ShardingScaling was opened in Github on 18 Sep 2019. The project major contributors are Wen OuYang, Yi Yang. Yi Yang is ShardingSphere's PPMC, ICLA are submitted. Wen OuYang will sign ICLA and become Apache committer if vote be accepted after ShardingScaling is accepted into the Apache Software Foundation (ASF) as ShardingSphere's sub-project. ## External Dependencies ### Apache 2.0 licenses - sharding-core-common 4.0.0-RC2: [https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere) - snakeyaml 1.16: [https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default) - guava 18.0: [https://github.com/google/guava](https://github.com/google/guava) - netty-all 4.1.16.Final: [https://github.com/netty/netty](https://github.com/netty/netty) - commons-dbcp2 2.7.0: [https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp) - commons-cli 1.4: [https://github.com/apache/commons-cli](https://github.com/apache/commons-cli) - log4j 1.2.17: [https://github.com/apache/log4j](https://github.com/apache/log4j) - gson 2.8.6: [https://github.com/google/gson](https://github.com/google/gson) ### MIT licenses - slf4j-api 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - slf4j-log4j12 1.7.28: [https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j) - lombok 1.18.4: [https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok) - mockito-core 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) - mockito-inline 2.7.21(scope test): [https://github.com/mockito/mockito](https://github.com/mockito/mockito) ### EPL 1.0 licenses - junit 4.12(scope test): [https://github.com/junit-team/junit4](https://github.com/junit-team/junit4) ### BSD License - hamcrest-library 1.3(scope test): [https://github.com/hamcrest/JavaHamcrest](https://github.com/hamcrest/Ja
Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4
LGTM. +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. | | sunbufu | | 邮箱：sunyoub...@163.com email：sunb...@apache.com | On 11/13/2019 14:00，duhongjun 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. -- - HongJun Du Apache ShardingSphere At 2019-11-11 18:40:26, "Juan Pan" wrote: Hi everyone, With the help and effort of our community, the previous issues were fixed already. I am glad to invite everyone to move on to check and vote for our 4.0.0-RC3 ROUND 4. Release notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/ Maven 2 staging repository: https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/ Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:[ISSUE] Can't getClob for LongVarchar type data.
I am agree with Yi Yang, I want to handle the `Clob` conversion. | | sunbufu | | 邮箱：sunyoub...@163.com email：sunb...@apache.com | 签名由网易邮箱大师定制 On 10/10/2019 15:25，Sion Yang wrote： Hi all the contributors and committers,Recently, some of issues like #2956[1] #3017[2] feedback exception when getClob for longVarchar type data.After investigation, this problem is be caused by getting value according to the metadata.ShardingSphere use `getString` to get LongVarchar type data, and return String type, but `getClob` should return Clob type.For fix this problem, we need to get value accroding to target type in StreamQueryResult instead of metadata type.But for MemoryQueryResult, ShardingSphere need to get value before users call getXXX method. So should we transfer the value to target type in ShardingResultSet/EncryptResultSet like `getDate` method do? -- Yi Yang(Sion) Apache ShardingSphere
Re:[ANNOUNCE] New committer: Qi Wang
Congratulation! On 09/25/2019 10:45，Chen QingYang wrote： The Podling Project Management Committee (PPMC) for Apache ShardingSphere has invited Qi Wang to become a committer and we are pleased to announce that he has accepted. Qi Wang did a lot of contributions for ShardingSphere community. Please join me to say congratulations to him! -- Chen QingYang Apache ShardingSphere
Re: Suggest to add team page to our website
Hi, My name is Haisheng Sun(孙海生), My apache id and github id is sunbufu. Thank you. On 09/21/2019 22:38, Juan Pan wrote: Hi Guangyuan and Haisheng, Can u provide your name and Apache ID? It will help lzs to add your information to our team page. Thanks. Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 22:34, Juan Pan wrote: Thanks for your contribution, now we have ShardingSphere team page, it is great. But There are Chinese words on this page, so can u modify them? Moreover, two new committers joined in us last week, so i think their names should be on the committer list on this page as well. Can you add our two new committers to this page? Thinks a lot :) Regards, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 09/21/2019 13:45, lzs wrote: We added this team introduce page at https://shardingsphere.apache.org/community/en/team/ | | lzs | | geo...@163.com | 签名由网易邮箱大师定制 On 9/18/2019 14:44，lzs wrote： We're willing to do this.Thank you for your suggestion. | | lzs | | geo...@163.com | On 9/18/2019 14:29，zhangli...@apache.org wrote： Great, we should add this page -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2019年9月18日周三 下午1:55写道： Hi ShardingSphere As we have invited some new committers to the project, I suddenly noticed, we don't have a team page, like this. http://skywalking.apache.org/team/ Listing our PPMC, mentors, committers and all other contributors. I think we should add that page. Any thoughts? Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re:new committer: Haisheng Sun
Thank you for your trust, Hope to continue to contribute to ShardingSphere community with you. On 09/18/2019 11:16，Juan Pan wrote： TheProjectManagementCommittee(PMC)forApache ShardingSphere hasinvited Haisheng Sun tobecomeacommitterandwearepleasedtoannouncethathehasaccepted. Haisheng Sun is active in ShardingSphere community, hope your further interactions with the community! Thanks for your contributions. Best wishes, Trista Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2 [ROUND 4]
+1 The following checking items have been done. [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] DISCLAIMER is included. [X] Source code artifacts have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each ShardingSphere repo. [X] All files have license headers if necessary. [X] No compiled archives bundled in source archive. At 2019-08-17 15:44:36, "Zhang Yonglun" wrote: >Hello ShardingSphere Community, > >This is a call for vote to release Apache ShardingSphere (Incubating) >version 4.0.0-RC2 > >Release notes: >https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md > >The release candidates: >https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/ > >Maven 2 staging repository: >https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > >Git tag for the release: >https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2 > >Release Commit ID: >https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36 > >Keys to verify the Release Candidate: >https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS >GPG username: zhangyonglun > >Look at here for how to verify this release candidate: >https://shardingsphere.apache.org/community/en/contribute/release/ > >The vote will be open for at least 72 hours or until necessary number of >votes are reached. > >Please vote accordingly: > >[ ] +1 approve > >[ ] +0 no opinion > >[ ] -1 disapprove with the reason > >Checklist for reference: > >[ ] Download links are valid. > >[ ] Checksums and PGP signatures are valid. > >[ ] DISCLAIMER is included. > >[ ] Source code artifacts have correct names matching the current release. > >[ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > >[ ] All files have license headers if necessary. > >[ ] No compiled archives bundled in source archive. > >-- >Zhang Yonglun >Apache ShardingSphere
