Re: [VOTE] Release Apache ShardingSphere 5.0.0-alpha

2020-11-08 Thread 蒋晓峰 
+1 non-binding

The following checklist has been verified.

[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.



Nicholas Jiang

Apache ShardingSphere

On Tue, Nov 3, 2020 at 12:29 PM Juan Pan  wrote:

> 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-3.0.0-beta [Round 4]

2020-10-31 Thread 蒋晓峰 
+1 non-binding

Regards,
Nicholas Jiang

On Sat, Oct 31, 2020 at 10:58 PM zhangli...@apache.org <
zhangli...@apache.org> wrote:

> 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 ShardingSphere ElasticJob-3.0.0-beta

2020-10-26 Thread 蒋晓峰 
+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.

On Mon, Oct 26, 2020 at 10:30 AM zhaojun  wrote:

> +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.
>
> Regards,
> cherrylzhao
> ---
> Email：zhao...@apache.org
> Jun Zhao(cherrylzhao) Apache ShardingSphere
>
>
> zhangli...@apache.org  于2020年10月25日周日 下午4:29写道：
>
> > 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-1053/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/9eafbd3c2a4c5a4abc5d639952f5c43c15e10f47
> >
> > 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: [DISCUSS] Rename MasterSlave module to ReadWriteSplit

2020-09-15 Thread 蒋晓峰 
Hi Liang,
   In my opinion, primary-replica naming makes confusion for developers how
to understand the replacement of 'master/slave' to 'primary/replica'. In a
distributed system, 'master/slave' directly describes the relationship
of distributed nodes, but what about 'primary/replica' represents?

Regards,
Nicholas Jiang

On Wed, Sep 16, 2020 at 1:43 PM zhangli...@apache.org 
wrote:

> Primary-replica is good to me.
>
> So, how about:
>
> MasterSlave -> PrimaryReplicaReplication
> MasterDataSource -> PrimaryDataSource
> SlaveDataSource -> ReplicaDataSource
>
> --
>
> Sincerely,
> Liang Zhang (John)
> Apache ShardingSphere
>
>
> Hongwei Li  于2020年9月14日周一 下午10:31写道：
>
> > FYI:
> > primary and replica, replica replication are widely used terms in AWS.
> >
> >
> >
> https://aws.amazon.com/blogs/database/best-practices-for-amazon-rds-postgresql-replication/
> >
> >
> https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Replication.Redis.Groups.html
> >
> > On Mon, Sep 14, 2020 at 1:07 AM Juan Pan  wrote:
> >
> > > Hi Liang,
> > >
> > >
> > > I also looked through many docs of other databases,
> > > like MySQL, MariaDB, PostgreSQL, and MongoDB.
> > >
> > >
> > > For me, I can accept your proposal.
> > >
> > >
> > > In short, no matter `PrimarySecondaryReplication` or
> > > `PrimaryReplicaReplication`,
> > > IMO. We need to focus on `replication` which means a synchronization
> > > process
> > > among primary nodes and secondary nodes (Replica nodes).
> > > The links below will help me explain more.
> > >
> > >
> > >
> > >
> > > [1]
> > >
> >
> https://medium.com/@Jelastic/mongodb-replica-set-with-master-slave-replication-and-automated-failover-be3cb374452
> > > [2]
> > >
> >
> https://www.datadriveninvestor.com/2020/05/28/the-master-slave-database-concept-for-beginners/
> > > [3] https://www.postgresql.org/docs/9.2/warm-standby.html
> > > [4]
> > >
> >
> https://mariadb.com/resources/blog/database-master-slave-replication-in-the-cloud/
> > >
> > >
> > > Best,
> > > Trista
> > >
> > >
> > >  Juan Pan (Trista)
> > >
> > > Senior DBA & PMC of Apache ShardingSphere
> > > E-mail: panj...@apache.org
> > >
> > >
> > >
> > >
> > > On 09/14/2020 12:34，zhangli...@apache.org
> wrote：
> > > I investigate related materials again, maybe read-write-spilt is not a
> > good
> > > name.
> > >
> > > There are two features in Apache ShardingSphere now, master-slave and
> > > replica.
> > >
> > > Master-slave:
> > > Write to master data source and replication data to slave data sources
> > > async, and then read from slave data sources.
> > > Benefit: performance.
> > >
> > > Replica:
> > > Still in dev mode, we plan to use Raft algorithm to keep the multiple
> > > replicas with consensus.
> > > Benefit: consensus.
> > >
> > > The tow features can not use together, users can choose one of them in
> > the
> > > same time only.
> > >
> > > I prefer to rename master-slave module to
> primary-secondary-replication,
> > > and rename replica module to consensus-replication.
> > > The new names can describe the feature more accurate and can let user
> to
> > > know they are mutually exclusive.
> > >
> > > Primary-standby-replication is another choice, but I am afraid the
> > meaning
> > > of `standby` is waiting here and do nothing if normal,
> > > but the secondary data source still need to process the query requests.
> > >
> > > So, how about to rename the concept to:
> > >
> > > MasterSlave -> PrimarySecondaryReplication
> > > MasterDataSource -> PrimaryDataSource
> > > SlaveDataSource -> SecondaryDataSource
> > >
> > > Please advice me.
> > >
> > > --
> > >
> > > Sincerely,
> > > Liang Zhang (John)
> > > Apache ShardingSphere
> > >
> > >
> > > Hongwei Li  于2020年9月14日周一 下午12:02写道：
> > >
> > > I don't have any idea about how the module
> 'shardingsphere-master-slave'
> > vs
> > > 'shardingsphere-read-write-split', was named.
> > > If there was no specific reason, it is like a historical debt, but does
> > not
> > > matter so much, as it has been there for a long time, everyone knows
> > > the function of the module.
> > > In the meantime, 'read-write-split' is more obvious from the
> > > processing/action perspective of the module. 'Master/Slave' is also
> fine
> > > from the processing object(datasource) perspective.
> > >
> > > For simple processing and not considering much, the replacement of
> > > 'master/slave' to 'primary/replica' including the combinations is much
> > > straightforward. It is kind of 'leave it as is' processing.
> > >
> > > For moving one step further, renaming the module to 'read-write-split'
> > is a
> > > way to go. The questions are:
> > > shall we replace 'MasterSlave' as 'ReadWriteSplit' at all places?
> > > Do we need to consider if the replacement is meaningful at any place,
> > such
> > > as the below names:
> > > MasterSlaveDataSourceRuleConfiguration
> > > MasterSlaveLoadBalanceAlgorithm
> > >
> > >
> > >
> > > On Sat, Sep 12, 2020 at 11:29 PM

Re: [DISCUSS] Archive shardingsphere-example and shardingsphere-acceptance-test

2020-08-11 Thread 蒋晓峰 
+1，for community developers and users, it's necessary to remove
the examples to avoid issues about this.

Regards,
Nicholas Jiang

On Tue, Aug 11, 2020 at 2:27 PM Zhang Yonglun 
wrote:

> We should archive the following repos:
>
> https://github.com/apache/shardingsphere-example
> https://github.com/apache/shardingsphere-acceptance-test
>
> All codes of shardingsphere-example have been merged into shardingsphere
> and acceptance-test will not use any more, so we don't need these repos any
> more.
>
> --
>
> Zhang Yonglun
> Apache ShardingSphere
>

Re: [DISCUSS] Rename ShardingSphere GitHub/GitBox repo

2020-07-09 Thread 蒋晓峰 
+1，it's more concise.

On Thu, Jul 9, 2020 at 4:23 PM 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: [ANN] Welcome a new committer Meng Haoran(menghaoranss)

2020-07-06 Thread 蒋晓峰 
Welcome!

Regard,
Nicholas

On Fri, Jul 3, 2020 at 9:26 PM KimmKing  wrote:

> Hello, Community,
>
> On behalf of the Apache ShardingSphere PMC, it is my honor to announce
> that Meng Haoran[1] has been voted in as a new Apache ShardingSphere
> committer.
>
> Please join me to say congratulations to him!
> Haoran, would you give us a briefly introduce of yourself to the community?
>
>
> 1. https://github.com/menghaoranss
>
>
> Yours,
> kimmking

Re: [DISCUSS] Rename ShardingSphere GitHub/GitBox repo

2020-06-16 Thread 蒋晓峰 
+1(binding)

Regards,
Nicholas Jiang

On Wed, Jun 17, 2020 at 11:00 AM Zhang Yonglun 
wrote:

> 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?

2020-06-10 Thread 蒋晓峰 
Agree, and the incubator releases are no longer important for users.

On Wed, Jun 10, 2020 at 10:25 PM Sheng Wu  wrote:

> 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: [Webinar] Exploring Apache ShardingSphere with the perspective of new SQL

2020-05-18 Thread 蒋晓峰 
Sounds very interesting! Looking forward.

On Sun, May 17, 2020 at 7:56 PM Juan Pan  wrote:

> Hello everyone,
>
>
>
>
> I am glad to be invited by itpub.net to give an online presentation,
>
> which chiefly introduces new SQL and the architecture of Apache
> ShardingSphere (Chinese language).
>
> If anyone is interested in this topic,
>
> please feel free to take part in. You can look at [1] to learn more.
>
>
>
>
> Best wishes,
>
> Trista
>
>
>
>
> [1]
> https://github.com/apache/shardingsphere/issues/5659#issuecomment-629784613
>
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>

Re: Fwd: Fwd: Apache ShardingSphere项目社区申请加入『开源软件供应链点亮计划2020』

2020-05-06 Thread 蒋晓峰 
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
>

Re: [ANNOUNCE] New committer: Jinwei Qin

2020-04-15 Thread 蒋晓峰 
Congratulations to Jinwei Qin!

On Tue, Apr 14, 2020 at 10:17 AM Juan Pan  wrote:

> Hi community,TheProjectManagementCommittee(PMC)forApache ShardingSphere
> hasinvited Jinwei Qin
> tobecomeacommitterandwearepleasedtoannouncethathehasaccepted.Welcome
> Jinwei!Best wishes,Trista
>
>  Juan Pan
>
>
> panj...@apache.org
> Juan Pan(Trista), Apache ShardingSphere
>
>

Re: Congratulations! The board made ShardingSphere TLP today

2020-04-15 Thread 蒋晓峰 
Congratulations to ShardingSphere!

On Thu, Apr 16, 2020 at 9:19 AM Craig Russell  wrote:

> ShardingSphere is now officially an Apache Project!
>
> Champagne! Balloons! Parades! Dragons!
>
> Best,
> Craig
>
> Craig L Russell
> c...@apache.org
>
>

Re: [VOTE] Graduate Apache ShardingSphere (incubating)

2020-03-07 Thread 蒋晓峰 
+1

On Thu, Mar 5, 2020 at 12:05 PM zhangli...@apache.org 
wrote:

> 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: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.1

2020-02-28 Thread 蒋晓峰 
+1

On Tue, Feb 25, 2020 at 10:48 PM zhaojun  wrote:

> Hello ShardingSphere Community,
>
> This is a call for vote to release Apache ShardingSphere (Incubating)
> version 4.0.1
>
> Release notes:
>
> https://github.com/apache/incubator-shardingsphere/blob/dev-4.x/RELEASE-NOTES.md
> <
> https://github.com/apache/incubator-shardingsphere/blob/dev-4.x/RELEASE-NOTES.md
> >
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.1/ <
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.1/>
>
> Maven 2 staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1047/org/apache/shardingsphere/
> <
> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1047/org/apache/shardingsphere/
> >
>
> Git tag for the release:
> https://github.com/apache/incubator-shardingsphere/tree/4.0.1/ <
> https://github.com/apache/incubator-shardingsphere/tree/4.0.1/>
>
> Release Commit ID:
>
> https://github.com/apache/incubator-shardingsphere/commit/b67d320209b4d4585231b356f2c575cfa383a98b
> <
> https://github.com/apache/incubator-shardingsphere/commit/b67d320209b4d4585231b356f2c575cfa383a98b
> >
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS>
>
> Look at here for how to verify this release candidate:
> https://shardingsphere.apache.org/community/en/contribute/release/ <
> https://shardingsphere.apache.org/community/en/contribute/release/>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.
>
> --
> Zhao Jun (cherrylzhao)
> Apache ShardingSphere & ServiceComb
>
>

Re: Mentor invitation of the ShardingSphere PMC

2020-02-17 Thread 蒋晓峰 
Yes.

On Mon, Feb 17, 2020 at 5:42 PM zhangli...@apache.org 
wrote:

> Dear ShardingSphere mentors,
>
> Please accept our deepest thanks of the great help during ASF incubator
> from ShardingSphere community.
>
> We are nearly graduation now. I sincere invitation you as of ShardingSphere
> PMC member.
>
> If you'd like to be the member of ShardingSphere PMC, it's welcome and
> please respond 'Yes' in this thread, or *respond 'No' if you are not
> interested in any more, 'Yes' by default.
>
>
> --
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>

Re: [DISCUSS] Optimization for Sharing Parser with Antlr Visitor

2020-02-17 Thread 蒋晓峰 
Hi Juan,
I'm very willing to wait for your ping. Any time you ping me, I would
like to be assigned for something about this issue.

Thanks,
Nicholas

On Mon, Feb 17, 2020 at 11:50 AM Juan Pan  wrote:

> Hi Nicholas,
> Very appreciated for your close follow-up for this thread.
> You can learn more about the most recent progress of this task here [1].
> I am handling this issue, and when i need your assistance, could i ping
> you then?
>
>
> Regards,
> Trista
>
>
> [1] https://github.com/apache/incubator-shardingsphere/issues/4335
>
>
>
>
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/16/2020 22:16，蒋晓峰 wrote：
> Hi Juan,
> What's the plan of improvements for new MySQL parser? I found no email
> including something about improvements for new MySQL parser.
>
> Thanks,
> Nicholas
>
> On Thu, Feb 13, 2020 at 3:17 PM Juan Pan  wrote:
>
> Hi everyone,
>
>
> Good news for us that we basically finish the parser refactoring for
> MySQL.[1]
> Specially thanks for @terrymanu @SteNicholas @dongzl @tianbin1001
> @beijing-penguin!
>
>
> Our next step is to do some improvements for new MySQL parser, and
> continue working on parser refactoring for other databases.
> So Veterans, would you like to move on? Additionally, we welcome anyone to
> join us for parser integrated tests!
> Please reply to give your comment.
>
>
> Best wishes,
>
>
> [1] https://github.com/apache/incubator-shardingsphere/issues/3914
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/12/2020 10:32，Juan Pan wrote：
> Kind reminder,
> If you could not edit issue, please be free to contact any committer or
> reply this email then i will provide you any help.
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/12/2020 10:25，Juan Pan wrote：
> Hi everyone,
>
>
> The task of `DML SQL Visitor` has made some progress, and i updated the
> status of issue #3914.
> However, i am unclear of others’ progress, any changes, could you please
> update the issue[1][2]?
>
>
> [1]
>
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-581108911
> [2]
>
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-583220969
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/7/2020 11:51，Juan Pan wrote：
> Hi
>
>
> Provide feedback on task progress, refer to [1] to learn more. Welcome
> your any suggestion.
>
>
> [1]
>
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-583220969
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/2/2020 18:04，Juan Pan wrote：
> Hi everyone,
>
>
> Thanks for your attention.
> I am glad to tell the community that this long-term task has been on the
> right way and made some progress. Please refer to [1]  for its detailed
> progress.
> Many thanks for the contributions from SteNicholas, dongzl, jingshanglu,
> tianbin1001 and beijing-penguin and your effort make this progress
> possible.
>
>
> However there are many optimization and work for community to do for this
> task, so we welcome everyone interested in it to join us!
>
>
> Hope your good health during this special Chinese new year.
>
>
> - [1]
>
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-581108911
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 01/9/2020 14:20，Juan Pan wrote：
> Hi folks,
>
>
> It is not common practice and prone to low performance that
> `ExtractorEngine` and `FillerEngine` are used to get final SQL parsed
> result based on AST generated by ANTLR at present. Upon investigation, we
> would like to replace them with ANTLR visitor.
>
>
> It is scheduled as a long-term task and a big change for our 5.x release,
> and currently i am trying to do some basic work for our new branch[1].
> After the groundwork (Roughly estimated time is one week. ) is basically
> laid, we would like to welcome anyone who is interested in it to join us
> for this wonderful sharding parser.
>
>
> Please watch this thread for follow-up. What’s more, welcome your any
> comment and suggestion!
>
>
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/tree/sharding-parser-5.x
>
>
>
>
>
>
> Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
>

Re: [DISCUSS] Optimization for Sharing Parser with Antlr Visitor

2020-02-16 Thread 蒋晓峰 
Hi Juan,
What's the plan of improvements for new MySQL parser? I found no email
including something about improvements for new MySQL parser.

Thanks,
Nicholas

On Thu, Feb 13, 2020 at 3:17 PM Juan Pan  wrote:

> Hi everyone,
>
>
> Good news for us that we basically finish the parser refactoring for
> MySQL.[1]
> Specially thanks for @terrymanu @SteNicholas @dongzl @tianbin1001
> @beijing-penguin!
>
>
> Our next step is to do some improvements for new MySQL parser, and
> continue working on parser refactoring for other databases.
> So Veterans, would you like to move on? Additionally, we welcome anyone to
> join us for parser integrated tests!
> Please reply to give your comment.
>
>
> Best wishes,
>
>
> [1] https://github.com/apache/incubator-shardingsphere/issues/3914
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/12/2020 10:32，Juan Pan wrote：
> Kind reminder,
> If you could not edit issue, please be free to contact any committer or
> reply this email then i will provide you any help.
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/12/2020 10:25，Juan Pan wrote：
> Hi everyone,
>
>
> The task of `DML SQL Visitor` has made some progress, and i updated the
> status of issue #3914.
> However, i am unclear of others’ progress, any changes, could you please
> update the issue[1][2]?
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-581108911
> [2]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-583220969
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/7/2020 11:51，Juan Pan wrote：
> Hi
>
>
> Provide feedback on task progress, refer to [1] to learn more. Welcome
> your any suggestion.
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-583220969
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/2/2020 18:04，Juan Pan wrote：
> Hi everyone,
>
>
> Thanks for your attention.
> I am glad to tell the community that this long-term task has been on the
> right way and made some progress. Please refer to [1]  for its detailed
> progress.
> Many thanks for the contributions from SteNicholas, dongzl, jingshanglu,
> tianbin1001 and beijing-penguin and your effort make this progress
> possible.
>
>
> However there are many optimization and work for community to do for this
> task, so we welcome everyone interested in it to join us!
>
>
> Hope your good health during this special Chinese new year.
>
>
> - [1]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-581108911
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 01/9/2020 14:20，Juan Pan wrote：
> Hi folks,
>
>
> It is not common practice and prone to low performance that
> `ExtractorEngine` and `FillerEngine` are used to get final SQL parsed
> result based on AST generated by ANTLR at present. Upon investigation, we
> would like to replace them with ANTLR visitor.
>
>
> It is scheduled as a long-term task and a big change for our 5.x release,
> and currently i am trying to do some basic work for our new branch[1].
> After the groundwork (Roughly estimated time is one week. ) is basically
> laid, we would like to welcome anyone who is interested in it to join us
> for this wonderful sharding parser.
>
>
> Please watch this thread for follow-up. What’s more, welcome your any
> comment and suggestion!
>
>
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/tree/sharding-parser-5.x
>
>
>
>
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>

Re: [DISCUSS] Remove some class members from `WhereSegment`

2020-02-16 Thread 蒋晓峰 
In previous refactor work of visitor,  I found that this segment has no
sense in parser, therefore I agree with you that to remove them to simply
our parsing module and integrated tests.

On Thu, Feb 13, 2020 at 2:44 PM Juan Pan  wrote:

> Hi everyone,
>
>
> I found  the class member `parametersCount` and
> `parameterMarkerStartIndex` of `WhereSegment .java` are written, but do not
> used or read by any other objects.
>
>
> So i plan to remove them to simply our parsing module and integrated
> tests. If i miss something, please tell me ASAP.
>
>
> Regards,
>
>
>  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

2020-02-10 Thread 蒋晓峰 
Good Job!

On Mon, Feb 10, 2020 at 8:58 PM Zhang Yonglun 
wrote:

> 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

2020-02-09 Thread 蒋晓峰 
Hi zhaojun,
   what about the pull request of
https://github.com/apache/incubator-shardingsphere/pull/3918? I thought
that this pull request is necessary to 4.0.1 version.

Thanks,
Nicholas Jiang

On Sun, Feb 9, 2020 at 3:44 PM zhaojun  wrote:

> 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

Fwd: [DISCUSS] Optimization for Sharing Encrypt IN operator

2020-02-07 Thread 蒋晓峰 
Hi Community,

Sharding encrypt module exists problem that rewrite sql is incorrect
when sql with in operator contains space and line break. I have written
document about this encrypt problem and my solution to this problem:

https://docs.google.com/document/d/1HjDjmaaEB-_eQOH6C4Cv6NxsrkAuaNFovr-oTUOvPbQ/edit

   The issue is sharding+encrypt when sql contains "\n"，sql rewrite error
for mybatis.


There are two pull request for fixing the problem above:
Fixes #4037. IN operator contains space and `\n` `\t` `\r`

Encrypt statement IN operator contains space and line break


According to previous discussion, the changes include core module
modification. Based on core module consideration, Zhang Liang provides the
suggestion:
1.Parse start index of In parent
2.Fix SQL conjunction logic

Here takes a discussion about the optimization of IN operator in
encrypt module. Welcome to join this dicussion to solve the problem.

Thanks,
Nicholas

[DISCUSS] Optimization for Sharing Encrypt IN operator

2020-02-07 Thread 蒋晓峰 
Hi Community,

Sharding encrypt module exists problem that rewrite sql is incorrect
when sql with in operator contains space and line break. I have written
document about this encrypt problem and my solution to this problem:

https://docs.google.com/document/d/1HjDjmaaEB-_eQOH6C4Cv6NxsrkAuaNFovr-oTUOvPbQ/edit

   The issue is sharding+encrypt when sql contains "\n"，sql rewrite error
for mybatis.


There are two pull request for fixing the problem above:
Fixes #4037. IN operator contains space and `\n` `\t` `\r`

Encrypt statement IN operator contains space and line break


According to previous discussion, the changes include core module
modification. Based on core module consideration, Zhang Liang provides the
suggestion:
1.Parse start index of In parent
2.Fix SQL conjunction logic

Here takes a discussion about the optimization of IN operator in
encrypt module. Welcome to join this dicussion to solve the problem.

Thanks,
Nicholas

Re: [DISCUSS] Optimization for Sharing Parser with Antlr Visitor

2020-02-07 Thread 蒋晓峰 
Hi Juan,
Sorry for the late reply. This weekend I would like to support the
change for DDLStatement.

Thanks,
Nicholas Jiang

On Fri, Feb 7, 2020 at 11:51 AM Juan Pan  wrote:

> Hi
>
>
> Provide feedback on task progress, refer to [1] to learn more. Welcome
> your any suggestion.
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-583220969
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 02/2/2020 18:04，Juan Pan wrote：
> Hi everyone,
>
>
> Thanks for your attention.
> I am glad to tell the community that this long-term task has been on the
> right way and made some progress. Please refer to [1]  for its detailed
> progress.
> Many thanks for the contributions from SteNicholas, dongzl, jingshanglu,
> tianbin1001 and beijing-penguin and your effort make this progress
> possible.
>
>
> However there are many optimization and work for community to do for this
> task, so we welcome everyone interested in it to join us!
>
>
> Hope your good health during this special Chinese new year.
>
>
> - [1]
> https://github.com/apache/incubator-shardingsphere/issues/3914#issuecomment-581108911
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>
> On 01/9/2020 14:20，Juan Pan wrote：
> Hi folks,
>
>
> It is not common practice and prone to low performance that
> `ExtractorEngine` and `FillerEngine` are used to get final SQL parsed
> result based on AST generated by ANTLR at present. Upon investigation, we
> would like to replace them with ANTLR visitor.
>
>
> It is scheduled as a long-term task and a big change for our 5.x release,
> and currently i am trying to do some basic work for our new branch[1].
> After the groundwork (Roughly estimated time is one week. ) is basically
> laid, we would like to welcome anyone who is interested in it to join us
> for this wonderful sharding parser.
>
>
> Please watch this thread for follow-up. What’s more, welcome your any
> comment and suggestion!
>
>
>
>
> [1]
> https://github.com/apache/incubator-shardingsphere/tree/sharding-parser-5.x
>
>
>
>
>
>
>  Juan Pan (Trista)
>
> Senior DBA & PPMC of Apache ShardingSphere(Incubating)
> E-mail: panj...@apache.org
>
>
>
>

Re: HA of Apache ShardingSphere(incubator) work plans

2020-02-06 Thread 蒋晓峰 
Hi, Haoran Meng:
Could you please provide the design document of "upgrade the
Orchestration module to the Governance module"? And please put the document
into confluence of wiki to let community developer for reference.

Thanks,
Nicholas Jiang

On Thu, Feb 6, 2020 at 4:18 PM Haoran Meng  wrote:

> Hello everyone, we plan to optimize Orchestration of Apache
> ShardingSphere(incubator)，
>
> and we plan to upgrade the Orchestration module to the Governance module.
>
> The goal is to package Governance as a core component of distributed
> database HA.
>
> Here are our plans:
>
>1.
>
>Sort out and redesign ConfigCenter and RegistryCenter, and separate them
>from specific domain models, so that developers can easily integrate and
>implement data access and change notification functions based on a
> certain
>technology.
>2.
>
>Consider the functions of Distributed Lock and Leaf ID Generator, keep
>or integrate third party?
>3.
>
>Provide API and SPI related to the above designs, which requires clear
>and Least Knowledge Principle.
>4.
>
>Design Metadata model, integrate with Config and Registry.
>5.
>
>Design the management of JDBC and Proxy nodes, the detection and
>reconstruction mechanism after nodes crashed.
>6.
>
>Design the elegant Refresh mechanism of Connection and the processing
>under the multi-threaded Executor. Minimize the reconstruction of all
>internal and external resource objects.
>7.
>
>Design the model and synchronization mechanism of Rules and DataSources.
>8.
>
>Spring NameSpace, Spring Boot integration.
>9.
>
>Governance module integrates with JDBC and Proxy modules to achieve HA.
>
> Everyone is welcome to actively discuss and provide comments and
> suggestions.
>

Re: [Discuss] What does ShardingSphere 4.0.0's final API look like?

2019-09-28 Thread 蒋晓峰 



On 2019/09/28 10:14:55, "zhangli...@apache.org"  wrote: 
> The scope of ShardingSphere keep expanding. Sharding is not the unique and
> core feature for ShardingSphere anymore.
> 
> So we plan to create pluggable infrastructure for database proxy and JDBC
> driver which to let users run it without any additional function, just
> transparent transmission. ShardingSphere can add more features into `EMPTY`
> infrastructure, such as sharding, master-slave, encrypt,
> distributed-transaction, orchestration and so on.
> 
> The API may look like: ShardingDataSource, MasterSlaveDataSource,
> EncryDataSource, DistributedTransactionDataSource and
> OrchestrationDataSource, the yaml and other configuration methods should
> change to this way too.
> 
> Every features are independent and can be work together which using
> composited and append-able way. We can provide SSDataSourceFacade to manage
> how to use them together.
> 
> This is one of the reason to why we do not release for 4.0.0 stable version
> soon, we want more discuss to make decision to change API before 4.0.0
> stable version release.
> 
> Any suggestions?
> 
> --
> 
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>

Re: [Discuss] What does ShardingSphere 4.0.0's final API look like?

2019-09-28 Thread 蒋晓峰 
Hi liang,
This version 4.0.0 can release before pluggable infrastructure for database 
proxy and JDBC driver.Not only database proxy and JDBC driver, other function 
features can implement with SPI way like parser.The configuration methods are 
very extensible, and this need to abstract the Datasource interface first, and 
then various DataSource implementations adapt its interface.This feature 
implementation requires a lot of work, first abstracting the interface, and 
then assigning several contributors together to complete the adaptation.

On 2019/09/28 10:14:55, "zhangli...@apache.org"  wrote: 
> The scope of ShardingSphere keep expanding. Sharding is not the unique and
> core feature for ShardingSphere anymore.
> 
> So we plan to create pluggable infrastructure for database proxy and JDBC
> driver which to let users run it without any additional function, just
> transparent transmission. ShardingSphere can add more features into `EMPTY`
> infrastructure, such as sharding, master-slave, encrypt,
> distributed-transaction, orchestration and so on.
> 
> The API may look like: ShardingDataSource, MasterSlaveDataSource,
> EncryDataSource, DistributedTransactionDataSource and
> OrchestrationDataSource, the yaml and other configuration methods should
> change to this way too.
> 
> Every features are independent and can be work together which using
> composited and append-able way. We can provide SSDataSourceFacade to manage
> how to use them together.
> 
> This is one of the reason to why we do not release for 4.0.0 stable version
> soon, we want more discuss to make decision to change API before 4.0.0
> stable version release.
> 
> Any suggestions?
> 
> --
> 
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>

Re: [Discuss] What does ShardingSphere 4.0.0's final API look like?

2019-09-28 Thread 蒋晓峰 



On 2019/09/28 10:14:55, "zhangli...@apache.org"  wrote: 
> The scope of ShardingSphere keep expanding. Sharding is not the unique and
> core feature for ShardingSphere anymore.
> 
> So we plan to create pluggable infrastructure for database proxy and JDBC
> driver which to let users run it without any additional function, just
> transparent transmission. ShardingSphere can add more features into `EMPTY`
> infrastructure, such as sharding, master-slave, encrypt,
> distributed-transaction, orchestration and so on.
> 
> The API may look like: ShardingDataSource, MasterSlaveDataSource,
> EncryDataSource, DistributedTransactionDataSource and
> OrchestrationDataSource, the yaml and other configuration methods should
> change to this way too.
> 
> Every features are independent and can be work together which using
> composited and append-able way. We can provide SSDataSourceFacade to manage
> how to use them together.
> 
> This is one of the reason to why we do not release for 4.0.0 stable version
> soon, we want more discuss to make decision to change API before 4.0.0
> stable version release.
> 
> Any suggestions?
> 
> --
> 
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>