Re:[VOTE]: Release Apache ShardingSphere (Incubating) 4.0.0-RC1 [ROUND 3]

[Sion Yang]

+1 approveChecked:[√] 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.

--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-04-13 01:57:12, "zhangli...@apache.org"  wrote:
>Hello ShardingSphere Community,
>
>This is a call for vote to release Apache ShardingSphere (Incubating)
>version 4.0.0-RC1
>
>Release notes:
>https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-d5d2dc137c82994bbaac
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/
>
>Maven 2 staging repository:
>https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
>
>Git tag for the release:
>https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1
>
>Release Commit ID:
>https://github.com/apache/incubator-shardingsphere/commit/2c1d23f9569e5cbe74074a578931c77dfa800800
>
>Keys to verify the Release Candidate:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>
>Look at here for how to verify this release candidate:
>https://shardingsphere.apache.org/community/en/contribute/release/
>
>The vote will be open for at least 72 hours or until necessary number of
>votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>
>[ ] +0 no opinion
>
>[ ] -1 disapprove with the reason
>
>Checklist for reference:
>
>[ ] Download links are valid.
>
>[ ] Checksums and PGP signatures are valid.
>
>[ ] DISCLAIMER is included.
>
>[ ] Source code artifacts have correct names matching the current release.
>
>[ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>
>[ ] All files have license headers if necessary.
>
>[ ] No compiled archives bundled in source archive.
>
>--
>
>Liang Zhang (John)
>Apache ShardingSphere & Dubbo

Re:[VOTE] Accept OpenShardingUI Donation

[Sion Yang]

+1


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-06-08 11:16:49, "Chen QingYang"  wrote:
>Dear Apache ShardingSphere Incubator Community ,
>
>After some discussions on the OpenShardingUI donation proposal, I would
>like to start a vote  on accepting OpenShardingUI into the Apache Incubator
>as ShardingSphere's sub-project.
>
>Discussion in ML
>https://lists.apache.org/thread.html/5edf7e9df370ac1ed9531232e8f240341ee87d1bad8629a165d74161@%3Cdev.shardingsphere.apache.org%3E
>https://lists.apache.org/thread.html/5cb119e4c7219c2bc0971a831d385b2c6ad1244c6fa9c20c29306d1a@%3Cdev.shardingsphere.apache.org%3E
>
>Please accept the OpenShardingUI podling into the Apache Incubator.
>
>The proposal can be found at
>https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/OpenShardingUI+Donation+Proposal.
>Here is the text of it:
>
># Abstract
>OpenShardingUI[1] is a simple and useful web administration console for
>Apache ShardingSphere Incubator[2].
>It is designed to help users more easily use ShardingSphere.
>It provides ability of registry center management, dynamic configuration
>management, database orchestration, etc.
>
># Proposal
>The goal of this proposal is to bring the existing OpenShardingUI 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 6 months.
>OpenShardingUI 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/OpenSharding/sharding-ui.
>
># 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
>it has long lacked an easy-to-use operation system for quick and easy
>configuration management and database orchestration.
>So Chen Qingyang and Wang Qi created a web administration console for
>ShardingSphere，and OpenShardingUI was born.
>
># Current status
>After we pushed OpenShardingUI in Github in an open source way, many
>companies began to integrate it into their own systems to match the use of
>ShardingSphere.
>Current open source users are mostly IT company in China, like CHINA
>TELECOM Bestpay, etc
>
># Core developer
>Chen Qingyang is an experienced open source developer and ShardingSphere
>PPMC.
>Wang Qi is an experienced open source developer.
>
># Donation source
>Github repo: https://github.com/OpenSharding/sharding-ui
>
># Source and Intellectual Property Submission Plan
>OpenShardingUI was opened in Github on 26 Nov 2018. The project major
>contributors are Chen Qingyang and Wang Qi. Chen Qingyang is
>ShardingSphere's PPMC, ICLA are submitted. Wang Qi will sign ICLA after
>OpenShardingUI is accepted into the Apache Software Foundation (ASF) as
>ShardingSphere's sub-project
>
># External Dependencies
>### Apache 2.0 licenses
>- sharding-orchestration-core 4.0.0-RC1:
>https://github.com/apache/incubator-shardingsphere
>- sharding-orchestration-reg-zookeeper-curator 4.0.0-RC1:
>https://github.com/apache/incubator-shardingsphere
>- snakeyaml 1.16: https://bitbucket.org/asomov/snakeyaml/src/default
>- commons-codec 1.11: https://github.com/apache/commons-codec
>- gson 2.7: https://github.com/google/gson
>- spring-boot-dependencies 2.0.2.RELEASE:
>https://github.com/spring-projects/spring-boot
>
>### MIT licenses
>- lombok 1.16.4: https://github.com/rzwitserloot/lombok
>- axios 0.18.0: https://github.com/axios/axios
>- element-ui 2.4.9: https://github.com/ElemeFE/element
>- js-yaml 3.12.0: https://github.com/nodeca/js-yaml
>- lodash 4.17.11: https://github.com/lodash/lodash
>- normalize.css 8.0.1: https://github.com/necolas/normalize.css
>- qs 6.6.0: https://github.com/ljharb/qs
>- vue 2.5.2: https://github.com/vuejs/vue
>- vue-i18n 8.4.0: https://github.com/kazupon/vue-i18n
>- vue-router 3.0.1: https://github.com/vuejs/vue-router
>- vuex 3.0.1: https://github.com/vuejs/vuex
>- autoprefixer 7.1.2: https://github.com/postcss/autoprefixer
>- babel-core 6.22.1:
>https://github.com/babel/babel/tree/master/packages/babel-core
>- babel-eslint 8.2.1: https://github.com/babel/babel-eslint
>- babel-helper-vue-jsx-merge-props 2.0.3:
>https://github.com/vuejs/babel-helper-vue-jsx-merge-props
>- babel-loader 7.1.1: https://github.com/babel/babel-loader
>- babel-plugin-dynamic-import-webpack 1.1.0:
>https://github.com/airbnb/babel-plugin-dynamic-import-webpack
>- babel-plugin-syntax-jsx 6.18.0:
>https://github.com/babel/babel/tree/master/packages/babel-plugin-syntax-jsx
>- babel-plugin-transform-runtime 6.22.0:
>https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-runtime
>- babel-plugin-transform-vue-jsx 3.7.0:

Re:Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2 [ROUND 2]

[Sion Yang]

+1 approve, 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-07-16 16:56:50, "zhaojun"  wrote:
>+1 approve, 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.
>
>--
>Zhao Jun
>Apache Sharding-Sphere & ServiceComb
>
>
>> On Jul 16, 2019, at 4:19 PM, zhangli...@apache.org wrote:
>> 
>> +1 approve, 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
>> 
>> 
>> Zhang Yonglun  于2019年7月15日周一 下午4:11写道：
>> 
>>> Hello ShardingSphere Community,
>>> 
>>> This is a call for vote to release Apache ShardingSphere (Incubating)
>>> version 4.0.0-RC2
>>> 
>>> Release notes:
>>> 
>>> https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e
>>> 
>>> The release candidates:
>>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/
>>> 
>>> Maven 2 staging repository:
>>> 
>>> https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
>>> 
>>> Git tag for the release:
>>> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2
>>> 
>>> Release Commit ID:
>>> 
>>> https://github.com/apache/incubator-shardingsphere/commit/5b4fa38b9237e8885c823dd92b4b42d1285c4c48
>>> 
>>> Keys to verify the Release Candidate:
>>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>>> GPG username: zhangyonglun
>>> 
>>> Look at here for how to verify this release candidate:
>>> https://shardingsphere.apache.org/community/en/contribute/release/
>>> 
>>> The vote will be open for at least 72 hours or until necessary number of
>>> votes are reached.
>>> 
>>> Please vote accordingly:
>>> 
>>> [ ] +1 approve
>>> 
>>> [ ] +0 no opinion
>>> 
>>> [ ] -1 disapprove with the reason
>>> 
>>> Checklist for reference:
>>> 
>>> [ ] Download links are valid.
>>> 
>>> [ ] Checksums and PGP signatures are valid.
>>> 
>>> [ ] DISCLAIMER is included.
>>> 
>>> [ ] Source code artifacts have correct names matching the current release.
>>> 
>>> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>>> 
>>> [ ] All files have license headers if necessary.
>>> 
>>> [ ] No compiled archives bundled in source archive.
>>> 
>>> --
>>> Zhang Yonglun
>>> Apache ShardingSphere
>>> 
>

Re:Boardcast select returns all records from all sharded databases

[Sion Yang]

Use `broadcastTables` please.
Configuration like this:
shardingRule:

tables:
other sharding table configuration
broadcastTables:
- your table


Detail see 
https://shardingsphere.apache.org/document/current/en/manual/sharding-jdbc/configuration/config-yaml/


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-07-02 03:04:15, "Eric"  wrote:
>Hi,
>
>Seems select statement without sharding key in the where clause will return
>all records from the tables from all sharded databases. Please have your
>help.
>
>For example, if two sharded database has the same table and records,
>selecting from that table without sharding key in the where clause, all
>records from the two databases are returned which are duplicated.
>
>Is there some settings I need to put into the configuration?
>
>If it's a boardcast route because not hitting sharding key, the table is
>not sharded or any reason, is there some way I can return unique records
>without using "unique" in the original source query?
>
>Regards,
>Eric Poon

Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 1]

[Sion Yang]

I've just finish a set of tests for Sharding-Proxy with MySQL protocol on this 
release.
I think there be not block issue, so we can continue to do release.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-06-27 15:54:30, "Zhang Yonglun"  wrote:
>Hello ShardingSphere Community,
>
>This is a call for the 1th round of discussion to release Apache
>ShardingSphere
>(Incubating) version 4.0.0-RC2
>
>Release notes:
>https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e
>
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/
>
>Maven 2 staging repository:
>https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
>
>
>Git tag for the release:
>https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2
>
>Release Commit ID:
>https://github.com/apache/incubator-shardingsphere/commit/7befe25afee89ab8408b8c8ed50384f1c94e2a4e
>
>
>Keys to verify the Release Candidate:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>GPG username: zhangyonglun
>
>Checklist:
>https://shardingsphere.apache.org/community/en/contribute/release/
>
>Anyone who is interested can do this acceptance test and discuss whether
>this version should be released or not.
>
>-- 
>Zhang Yonglun
>Apache ShardingSphere

Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2 [ROUND 4]

[Sion Yang]

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



--

Yi Yang(Sion)
Apache ShardingSphere



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

Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 4]

[Sion Yang]

I execute all examples. Most of examples execute successfully except encrypt in 
JPA with SpringBoot.  
The bug has marked `TODO` in example, and only affects part of encrypt.
So i think we can continue to prepare our version 4.0.0-RC2.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-08-09 18:46:33, "Zhang Yonglun"  wrote:
>Hello ShardingSphere Community,
>
>This is a call for the 4th round of discussion to release Apache
>ShardingSphere (Incubating) version 4.0.0-RC2
>
>Release notes:
>https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-08931c6025e028ee428c
>
>Git branch for the release:
>The dev branch of ShardingSphere(
>https://github.com/apache/incubator-shardingsphere.git)
>
>We have fixed all know serious issues found during the integration test. So
>the dev branch is ready for discussion.
>
>Anyone who is interested can do this acceptance test and discuss whether
>this version should be released or not.
>
>-- 
>Zhang Yonglun
>Apache ShardingSphere

Re:Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 4]

[Sion Yang]

There are another issue[1] for encrypt in 4.0.0-RC2.
Encrypt may replace table name with column so that the column in SQL become 
`column.column`.


[1] https://github.com/apache/incubator-shardingsphere/issues/2883


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-08-13 18:38:13, "Sion Yang"  wrote:
>I execute all examples. Most of examples execute successfully except encrypt 
>in JPA with SpringBoot.  
>The bug has marked `TODO` in example, and only affects part of encrypt.
>So i think we can continue to prepare our version 4.0.0-RC2.
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2019-08-09 18:46:33, "Zhang Yonglun"  wrote:
>>Hello ShardingSphere Community,
>>
>>This is a call for the 4th round of discussion to release Apache
>>ShardingSphere (Incubating) version 4.0.0-RC2
>>
>>Release notes:
>>https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-08931c6025e028ee428c
>>
>>Git branch for the release:
>>The dev branch of ShardingSphere(
>>https://github.com/apache/incubator-shardingsphere.git)
>>
>>We have fixed all know serious issues found during the integration test. So
>>the dev branch is ready for discussion.
>>
>>Anyone who is interested can do this acceptance test and discuss whether
>>this version should be released or not.
>>
>>-- 
>>Zhang Yonglun
>>Apache ShardingSphere

Re:Re:Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 4]

[Sion Yang]

These two issues can reproduce in apache/incubator-shardingsphere-example[1].
And I also open issue in GitHub[2][3].


[1] https://github.com/apache/incubator-shardingsphere-example
[2] https://github.com/apache/incubator-shardingsphere/issues/2883
[3] https://github.com/apache/incubator-shardingsphere/issues/2884


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-08-16 17:09:48, "Sion Yang"  wrote:
>There are another issue[1] for encrypt in 4.0.0-RC2.
>Encrypt may replace table name with column so that the column in SQL become 
>`column.column`.
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/2883
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2019-08-13 18:38:13, "Sion Yang"  wrote:
>>I execute all examples. Most of examples execute successfully except encrypt 
>>in JPA with SpringBoot.  
>>The bug has marked `TODO` in example, and only affects part of encrypt.
>>So i think we can continue to prepare our version 4.0.0-RC2.
>>
>>
>>--
>>
>>Yi Yang(Sion)
>>Apache ShardingSphere
>>
>>
>>
>>At 2019-08-09 18:46:33, "Zhang Yonglun"  wrote:
>>>Hello ShardingSphere Community,
>>>
>>>This is a call for the 4th round of discussion to release Apache
>>>ShardingSphere (Incubating) version 4.0.0-RC2
>>>
>>>Release notes:
>>>https://github.com/apache/incubator-shardingsphere/releases/edit/untagged-08931c6025e028ee428c
>>>
>>>Git branch for the release:
>>>The dev branch of ShardingSphere(
>>>https://github.com/apache/incubator-shardingsphere.git)
>>>
>>>We have fixed all know serious issues found during the integration test. So
>>>the dev branch is ready for discussion.
>>>
>>>Anyone who is interested can do this acceptance test and discuss whether
>>>this version should be released or not.
>>>
>>>-- 
>>>Zhang Yonglun
>>>Apache ShardingSphere

Re:Re: [DISCUSS] Do we have to resolve issue #2884 in 4.0.0-RC2

[Sion Yang]

I think so, DML for encrypt can work well now. 
Users can create table by themselves instead of by JPA to solve the problem. 
We can complete DDL for encrypt at next release.


--

Yi Yang(Sion)
Apache ShardingSphere



在 2019-08-21 12:08:42，"zhangli...@apache.org"  写道：
>Because it is not a blocking issue, we don't do ddl for data mask now,
>(data mask only for DML), so I prefer leave this issue for now, we can fix
>this issue at next release.
>
>--
>
>Liang Zhang (John)
>Apache ShardingSphere & Dubbo
>
>
>juan pan  于2019年8月21日周三 上午11:09写道：
>
>> Ok, so that we can have more time to take care of it, and yesterday one
>> volunteer also showed interest on it. So i think fixing it in our next
>> version is better.
>>
>> -
>> Juan Pan (Trista)
>> Apache ShardingSphere
>>
>>
>> Zhang Yonglun  于2019年8月21日周三 上午10:58写道：
>>
>> > Hi,
>> >
>> > I think this issue (
>> > https://github.com/apache/incubator-shardingsphere/issues/2884) is not a
>> > serious or block bug. What's your opinion on this? I suggest to resolve
>> > this problem in the next release.
>> >
>> > --
>> > Zhang Yonglun
>> > Apache ShardingSphere
>> >
>>

Re:How to use sharding jdbc with hint(如何在sharding jdbc中使用hint)

[Sion Yang]

Hi,


It looks like you don't add shardingValue to `HintManager`. 
As the document show, you should add your shardingValue to `HintManager` 
before your execute your SQL. 


These codes come from document:
```
// Sharding database and table with using hintManager.
String sql = "SELECT * FROM t_order";
try (HintManager hintManager = HintManager.getInstance();
 Connection conn = dataSource.getConnection();
 PreparedStatement preparedStatement = conn.prepareStatement(sql)) {
hintManager.addDatabaseShardingValue("t_order", 1);
hintManager.addTableShardingValue("t_order", 2);
try (ResultSet rs = preparedStatement.executeQuery()) {
while (rs.next()) {
// ...
}
}
}


// Sharding database without sharding table and routing to only one database 
with using hintManger.
String sql = "SELECT * FROM t_order";
try (HintManager hintManager = HintManager.getInstance();
 Connection conn = dataSource.getConnection();
 PreparedStatement preparedStatement = conn.prepareStatement(sql)) {
hintManager.setDatabaseShardingValue(3);
try (ResultSet rs = preparedStatement.executeQuery()) {
while (rs.next()) {
// ...
}
}
}
```


> HintManager hintManager = HintManager.getInstance();
this code should be used to get `HintManager` in your SQL execute Thread,
and add your shardingValue before you execute SQLs.


--

Yi Yang(Sion)
Apache ShardingSphere



在 2019-08-30 15:55:20，"悟饭"  写道：
>hi，English is not my first language，if you don’t  understand which I talk 
>about, please mail me. 
>
>my config：
>
>Shardjdbc version: 4.0.0-RC2
>Springboot version: 2.1.7
>DB:mysql5.7
>Jdbc driver:   com.mysql.jdbc.Driver
>Db connection pool:com.alibaba.druid.pool.DruidDataSource
>
>When I use hint to sharing my table, it looks like not work.please show me 
>which one I was mistake. 
>
>When I insert one object to mysql, it will insert 12 records in every sharding 
>table, and, when query by createdAt it also query all tables don’t use the 
>sharing algorithm.
>
>The official demo link was 
>failure.（https://github.com/apache/incubator-shardingsphere-example/tree/dev/sharding-jdbc-example/hint-example
> 
>）
>
>Thanks all.
>
>
>
>Config in application.yml:
>
>spring:
>  application.name: demo
>  shardingsphere:
>datasource:
>  ds0:
>driver-class-name: com.mysql.jdbc.Driver
>type: com.alibaba.druid.pool.DruidDataSource
>url: jdbc:mysql://$ {DB_URL}:3306/demo
>username: ${DB_USERNAME}
>password: ${DB_PASS}
>  names: ds0
>sharding:
>  binding-tables: t_order
>  default-database-strategy:
>hint:
>  algorithmClassName: com.demo.config.MyShardingAlgorithm
>  tables:
>illegal_result:
>  actual-data-nodes: ds0.t_order$->{1..9}, ds0.t_order$->{10..12}
>  key-generator:
>column: id
>type: SNOWFLAKE
>  table-strategy:
>hint:
>  algorithmClassName: com.demo.config.MyShardingAlgorithm
>props:
>  sql:
>show: true
>
>MyShardAlgorithm.java
>public class MyShardingAlgorithm implements HintShardingAlgorithm {
>  private static final String ORDER_TABLE = "illegal_result";
>
>  @Override
>  public Collection doSharding(Collection collection, 
> HintShardingValue shardingValue) {
>
>List list = Lists.newArrayList(shardingValue.getValues());
>List actualTable = Lists.newArrayList();
>
>// 页面上的查询条件会以json的方式传到shardingValue变量中
>String json = list.get(0);
>QueryCondition condition = JSON.parseObject(json, 
> IllegalResultQueryCondition.class);
>// if no createdat, quarry all
>if (StringUtils.isEmpty(condition.getCreatedAt())) {
>  // 所有的分表
>  for (int i = 1; i < 13; i++) {
>String tabIndex = i < 10 ? "0".concat(String.valueOf(i)) : 
> String.valueOf(i);
>actualTable.add(ORDER_TABLE.concat(tabIndex));
>  }
>} else {
>  // if has createdAt, only query month table which createAt in. 
> ShardingUtils.getDateIndex will get month from createdAt
>  String tableSuffix = 
> ShardingUtils.getDateIndex(condition.getCreatedAt());
>  actualTable.add(ORDER_TABLE.concat(tableSuffix));
>}
>
>return actualTable;
>  }
>
>}
>
>Hi,英文水平有限，抱歉。
>我在使用shardinng jdbc进行分表实践的时候，使用hint策略，并根据文档进行了配置，发现并没有生效。官方给出的demo链接已经失效（404）。
>根据官方文档（https://shardingsphere.apache.org/document/current/cn/manual/sharding-jdbc/usage/hint/
> 
>）我实现了自己的路由算法，但debug时，并没有执行该方法
>另外对于文档中提到的
>获取HintManager
>
>
>HintManager 

Re:Would sharded database has data integrity issue when a shard fail

[Sion Yang]

Hi,


There are three kinds of distributed transaction in ShardingSphere, local, two 
phase commit and BASE.
Default is local transaction.


For local transaction, if the SQL execute failed before commit, all sharding 
data node will be rollback.
If failed in commit, the other sharding data node will not be rollback.


Detail information can see the document 
https://shardingsphere.apache.org/document/current/en/features/transaction/


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-09-09 06:31:23, "Eric"  wrote:
>Hi,
>
>If a shard fail on a transaction, would the transactions on the other
>shards rolled back together?
>
>Let say I have 100 payments being updated in one sql statement (e.g. update
>payment set remark = 'xxx' where customer = 'yyy'), the records are
>distributed on several shards. A shard failed to update the records. Would
>other shards roll back the updates?
>
>Best Regards,
>Eric Poon

Re:Re: Would sharded database has data integrity issue when a shard fail

[Sion Yang]

Do you use sharding-proxy?


If you use sharding-proxy, you can send `sctl:set transaction_type=` before you 
begin transaction.
you also can get information in 
https://shardingsphere.apache.org/document/current/en/manual/sharding-proxy/usage/


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-09-09 10:28:42, "Eric"  wrote:
>Hi Sion,
>
>Thank you. The document uses TransactionTypeHolder to modify transaction
>type in Java. Is it possible to set it in proxy yaml file?
>
>Regards,
>Eric Poon
>
>On Mon, Sep 9, 2019 at 8:45 AM Sion Yang  wrote:
>
>> Hi,
>>
>>
>> There are three kinds of distributed transaction in ShardingSphere, local,
>> two phase commit and BASE.
>> Default is local transaction.
>>
>>
>> For local transaction, if the SQL execute failed before commit, all
>> sharding data node will be rollback.
>> If failed in commit, the other sharding data node will not be rollback.
>>
>>
>> Detail information can see the document
>> https://shardingsphere.apache.org/document/current/en/features/transaction/
>>
>>
>> --
>>
>> Yi Yang(Sion)
>> Apache ShardingSphere
>>
>>
>>
>> At 2019-09-09 06:31:23, "Eric"  wrote:
>> >Hi,
>> >
>> >If a shard fail on a transaction, would the transactions on the other
>> >shards rolled back together?
>> >
>> >Let say I have 100 payments being updated in one sql statement (e.g.
>> update
>> >payment set remark = 'xxx' where customer = 'yyy'), the records are
>> >distributed on several shards. A shard failed to update the records. Would
>> >other shards roll back the updates?
>> >
>> >Best Regards,
>> >Eric Poon
>>

Re:Re: Re: Would sharded database has data integrity issue when a shard fail

[Sion Yang]

Hi Eric,


SCTL is same as normal SQL, it can be send by the connection and statement of 
sharding-proxy.
```
// datasource : datasource to sharding-proxy


Connection connection = datasource.getConnection();
Statement statement = connection.createStatement()
statement.execute("sctl:set transaction_type=local/xa/base")
connection.begin();
...(execute your business)
connection.commit();


```


--

Yi Yang(Sion)
Apache ShardingSphere
 

At 2019-09-09 22:31:29, "Eric"  wrote:
>Hi Sion,
>
>That's very helpful but I don't know how to send the SCTL to the proxy. Is
>it a custom Java program, command prompt, or inside a configuration file?
>
>Please help.
>
>Best Regards,
>Eric Poon
>
>On Mon, Sep 9, 2019 at 10:52 AM Sion Yang  wrote:
>
>> Do you use sharding-proxy?
>>
>>
>> If you use sharding-proxy, you can send `sctl:set transaction_type=`
>> before you begin transaction.
>> you also can get information in
>> https://shardingsphere.apache.org/document/current/en/manual/sharding-proxy/usage/
>>
>>
>> --
>>
>> Yi Yang(Sion)
>> Apache ShardingSphere
>>
>>
>>
>> At 2019-09-09 10:28:42, "Eric"  wrote:
>> >Hi Sion,
>> >
>> >Thank you. The document uses TransactionTypeHolder to modify transaction
>> >type in Java. Is it possible to set it in proxy yaml file?
>> >
>> >Regards,
>> >Eric Poon
>> >
>> >On Mon, Sep 9, 2019 at 8:45 AM Sion Yang  wrote:
>> >
>> >> Hi,
>> >>
>> >>
>> >> There are three kinds of distributed transaction in ShardingSphere,
>> local,
>> >> two phase commit and BASE.
>> >> Default is local transaction.
>> >>
>> >>
>> >> For local transaction, if the SQL execute failed before commit, all
>> >> sharding data node will be rollback.
>> >> If failed in commit, the other sharding data node will not be rollback.
>> >>
>> >>
>> >> Detail information can see the document
>> >>
>> https://shardingsphere.apache.org/document/current/en/features/transaction/
>> >>
>> >>
>> >> --
>> >>
>> >> Yi Yang(Sion)
>> >> Apache ShardingSphere
>> >>
>> >>
>> >>
>> >> At 2019-09-09 06:31:23, "Eric"  wrote:
>> >> >Hi,
>> >> >
>> >> >If a shard fail on a transaction, would the transactions on the other
>> >> >shards rolled back together?
>> >> >
>> >> >Let say I have 100 payments being updated in one sql statement (e.g.
>> >> update
>> >> >payment set remark = 'xxx' where customer = 'yyy'), the records are
>> >> >distributed on several shards. A shard failed to update the records.
>> Would
>> >> >other shards roll back the updates?
>> >> >
>> >> >Best Regards,
>> >> >Eric Poon
>> >>
>>

Re:[DISCUSS] Apache ShardingSphere (Incubating) 4.0.0-RC2 release [ROUND 3]

[Sion Yang]

I notice a bug about distinct SQL, and create a new issue #2777.
I think we should fix it in RC-2.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-07-24 17:36:34, "Zhang Yonglun"  wrote:
>Hello ShardingSphere Community,
>
>This is a call for the 3rd round of discussion to release Apache
>ShardingSphere (Incubating) version 4.0.0-RC2
>
>Release notes:
>https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/
>
>Maven 2 staging repository:
>https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
>
>Git tag for the release:
>https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2
>
>Release Commit ID:
>https://github.com/apache/incubator-shardingsphere/commit/1014b760ec22419441fae1c26df36f813cf3026d
>
>Keys to verify the Release Candidate:
>https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>GPG username: zhangyonglun
>
>Checklist:
>https://shardingsphere.apache.org/community/en/contribute/release/
>
>Anyone who is interested can do this acceptance test and discuss whether
>this version should be released or not.
>
>-- 
>Zhang Yonglun
>Apache ShardingSphere

Re:How to apply sharding on all tables globally by using proxy

[Sion Yang]

Hi Eric Poon,


ShardingSphere requires users to configure which tables need to be shard 
currently. 
If there are no sharding-rule for sharding tables, ShardingSphere will use 
default-datasource
to execute it. So it should not work with dynamic table names for now.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-07-20 05:21:10, "Eric"  wrote:
>Hi,
>
>I am trying to apply sharding on all tables on the same key column exists
>on all tables. The objective is evenly distribute the records on several
>database instances. For example, even no. records on one server. After
>trying around several hours, seems it's not possible to define database
>sharding strategy bases on table column without table name nor by using
>wildcard table name in yaml. I need it because the tables are dynamically
>generated which I don't know the table names in advance. Please give me
>some hints if someone knows hot to define global database sharding
>strategy on all tables by using a key column?
>
>Besides, I tried that the engine will randomly route the query to the
>datasources if no sharding rule defined in yaml. Is it possible to
>broadcast the query to all datasources if no sharding rule find? I can't
>use broadcastTables for the same reason which tables are dynamically
>generated.
>
>Very appreciate for your help.
>
>Regards,
>Eric Poon

Re:回复：config rules to exclude some unnecessary code for unit codecoverage?

[Sion Yang]

Hi, sluk3r.


For single method such as set/get method, we use Lombok to generate. These code 
can miss unit test.
But other methods should be full covered, if no particular reasons.


For the method you print out. I think it should have a unit test, even use 
Mockito backendDataSource.


In community document[1], you can see the `Covenant Unit Test of Conduct`


[1] https://shardingsphere.apache.org/community/en/contribute/code-conduct/


--

Yi Yang(Sion)
Apache ShardingSphere



在 2019-09-27 09:25:49，"王喜春"  写道：
>Hi, Sion Yang: 
>
>
>the method's whole implementation is:
>
>
>public Map getDataSources() {
>return backendDataSource.getDataSourceParameters();
>}
>there is just a single return statement, intuitively, I think there is little 
>necessary to unit test this method. Or this type of problem has been 
>discussed, and agreement has been achieved?  give me a point, pls.
>Tks
>
>
>
>
>-- 原始邮件 --
>发件人: "Sion Yang";
>发送时间: 2019年9月27日(星期五) 上午8:51
>收件人: "dev";
>
>主题: Re:config rules to exclude some unnecessary code for unit codecoverage?
>
>
>
>Hi, sluk3r.
>
>
>How to judge these codes are unnecessary or little necessary?
>
>
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>At 2019-09-27 05:40:16, "王喜春"  wrote:
>
>Hi,   for example, the code shown in the following pic, method of 
>getDataSources return "backendDataSource.getDataSourceParameters()" directly. 
>the full url is : 
>https://coveralls.io/builds/25937232/source?filename=sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/LogicSchema.java
>
>
>
>
>it seems that there is little necessary for some code. 
>
>
>So I'd like to know, is there some standard for unit code coverage rate? if 
>so, has this coverage rate been configured into some file?
>
>
>
>
>Tks.

Re:config rules to exclude some unnecessary code for unit code coverage?

[Sion Yang]

Hi, sluk3r.


How to judge these codes are unnecessary or little necessary?




--

Yi Yang(Sion)
Apache ShardingSphere


At 2019-09-27 05:40:16, "王喜春"  wrote:

Hi,   for example, the code shown in the following pic, method of 
getDataSources return "backendDataSource.getDataSourceParameters()" directly. 
the full url is : 
https://coveralls.io/builds/25937232/source?filename=sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/LogicSchema.java




it seems that there is little necessary for some code. 


So I'd like to know, is there some standard for unit code coverage rate? if so, 
has this coverage rate been configured into some file?




Tks.

Re:[Proposal] ShardingScaling donation

[Sion Yang]

Proposal has some update.


The newest version can be view in 
https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-09 09:06:09, "Sion Yang"  wrote:
>
>
>## Abstract
>
>
>ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere 
>Incubator[2].
>
>
>It is designed to help users migrate data from origin database to 
>ShardingSphere or scale out  ShardingSphere data node more easily.
>
>
>It provides ability of migrant data, scaling out data nodes, etc.
>
>
>## Proposal
>
>
>The goal of this proposal is to bring the existing ShardingScaling codebase 
>and existing developers and community into the Apache Software Foundation 
>(ASF) as ShardingSphere's sub-project.
>
>
>This project started in Open Source on Github nearly 2 months.
>
>
>ShardingScaling is submitting this proposal to donate it to the Apache 
>ShardingSphere Incubator under the Apache License, Version 2.0, in order to 
>provide a visual management tool for ShardingSphere.
>
>
>These artifacts are currently available on GitHub at 
>[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>
>
>## Background
>
>
>ShardingSphere is an ecosystem of transparent distributed database middleware, 
>focusing on data sharding, distributed transaction and database orchestration. 
>It is also widely adopted by many companies and organizations as a solution to 
>process their massive amounts of data. 
>
>
>But users have long lacked an easy-to-use way to migrate their data from 
>origin database when they first started using ShardingSphere.
>Moreover, users have also lacked easy-to-use ways to expand data nodes when 
>they use ShardingSphere for a while.
>
>
>So Wen OuYang created a scaling out component for ShardingSphere -- 
>ShardingScaling.
>
>
>## Current status
>
>
>After we pushed ShardingScaling in Github in an open source way, many users 
>and developers have shown strong intentions to this. Yi Yang and ZongLei Dong 
>have contributed many features and codes.
>
>
>Current, ShardingScaling has implemented basic data migration and scaling out 
>data nodes feature.
>
>
>## Core developer
>
>
>Wen OuYang is an experienced open source developer.
>Yi Yang is an experienced open source developer and ShardingSphere PPMC.
>ZongLei Dong is an experienced open source developer.
>
>
>## Donation source
>
>
>Github repo: 
>[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>
>
>## Source and Intellectual Property Submission Plan
>
>
>ShardingScaling was opened in Github on 18 Sep 2019. The project major 
>contributors are Wen OuYang, Yi Yang and ZongLei Dong. Yi Yang is 
>ShardingSphere's PPMC, ICLA are submitted. Wen OuYang and ZongLei Dong will 
>sign ICLA after ShardingScaling is accepted into the Apache Software 
>Foundation (ASF) as ShardingSphere's sub-project.
>
>
>## External Dependencies
>
>
>### Apache 2.0 licenses
>
>
>- sharding-core-common 4.0.0-RC2: 
>[https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere)
>- snakeyaml 1.16: 
>[https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default)
>- guava 18.0: 
>[https://github.com/google/guava](https://github.com/google/guava)
>- netty-all 4.1.16.Final: 
>[https://github.com/netty/netty](https://github.com/netty/netty)
>- commons-dbcp2 2.7.0: 
>[https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp)
>- commons-cli 1.4: 
>[https://github.com/apache/commons-cli](https://github.com/apache/commons-cli)
>- log4j 1.2.17: 
>[https://github.com/apache/log4j](https://github.com/apache/log4j)
>- gson 2.8.6: [https://github.com/google/gson](https://github.com/google/gson)
>
>
>
>
>### MIT licenses
>
>
>- slf4j-api 1.7.28: 
>[https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j)
>- slf4j-log4j12 1.7.28: 
>[https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j)
>- lombok 1.18.4: 
>[https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok)
>- mockito-core 2.7.21(scope test): 
>[https://github.com/mockito/mockito](https://github.com/mockito/mockito)
>- mockito-inline 2.7.21(scope test): 
>[https://github.com/mockito/mockito](https://github.com/mockito/mockito)
>
>
>### EPL 1.0 licenses
>
>
>- junit 4.12(scope test): 
>[https://github.com/junit-team/junit4](https://github.com/junit-team/junit4)
>
>
>### BSD License
>
>
>- hamcrest

Re:Re: Re: Re: Re: [Proposal] ShardingScaling donation

[Sion Yang]

Sorry, because I think the wiki link is not the content of proposal in this 
time.


Do you mean the wiki link should be shown up in proposal mail?


BTW, What title should the next post of the proposal use? Round 2? version 2?


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-09 22:03:34, "Sheng Wu"  wrote:
>My point is, this WIKI link is not showing up in the proposal page.
>
>Sheng Wu 吴晟
>
>Apache SkyWalking
>Apache Incubator
>Apache ShardingSphere, ECharts, DolphinScheduler podlings
>Zipkin
>Twitter, wusheng1108
>
>
>Sion Yang  于2019年11月9日周六 下午9:43写道：
>
>> I will update the latest version of the proposal in wiki[1].
>> And also post here again.
>>
>>
>> Or should I publish it in other ways?
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal
>>
>>
>> --
>>
>> Yi Yang(Sion)
>> Apache ShardingSphere
>>
>>
>>
>> At 2019-11-09 21:35:44, "Sheng Wu"  wrote:
>> >Where is the latest version of the proposal? Or are you going to post here
>> >again?
>> >
>> >Sheng Wu 吴晟
>> >
>> >Apache SkyWalking
>> >Apache Incubator
>> >Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> >Zipkin
>> >Twitter, wusheng1108
>> >
>> >
>> >Sion Yang  于2019年11月9日周六 下午9:32写道：
>> >
>> >> Yes, They will become committer.
>> >> I will add some description in `Initial Committers`
>> >>
>> >>
>> >> --
>> >>
>> >> Yi Yang(Sion)
>> >> Apache ShardingSphere
>> >>
>> >>
>> >>
>> >> At 2019-11-09 21:03:39, "Sheng Wu"  wrote:
>> >> >Yes. But as PPMC has been set up, are they willing to (if PPMC vote to
>> >> >accept) join as PPMC?
>> >> >
>> >> >Sheng Wu 吴晟
>> >> >
>> >> >Apache SkyWalking
>> >> >Apache Incubator
>> >> >Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> >> >Zipkin
>> >> >Twitter, wusheng1108
>> >> >
>> >> >
>> >> >Sion Yang  于2019年11月9日周六 下午8:58写道：
>> >> >
>> >> >> I describe the roles in `Core developer` part, so should I add these
>> >> >> describe to `Initial Committers`?
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> Yi Yang(Sion)
>> >> >> Apache ShardingSphere
>> >> >>
>> >> >>
>> >> >>
>> >> >> At 2019-11-09 20:53:29, "Sheng Wu" 
>> wrote:
>> >> >> >A thing missing in the proposal, there are three core developers for
>> >> the
>> >> >> >new component(subproject).
>> >> >> >What are the roles for them? PPMC member too?
>> >> >> >I hope they will be because, from my understanding, the core team
>> will
>> >> >> lead
>> >> >> >the subproject and work with existing PPMC
>> >> >> >
>> >> >> >Sheng Wu 吴晟
>> >> >> >
>> >> >> >Apache SkyWalking
>> >> >> >Apache Incubator
>> >> >> >Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> >> >> >Zipkin
>> >> >> >Twitter, wusheng1108
>> >> >> >
>> >> >> >
>> >> >> >Sion Yang  于2019年11月9日周六 上午9:06写道：
>> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >> ## 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.
>> >> >> >>
>> >> >> >>

Re:Add email signature

[Sion Yang]

Done




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-14 12:05:56, "zhangli...@apache.org"  wrote:
>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

Move ShardingScaling project to apache-incubator/shardingsphere repo

[Sion Yang]

Dear Apache ShardingSphere Incubator Community,

Accept ShardingScaling Donation vote has passed.
ML is 
https://lists.apache.org/thread.html/f7cf7f6d0d503080511f9c3bdc6bda25db8aad0cce2b03d2338484d2@%3Cdev.shardingsphere.apache.org%3E
 Now, Initial committers' icla files has submitted to secret...@apache.org, and 
waiting for reply.
After replying, We will move ShardingScaling project to 
apache-incubator/shardingsphere repo as a sub-project.
--

Yi Yang(Sion)
Apache ShardingSphere

Re:[VOTE] Accept ShardingScaling Donation ROUND2

[Sion Yang]

Dear Apache ShardingSphere Incubator Community ,72 hours has passed and the 
vote to Accept ShardingScaling Donation has passed.


7 PPMC member +1 votes:


Willem Jiang (mentor)
Sheng Wu
Zhang Yonglun
Liang Zhang
Juan Pan
Zhao Jun
Chen QingYang




3 community +1 vote:


Ya Li (committer)
sunbufu (committer)
Zonglei Dong


No 0 or -1 votes


Thank you everyone for taking the time to review the proposal and help us. 


--

Yi Yang(Sion)
Apache ShardingSphere



在 2019-11-16 22:11:53，"Zonglei Dong" <598363...@qq.com> 写道：
>That sounds great.
>
>
>+1
>
>
>Zonglei Dong
>Apache ShardingSphere
>
>
>------原始邮件--
>发件人:"Sion Yang"发送时间:2019年11月13日(星期三) 上午9:57
>收件人:"dev"
>主题:[VOTE] Accept ShardingScaling Donation ROUND2
>
>
>
>Dear Apache ShardingSphere Incubator Community ,
>
>
>With the help and effort of our community, the previous issues were fixed 
>already. 
>I am glad to invite everyone to start a vote on accepting ShardingScaling into 
>the Apache Incubator as ShardingSphere's sub-project ROUND 2.
>
>
>Discussion in ML
>https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%3Cdev.shardingsphere.apache.org%3E
>https://lists.apache.org/thread.html/a1ef4b44abe8f11273983e69c12becda12302aee852f7569c99a34d1@%3Cdev.shardingsphere.apache.org%3E
>
>
>Please accept the ShardingScaling podling into the Apache Incubator.
>
>
>The proposal can be found at
>https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal
>Here is the text of it:
>
>
>## Abstract
>
>
>ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere 
>Incubator[2].
>It is designed to help users migrate data from origin database to 
>ShardingSphere or scale out ShardingSphere data node more easily.
>It provides ability of migrant data, scaling out data nodes, etc.
>
>
>## Proposal
>
>
>The goal of this proposal is to bring the existing ShardingScaling codebase 
>and existing developers and community into the Apache Software Foundation 
>(ASF) as ShardingSphere's sub-project.
>This project started in Open Source on Github nearly 2 months.
>ShardingScaling is submitting this proposal to donate it to the Apache 
>ShardingSphere Incubator under the Apache License, Version 2.0, in order to 
>provide a visual management tool for ShardingSphere.
>These artifacts are currently available on GitHub at 
>[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>
>
>## Background
>
>
>ShardingSphere is an ecosystem of transparent distributed database middleware, 
>focusing on data sharding, distributed transaction and database orchestration. 
>It is also widely adopted by many companies and organizations as a solution to 
>process their massive amounts of data. 
>But users have long lacked an easy-to-use way to migrate their data from 
>origin database when they first started using ShardingSphere.
>Moreover, users have also lacked easy-to-use ways to expand data nodes when 
>they use ShardingSphere for a while.
>So Wen OuYang created a scaling out component for ShardingSphere -- 
>ShardingScaling.
>
>
>## Current status
>
>
>After we pushed ShardingScaling in Github in an open source way, many users 
>and developers have shown strong intentions to this. Yi Yang, ZongLei Dong and 
>ssxlulu have contributed many features and codes.
>Current, ShardingScaling has implemented basic data migration and scaling out 
>data nodes feature.
>
>
>## Core developer
>
>
>Wen OuYang is an experienced open source developer.
>Yi Yang is an experienced open source developer and ShardingSphere PPMC.
>
>
>## Donation source
>
>
>Github repo: 
>[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>
>
>## Source and Intellectual Property Submission Plan
>
>
>ShardingScaling was opened in Github on 18 Sep 2019. The project major 
>contributors are Wen OuYang, Yi Yang.
>Yi Yang is ShardingSphere's PPMC, ICLA are submitted. 
>Wen OuYang will sign ICLA and become Apache committer if vote be accepted 
>after ShardingScaling is accepted into the Apache Software Foundation (ASF) as 
>ShardingSphere's sub-project. 
>
>
>## External Dependencies
>
>
>### Apache 2.0 licenses
>
>
>- sharding-core-common 4.0.0-RC2: 
>[https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere)
>- snakeyaml 1.16: 
>[https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default)
>- guava 18.0: 
>[https://github.com/google/guava](ht

Re:Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4

[Sion Yang]

Hi Craig,


I generally compared the KEYS, it is the same as My local KEYS which I used to 
check 4.0.0-RC3.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-18 09:02:30, "Craig Russell"  wrote:
>I'm having trouble downloading the public key from the KEYS file.
>
>Does this KEYS file look right?
>
>Craig
>
>gpg --verify apache-shardingsphere-incubating-4.0.0-RC3-src.zip.asc
>gpg: assuming signed data in 
>'apache-shardingsphere-incubating-4.0.0-RC3-src.zip'
>gpg: Signature made Sun Nov 10 22:43:40 2019 PST using RSA key ID C8ADAD3A
>gpg: requesting key C8ADAD3A from https server keyserver.pgp.com
>gpgkeys: no key data found for https://keyserver.pgp.com/
>gpg: no valid OpenPGP data found.
>gpg: Total number processed: 0
>gpg: keyserver communications error: Not found
>gpg: keyserver communications error: Bad public key
>gpg: Can't check signature: No public key
>
>[MacBook-Pro-10:~/Downloads] clr% gpg --recv-keys < KEYS-2.txt 
>
>[MacBook-Pro-10:~/Downloads] clr% cat KEYS-2.txt 
>-BEGIN PGP PUBLIC KEY BLOCK-
>Version: GnuPG v1
>
>mQINBFyR/WgBEACuVDJ2aFMc+GvOcvBA2CpgIM5AwWo3ES2WxcWuNoBHugZvtmQ0
>Rhq0HigPcXD7F7J6Xh6PCs80EJxvbczQ16wi9597s1rzHbHFxueX8GKNtVyg7+NG
>/INzhDEEvaVE0ChxOGpSgZ8vnGZe5ERbLaW9e+onFvah5/poWiHKUJAlsvbgV4tB
>mmBCxIeTjdxHsdCFQYKpK1MNToTvSvgLZBIcNZ1OTTQMRFRDkoEfU0HR19naqHtW
>Mv87as4nxlnI4Du85tYdv6DbzL7qqFUNWUh+SROCdzReyWZiVrHzaP+zywtCnbjO
>/ddVo+lnMEesoFEdVnhRqCrtpYJuvSeIt+YkojCJtL+hooqgDcmXxlwRKOftY5ic
>ISXnriT8OE1cuUi8ghyl9YefZmjlyz+S7kCNJV81ZCi1/Uxan+yXxx4mxRn3fL61
>hm51NPEghA+plWLLXylRFlRXYuwnUvOIMk1p5gx7Il3xfmtQ+cLC2dclN85viaaC
>avbMUQDEp1qGn6K/tKIZSF+CAViCCNg2ZgHxgimLNFkvK6TfUsvBNj/oPC18+H4+
>l6+0Ub8TXb9XzRL2CcJ/I6uuifkABOuAPE2ObK2+K/yL5sQX2/qZuZotClHHWBqE
>idwChmt52ygbLwiOxQGcy6Rbv3A72WCZmbW+7f7i7iRE3x8w5HAjdDYbpwARAQAB
>tDhaaGFuZyBMaWFuZyAoYXBhY2hlIHJlbGVhc2UgYXdzKSA8emhhbmdsaWFuZ0Bh
>cGFjaGUub3JnPokCOAQTAQIAIgUCXJH9aAIbAwYLCQgHAwIGFQgCCQoLBBYCAwEC
>HgECF4AACgkQWfbgE3AOYGVdMg//W+DeSXux1j7uTfpgZ/NpBL/GDQPmxDVfredC
>xBuFtyGhX4HszPHXaSHtBZ69PcfjEPXM0Cs3+U+FR6Idkh4dorxwt+vcgD1PIInm
>4wQaT6WGwbWboBuYpNqd833lAkykz0J881JtoGSPLA2llV/edOYlHOGTqV+Hbyym
>o136xlp8BcjhiKFK8j8a1ayUN7OOijTVFVZVpjLXw5zekqaPjYz7BOVvYeNu/27F
>+sUWszEGzrrC0TsM1pm48fGVClVy4x9UX9uMYjuWUL1sSepOfE8JMvDo2F4JyePw
>yS5KCqM5/hSSAh2NzlhgsBi997idNaKobCyQhbmCBgWW27KiOPMEmpk7hOCw5piT
>cVznTwlLAip4Jm7X2feEltlSWIrgPmuEliLdEPzTaNz6DLHaLRApvv1vmgcg42cn
>sckVq4zlXO7Ia3xP3H7gxxtM4i4MdkThbVF+iUd8wWmUOdA0iWg5eyrSoxfDJ2kE
>K68vZIxwKvEiXG7Eei2UNRka7/CzSj/rH8IIgcSV2bvxin/c/01/xf0dJj7vUSqF
>MNXkDkij2U2kX5r27bPZLQXqIqigga/ytqxWluvTIitXaiXgY2vEqWd/AMWYY07Y
>ZdX0fXoJIvLXndi4Y2M1YWCsB9T4gqzr2PP55c7/L2lrxa6gYK1Tg9vY20GhmdSh
>WbF24c65Ag0EXJH9aAEQANhKpqL/X6w32ud4/Y4COZtnfn7W8tDwNl5v37aez98w
>jm+WK+/QukKno0wlcSdAhKwg5vTJUiDqRse5Uo8auLVInFCHOyYknpE6bbiz/b8k
>NmXKGYsM3UGLDVuoBDXqH0ThFCEAiNCud+bcuOspIbLiYLWeI7732C3lbXUZJnsR
>XgybO4+SBYlB4lm9XfcdSFBss9mdLikqJsLAkB+2nRBZKcvamJqML3pjAr/Ps7Te
>gW7KvPedPHY/0CV1iqSTPB5KE1WelYm6hOmjL8MfnlXna8rgO/9Oh2D2pKydYbhs
>kY0JmURQuP/KnIiJt2th096JWftQAWZvmF7XYwBS82ZReQzqj/VGPZQgO1UBUR3v
>ZIHXzfm/fuA9UtT8BZCUJSgkDL3nkVuHWTVt+HkealBxqjGZj5Y+S6XXwhfNnqYA
>U0oADAoB3rqnmRyhP8A266NxA+2MkZ8YERHG9GY0FIa3Oe2U6AWXMfxB2NwGx/5X
>X4iKTSD2uvk5QFw8F7/F8aovh0D0kttCxGR8G6ZMY5HxMNSVyWiK257QNWkTl4xO
>xHmLUvECwKlpCwfzCL/N8A6xv4iux+PO8SzYRcKKx41wvS13AN0N3YFA8OPe0HNH
>cJM9xgQ1pksxAjxM4z/7xh4NU1v2XlpG5trbIYmDMHQR77bPpkXLe/c4xiTVU4dP
>ABEBAAGJAh8EGAECAAkFAlyR/WgCGwwACgkQWfbgE3AOYGUnNQ/8CAleXdzC8dkx
>20Ph8vQvXn3poURZMftFeL8nnPp0Rx5KlBYe5Fvkldbv4lz7p6XTEDUfzy7fpZAC
>PjHVCuT4RUIsDMUPqjruhQuo7dFJqT9Pe692msk0PkqjvkXvW/TwfGNrGd6IYjpz
>/GY7xtTzxrnrzYk0E/s+E0Zr0nA7VZYwbQtVT2+jYn4TKYWJ/CXP87BoE05IrY2Q
>DEQn1zCapjdiyo/5UlyXKp4LrqQqoaFhNvGUa5teZ6wOwX/T/uM0ijLemvGq3mAd
>8v1elh7gHnxQJ1qLGStXS/CrsR6JO9QE0/AfI18wLs7tDZoAL+tThmBy9CyfSAko
>F6YBKaCNc9zZyoutFAkBQClUZXRof2PkYMGKcNDeoHpA9o5AXJPAO9iOkU+JRb+a
>j4YRM1iGiG83wLIhvuI8d3HiczaRKp2LWu7MOK+0FfOdfswzXl1UHLphSWcKlbwJ
>mDkhcE/7k84Fd2EHSfravtUcfpcauL2+2f+H3x3FQqYxYbP9yQusmB8Bq4x+Ukcs
>YSzWnELUjHxXlI+fCgOOc7DF90ffPlg8LVo24O436HF1Cyl7izX2pIWnENmLVh8H
>33W6DBs1QGh293phN+CBYInxYjn8X12RuCOvQeFAJVXlJSK58SLSKvf81DWmAbu/
>iX3+DXBQeKKl6cZZOAKjhVtG7X0SDjE=
>=89x7
>-END PGP PUBLIC KEY BLOCK-
>
>-BEGIN PGP PUBLIC KEY BLOCK-
>Version: GnuPG v1
>
>mQINBFyFx0kBEADHUr5MvL2qZKxcIeN31OoMhbOipk131IFzp+k4wob1GwGTai+t
>n18pEkWKXACWTdBgk+QggAb78uh0Z1+otlB3x6W9IoFf4rxc6xAKKlveYEF2lnaw
>r/hvIzNYcleR3watbnMls0zHTQm0VsF7ZeDZ2UAWBZFy5+O9UZMgTvSiSOumNrFp
>pq6u8mrC/8p+WbcqYZLuB5t5aHkMuWgLFEpnlbCU5vlOohl0XNyvg8iu/uR+KT7P
>kzUu8KtUgyYcC0vywlBeCe3FE7vQ3MEg5VkiNd7jArkDmiWmQQyJbeMbLXHUXQhN
>uXk/UvIZ9QUKiW50A+iSCdiHPVxxpJS5bRflvdTiUMmW8bnnPqnw1ELoHcVDKNra
>aykuOQtLJxMpRfHgtzA1Si9bkXeDvRNmUyqbmXcq/UjHfGjg6UOKJvXrHQ20fPn2
>4U0YiGBtwhIyZ9m0TbdS82HLNlixeBbkEWG1uzF3a72xMmg1EHvnS9h0mMy2KF93
>hkdaWFujSRjGi5LPT76EO6zv8WH+73wd4uVVRuHB5z6MbtQRD5iP4u8Bm4azk1IQ
>cPQ83oViM69BV5t8pjIfhLTjLEhpp7KdO/3fcu8bJxOMCHExp9fSsoH97bWxdVtN
>51liD/ENDJrt4E0XwuyZtzFG++X+N6mRWly8ny564tv7zlQsjBLQH6ACNwARAQAB

Re:Re: [VOTE] Accept ShardingScaling Donation

[Sion Yang]

Sorry, I miss the contributor, I will update the proposal, and start new round 
vote.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-12 17:40:12, "Willem Jiang"  wrote:
>It's great to hear there is new subproject comes to ShardingSphere.
>Just a quick question about the contributors of this project.
>There are four contributors[1] but only 3 initial committer, is there
>any reason that you don't include ssxlulu in?
>
>[1]https://github.com/avalon566/sharding-scaling/graphs/contributors
>
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Tue, Nov 12, 2019 at 3:23 PM Sion Yang  wrote:
>>
>> Dear Apache ShardingSphere Incubator Community ,
>>
>>
>> After some discussions on the ShardingScaling donation proposal, I would
>> like to start a vote on accepting ShardingScaling into the Apache Incubator
>> as ShardingSphere's sub-project.
>>
>>
>> Discussion in ML
>> https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%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 and ZongLei 
>> Dong have contributed many features and codes.
>> Current, ShardingScaling has implemented basic data migration and scaling 
>> out data nodes feature.
>>
>>
>> ## Core developer
>>
>>
>> Wen OuYang is an experienced open source developer.
>> Yi Yang is an experienced open source developer and ShardingSphere PPMC.
>> ZongLei Dong is an experienced open source developer.
>>
>>
>> ## Donation source
>>
>>
>> Github repo: 
>> [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>>
>>
>> ## Source and Intellectual Property Submission Plan
>>
>>
>> ShardingScaling was opened in Github on 18 Sep 2019. The project major 
>> contributors are Wen OuYang, Yi Yang and ZongLei Dong. Yi Yang is 
>> ShardingSphere's PPMC, ICLA are submitted. Wen OuYang and ZongLei Dong will 
>> sign ICLA 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

Re:Re:Re: [VOTE] Accept ShardingScaling Donation

[Sion Yang]

Proposal has updated in wiki.
https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-12 18:04:40, "Sion Yang"  wrote:
>Sorry, I miss the contributor, I will update the proposal, and start new round 
>vote.
>
>
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2019-11-12 17:40:12, "Willem Jiang"  wrote:
>>It's great to hear there is new subproject comes to ShardingSphere.
>>Just a quick question about the contributors of this project.
>>There are four contributors[1] but only 3 initial committer, is there
>>any reason that you don't include ssxlulu in?
>>
>>[1]https://github.com/avalon566/sharding-scaling/graphs/contributors
>>
>>
>>Willem Jiang
>>
>>Twitter: willemjiang
>>Weibo: 姜宁willem
>>
>>On Tue, Nov 12, 2019 at 3:23 PM Sion Yang  wrote:
>>>
>>> Dear Apache ShardingSphere Incubator Community ,
>>>
>>>
>>> After some discussions on the ShardingScaling donation proposal, I would
>>> like to start a vote on accepting ShardingScaling into the Apache Incubator
>>> as ShardingSphere's sub-project.
>>>
>>>
>>> Discussion in ML
>>> https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%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 and ZongLei 
>>> Dong have contributed many features and codes.
>>> Current, ShardingScaling has implemented basic data migration and scaling 
>>> out data nodes feature.
>>>
>>>
>>> ## Core developer
>>>
>>>
>>> Wen OuYang is an experienced open source developer.
>>> Yi Yang is an experienced open source developer and ShardingSphere PPMC.
>>> ZongLei Dong is an experienced open source developer.
>>>
>>>
>>> ## Donation source
>>>
>>>
>>> Github repo: 
>>> [https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).
>>>
>>>
>>> ## Source and Intellectual Property Submission Plan
>>>
>>>
>>> S

Re:[ANNOUNCE] New committer: Zhiyi Yan

[Sion Yang]

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
>

Re:Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 3

[Sion Yang]

+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  于2019年11月7日周四 下午7:34写道：
>
>> Hi ShardingSphere Community,
>>
>>
>> I tried my best to solve the issues you raised, and went through the check
>> list twice to avoid the confusion, but your review and vote on this release
>> is important to us. Look forward to your attention and interaction.
>>
>>
>> Release notes:
>>
>> https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md
>>
>>
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/
>>
>>
>> Maven 2 staging repository:
>>
>> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1026/org/apache/shardingsphere/
>>
>>
>> Git tag for the release:
>> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/
>>
>>
>> Release Commit ID:
>>
>> https://github.com/apache/incubator-shardingsphere/commit/ea05bb0ff693bde04b7e0742386fdcb94b93bd60
>>
>>
>> Keys to verify the Release Candidate:
>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>>
>>
>> Look at here for how to verify this release candidate:
>> https://shardingsphere.apache.org/community/en/contribute/release/
>>
>>
>> The vote will be open for at least 72 hours or until necessary number of
>> votes are reached.
>>
>>
>> Please vote accordingly:
>>
>>
>> [ ] +1 approve
>>
>>
>> [ ] +0 no opinion
>>
>> [ ] -1 disapprove with the reason
>>
>>
>> Checklist for reference:
>>
>>
>> [ ] Download links are valid.
>>
>>
>> [ ] Checksums and PGP signatures are valid.
>>
>>
>> [ ] DISCLAIMER is included.
>>
>>
>> [ ] Source code artifacts have correct names matching the current release.
>>
>>
>> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>>
>>
>> [ ] All files have license headers if necessary.
>>
>>
>> [ ] No compiled archives bundled in source archive.
>>
>>
>>
>>
>> Best wishes,
>> Trista
>>
>>
>>  Juan Pan
>>
>>
>> panj...@apache.org
>> Juan Pan(Trista), Apache ShardingSphere
>>
>>

Re:Re: [ShardingScaling][Discuss] Http request APIS about shardingscaling

[Sion Yang]

When create job, the job_id do not generate, so can't input .


Progress is part information of job, so I think progress word show in url is 
better.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-12-04 16:31:34, "xia Yanick"  wrote:
>Hi Xiang:
>   That's exactly what I needed,  otherwise, do you want like a restful 
> style?
>   
>   create a job:   /shardingscaling/job/ [POST]
>   query a job status: /shardingscaling/job/ [GET]
>   stop a job  /shardingscaling/job/ [DELETE]
>
>
>
>
>> On Dec 4, 2019, at 16:18, sushixiang  wrote:
>> 
>> Hi, everybody:
>> 
>> 
>> Http request apis will be provided for shardingscaling to let people easily 
>> manager the scaling job.
>> 
>> 
>> Here are the definitions of such apis:
>> 
>> 
>> /shardingscaling/job/start [POST]
>> /shardingscaling/job/progress/${jobId} [GET]
>> /shardingscaling/job/stop [POST]
>> 
>> 
>> 
>> Above apis will be used for starting job, get job process and stop job 
>> respectively.
>> 
>> 
>> Here are the related issue and pr:
>> [1] https://github.com/apache/incubator-shardingsphere/issues/3256
>> [2] https://github.com/apache/incubator-shardingsphere/pull/3656
>> 
>> 
>> Comments or Suggestions on it are welcome!
>> 
>> 
>> 
>> Thanks!
>

Re:Re: [ShardingScaling][Discuss] Http request APIS about shardingscaling

[Sion Yang]

Agree. [PUT] /job/ with stop status in body is not as clear as using 
`stop` on uri directly, I think.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-12-05 09:29:20, "sushixiang"  wrote:
>Hi, PUT may be used for modification, but we really not modify anything. And I 
>think this may be not as straightforward as putting 'stop' in the url.What do 
>you think?
>
>
>
>
>
>
>--Original--
>From:"xia Yanick"Date:Wed, Dec 4, 2019 05:10 PM
>To:"dev"
>Subject:Re: [ShardingScaling][Discuss] Http request APIS about 
>shardingscaling
>
>
>
>HI Xiang:
>   how about that stop a job like:
>   
>   PUT /shardingscaling/job/   Content-Type: application/json 
>   Body: { "status": "stop" }
>   
>
>
> On Dec 4, 2019, at 17:05, sushixiang  
>

Re:[DISCUSS] The DataBase UNSIGNED INT and UNSIGNED BIGINT column return value discuss

[Sion Yang]

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.

Re:Re: Move ShardingScaling project to apache-incubator/shardingsphere repo

[Sion Yang]

Dear Apache ShardingSphere Incubator Community,


The initial committers' icla files has already been confirmed. 
I will merge ShardingSclaing project to apache-incubator/shardingsphere repo as 
a sub-project recently with commit history.
Currently, ShardingSclaing only support MySQL, and usage is not quiet easy.
So I want to merge it to a new branch first to develop. After we complete to 
support PostgreSQL and link to ShardingUI, we merge it to dev branch and go to 
step of release.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-18 21:03:10, "Liang Zhang"  wrote:
>Good news, hope merge to apache repo soon
>
>On 2019/11/17 02:33:54, "Sion Yang"  wrote: 
>> Dear Apache ShardingSphere Incubator Community,
>> 
>> Accept ShardingScaling Donation vote has passed.
>> ML is 
>> https://lists.apache.org/thread.html/f7cf7f6d0d503080511f9c3bdc6bda25db8aad0cce2b03d2338484d2@%3Cdev.shardingsphere.apache.org%3E
>>  Now, Initial committers' icla files has submitted to secret...@apache.org, 
>> and waiting for reply.
>> After replying, We will move ShardingScaling project to 
>> apache-incubator/shardingsphere repo as a sub-project.
>> --
>> 
>> Yi Yang(Sion)
>> Apache ShardingSphere

[ShardingScaling][Discuss] The basic features including in the first beta release version

[Sion Yang]

Hi ShardingSphere community,


ShardingScaling sub-project has been merged into ShardingSphere. 
Now It can migrate data and scaling out for MySQL with sharding-proxy. So I 
think it's not enough to release and usage.
There are following items and features we need to complete in the first beta 
release version.


1. Change as a server instead of a independent program
1.1 Use Netty to implement as HTTP Servers
1.2 Provide create, query and stop job interface
1.2.1 Create job interface
1.2.2 query job interface, consider about which informations need to 
show
1.2.3 Stop job interface
1.2.4 The Stopped job need to persist, in register center or log files
2. UI design and cooperation
2.1 Design
2.1.1 ShardingScaling overview UI
2.1.2 Scaling Progress Query UI. How to show the progress detail of 
jobs.
2.2 Config ShardingScaling Server 
3. Support PostgreSQL
3.1 Support PostgreSQL upper 9.4 version through the logical replication
 3.1.1 Support Official logic replication plugin
 3.1.1 Support third logic replication plugin -- wal2json


Have any important job need to be done in first beta release?


--

Yi Yang(Sion)
Apache ShardingSphere

Re:Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3 ROUND 4

[Sion Yang]

+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-12 10:20:54, "zhaojun"  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.
>
>--
>Zhao Jun
>Apache Sharding-Sphere & ServiceComb
>
>> On Nov 11, 2019, at 8:04 PM, 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  于2019年11月11日周一 下午6:40写道：
>> 
>>> Hi everyone,
>>> 
>>> 
>>> With the help and effort of our community, the previous issues were fixed
>>> already. I am glad to invite everyone to move on to check and vote for our
>>> 4.0.0-RC3 ROUND 4.
>>> 
>>> 
>>> Release notes:
>>> 
>>> https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md
>>> 
>>> 
>>> The release candidates:
>>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC3/
>>> 
>>> 
>>> Maven 2 staging repository:
>>> 
>>> https://repository.apache.org/content/repositories/orgapacheshardingsphere-1027/org/apache/shardingsphere/
>>> 
>>> 
>>> Git tag for the release:
>>> https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC3/
>>> 
>>> 
>>> Release Commit ID:
>>> 
>>> https://github.com/apache/incubator-shardingsphere/commit/78a67e8c088ffc0b6f0e2c7418b0217cdc3bb87d
>>> 
>>> 
>>> Keys to verify the Release Candidate:
>>> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
>>> 
>>> 
>>> Look at here for how to verify this release candidate:
>>> https://shardingsphere.apache.org/community/en/contribute/release/
>>> 
>>> 
>>> The vote will be open for at least 72 hours or until necessary number of
>>> votes are reached.
>>> 
>>> 
>>> Please vote accordingly:
>>> 
>>> 
>>> [ ] +1 approve
>>> 
>>> 
>>> [ ] +0 no opinion
>>> 
>>> [ ] -1 disapprove with the reason
>>> 
>>> 
>>> Checklist for reference:
>>> 
>>> 
>>> [ ] Download links are valid.
>>> 
>>> 
>>> [ ] Checksums and PGP signatures are valid.
>>> 
>>> 
>>> [ ] DISCLAIMER is included.
>>> 
>>> 
>>> [ ] Source code artifacts have correct names matching the current release.
>>> 
>>> 
>>> [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>>> 
>>> 
>>> [ ] All files have license headers if necessary.
>>> 
>>> 
>>> [ ] No compiled archives bundled in source archive.
>>> 
>>> 
>>> 
>>> 
>>> Best wishes,
>>> Trista
>>> 
>>> 
>>> Juan Pan
>>> 
>>> 
>>> panj...@apache.org
>>> Juan Pan(Trista), Apache ShardingSphere
>>> 
>>> 
>

[VOTE] Accept ShardingScaling Donation

[Sion Yang]

Dear Apache ShardingSphere Incubator Community ,


After some discussions on the ShardingScaling donation proposal, I would
like to start a vote on accepting ShardingScaling into the Apache Incubator
as ShardingSphere's sub-project.


Discussion in ML
https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%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 and ZongLei Dong have 
contributed many features and codes.
Current, ShardingScaling has implemented basic data migration and scaling out 
data nodes feature.


## Core developer


Wen OuYang is an experienced open source developer.
Yi Yang is an experienced open source developer and ShardingSphere PPMC.
ZongLei Dong is an experienced open source developer.


## Donation source


Github repo: 
[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).


## Source and Intellectual Property Submission Plan


ShardingScaling was opened in Github on 18 Sep 2019. The project major 
contributors are Wen OuYang, Yi Yang and ZongLei Dong. Yi Yang is 
ShardingSphere's PPMC, ICLA are submitted. Wen OuYang and ZongLei Dong will 
sign ICLA 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/JavaHamcrest)


## Required Resources


### Git Repositories:


- 

[VOTE] Accept ShardingScaling Donation ROUND2

[Sion Yang]

Dear Apache ShardingSphere Incubator Community ,


With the help and effort of our community, the previous issues were fixed 
already. 
I am glad to invite everyone to start a vote on accepting ShardingScaling into 
the Apache Incubator as ShardingSphere's sub-project ROUND 2.


Discussion in ML
https://lists.apache.org/thread.html/86697906488f964e40d6ac5f3c07bc26686294281e23f60bc6f8da29@%3Cdev.shardingsphere.apache.org%3E
https://lists.apache.org/thread.html/a1ef4b44abe8f11273983e69c12becda12302aee852f7569c99a34d1@%3Cdev.shardingsphere.apache.org%3E


Please accept the ShardingScaling podling into the Apache Incubator.


The proposal can be found at
https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/ShardingScaling+Donation+Proposal
Here is the text of it:


## Abstract


ShardingScaling[1] is a simple scaling out component for Apache ShardingSphere 
Incubator[2].
It is designed to help users migrate data from origin database to 
ShardingSphere or scale out  ShardingSphere data node more easily.
It provides ability of migrant data, scaling out data nodes, etc.


## Proposal


The goal of this proposal is to bring the existing ShardingScaling codebase and 
existing developers and community into the Apache Software Foundation (ASF) as 
ShardingSphere's sub-project.
This project started in Open Source on Github nearly 2 months.
ShardingScaling is submitting this proposal to donate it to the Apache 
ShardingSphere Incubator under the Apache License, Version 2.0, in order to 
provide a visual management tool for ShardingSphere.
These artifacts are currently available on GitHub at 
[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).


## Background


ShardingSphere is an ecosystem of transparent distributed database middleware, 
focusing on data sharding, distributed transaction and database orchestration. 
It is also widely adopted by many companies and organizations as a solution to 
process their massive amounts of data. 
But users have long lacked an easy-to-use way to migrate their data from origin 
database when they first started using ShardingSphere.
Moreover, users have also lacked easy-to-use ways to expand data nodes when 
they use ShardingSphere for a while.
So Wen OuYang created a scaling out component for ShardingSphere -- 
ShardingScaling.


## Current status


After we pushed ShardingScaling in Github in an open source way, many users and 
developers have shown strong intentions to this. Yi Yang, ZongLei Dong and 
ssxlulu have contributed many features and codes.
Current, ShardingScaling has implemented basic data migration and scaling out 
data nodes feature.


## Core developer


Wen OuYang is an experienced open source developer.
Yi Yang is an experienced open source developer and ShardingSphere PPMC.


## Donation source


Github repo: 
[https://github.com/avalon566/sharding-scaling](https://github.com/avalon566/sharding-scaling).


## Source and Intellectual Property Submission Plan


ShardingScaling was opened in Github on 18 Sep 2019. The project major 
contributors are Wen OuYang, Yi Yang.
Yi Yang is ShardingSphere's PPMC, ICLA are submitted. 
Wen OuYang will sign ICLA and become Apache committer if vote be accepted after 
ShardingScaling is accepted into the Apache Software Foundation (ASF) as 
ShardingSphere's sub-project. 


## External Dependencies


### Apache 2.0 licenses


- sharding-core-common 4.0.0-RC2: 
[https://github.com/apache/incubator-shardingsphere](https://github.com/apache/incubator-shardingsphere)
- snakeyaml 1.16: 
[https://bitbucket.org/asomov/snakeyaml/src/default](https://bitbucket.org/asomov/snakeyaml/src/default)
- guava 18.0: [https://github.com/google/guava](https://github.com/google/guava)
- netty-all 4.1.16.Final: 
[https://github.com/netty/netty](https://github.com/netty/netty)
- commons-dbcp2 2.7.0: 
[https://github.com/apache/commons-dbcp](https://github.com/apache/commons-dbcp)
- commons-cli 1.4: 
[https://github.com/apache/commons-cli](https://github.com/apache/commons-cli)
- log4j 1.2.17: 
[https://github.com/apache/log4j](https://github.com/apache/log4j)
- gson 2.8.6: [https://github.com/google/gson](https://github.com/google/gson)




### MIT licenses


- slf4j-api 1.7.28: 
[https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j)
- slf4j-log4j12 1.7.28: 
[https://github.com/qos-ch/slf4j](https://github.com/qos-ch/slf4j)
- lombok 1.18.4: 
[https://github.com/rzwitserloot/lombok](https://github.com/rzwitserloot/lombok)
- mockito-core 2.7.21(scope test): 
[https://github.com/mockito/mockito](https://github.com/mockito/mockito)
- mockito-inline 2.7.21(scope test): 
[https://github.com/mockito/mockito](https://github.com/mockito/mockito)


### EPL 1.0 licenses


- junit 4.12(scope test): 
[https://github.com/junit-team/junit4](https://github.com/junit-team/junit4)


### BSD License


- hamcrest-library 1.3(scope test): 

Re: Move ShardingScaling project to apache-incubator/shardingsphere repo

[Sion Yang]

Merging has completed in branch `sharding-scaling`[1]. 


[1] https://github.com/apache/incubator-shardingsphere/tree/sharding-scaling


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-11-25 11:18:10, "Sion Yang"  wrote:
>
>
>Dear Apache ShardingSphere Incubator Community,
>
>
>The initial committers' icla files has already been confirmed. 
>I will merge ShardingSclaing project to apache-incubator/shardingsphere repo 
>as a sub-project recently with commit history.
>Currently, ShardingSclaing only support MySQL, and usage is not quiet easy.
>So I want to merge it to a new branch first to develop. After we complete to 
>support PostgreSQL and link to ShardingUI, we merge it to dev branch and go to 
>step of release.
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2019-11-18 21:03:10, "Liang Zhang"  wrote:
>>Good news, hope merge to apache repo soon
>>
>>On 2019/11/17 02:33:54, "Sion Yang"  wrote: 
>>> Dear Apache ShardingSphere Incubator Community,
>>> 
>>> Accept ShardingScaling Donation vote has passed.
>>> ML is 
>>> https://lists.apache.org/thread.html/f7cf7f6d0d503080511f9c3bdc6bda25db8aad0cce2b03d2338484d2@%3Cdev.shardingsphere.apache.org%3E
>>>  Now, Initial committers' icla files has submitted to secret...@apache.org, 
>>> and waiting for reply.
>>> After replying, We will move ShardingScaling project to 
>>> apache-incubator/shardingsphere repo as a sub-project.
>>> --
>>> 
>>> Yi Yang(Sion)
>>> Apache ShardingSphere

[ISSUE] Can't getClob for LongVarchar type data.

[Sion Yang]

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:Re:[ISSUE] Can't getClob for LongVarchar type data.

[Sion Yang]

Getting value accroding to target type in StreamQueryResult has completed.Pull 
Request is #3208 https://github.com/apache/incubator-shardingsphere/pull/3208


--

Yi Yang(Sion)
Apache ShardingSphere



在 2019-10-10 15:34:58，"sunbufu"  写道：
>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:[ISSUE] Can't getClob for LongVarchar type data.

[Sion Yang]

[1] issue#2956 https://github.com/apache/incubator-shardingsphere/issues/2956
[2] issue#2956 https://github.com/apache/incubator-shardingsphere/issues/3017




--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-10-10 15:25:59, "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:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.1

[Sion Yang]

+1,


I checked following checklist:


[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.
[x] Source code can compile successfully.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-25 22:47:04, "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
> 
>
>
>The release candidates:
>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/
> 
>
>
>Git tag for the release:
>https://github.com/apache/incubator-shardingsphere/tree/4.0.1/ 
>
>
>Release Commit ID:
>https://github.com/apache/incubator-shardingsphere/commit/b67d320209b4d4585231b356f2c575cfa383a98b
> 
>
>
>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.
>
>--
>Zhao Jun (cherrylzhao)
>Apache ShardingSphere & ServiceComb
>

Re:回复：[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

ShardingScaling is a data scaling out function for ShardingSphere.


Currently it is in scaling-scaling branch to develop, and now we plan merge it 
into master branch.


Just it.




--

Yi Yang(Sion)
Apache ShardingSphere



在 2020-03-04 19:52:04，"思埝四叶草" <546810...@qq.com> 写道：
>I'm sorry
>
>
>I don't understand your email
>
>
>Do I need to mention this question or do I need answers here
>
>
>
>------原始邮件--
>发件人:"Sion Yang"发送时间:2020年3月4日(星期三) 晚上7:09
>收件人:"dev"
>主题:Re:[Scaling] Preparing to merge sharding-scaling and 
>sharding-scaling-ui into master
>
>
>
>Hello ShardingSphere Community,
>
>The Preparing has finished, detail see issue#4510[1].
>
>
>I will create pull request merge sharding-scaling and sharding-scaling-ui into 
>master branch.
>
>
>- [x] Double check the License and dependency
>- [x] Double check ASF headers
>- [x] Check spelling and naming
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/4510
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2020-02-28 15:12:13, "Sion Yang" Hello ShardingSphere Community,
>
>
>
>
>ShardingScaling has finish some basic function for migrating and scaling 
>out, detail see #3598[1] .
>
>I think it is already available to merge into master branch.
>
>
>
>
>So I'd like to open a discussion and do some checks for merging 
>sharding-scaling/sharding-scaling-ui into master branch.
>
>
>
>
>Following is the check list:
>
>- [ ] Double check the License and dependency
>
>- [ ] Double check ASF headers
>
>- [ ] Check spelling and naming
>
>
>
>
>Any more check item?
>
>
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/3598
>
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>
>
>

Re:Re:[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

Merge work has completed by PR#4605[1], PR#4606[2]


[1] https://github.com/apache/incubator-shardingsphere/pull/4605
[2] https://github.com/apache/incubator-shardingsphere/pull/4606


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-03-04 19:09:14, "Sion Yang"  wrote:
>Hello ShardingSphere Community,
>
>The Preparing has finished, detail see issue#4510[1].
>
>
>I will create pull request merge sharding-scaling and sharding-scaling-ui into 
>master branch.
>
>
>- [x] Double check the License and dependency
>- [x] Double check ASF headers
>- [x] Check spelling and naming
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/4510
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere
>
>
>
>At 2020-02-28 15:12:13, "Sion Yang"  wrote:
>>Hello ShardingSphere Community,
>>
>>
>>
>>
>>ShardingScaling has finish some basic function for migrating and scaling out, 
>>detail see #3598[1] .
>>
>>I think it is already available to merge into master branch.
>>
>>
>>
>>
>>So I'd like to open a discussion and do some checks for merging 
>>sharding-scaling/sharding-scaling-ui into master branch.
>>
>>
>>
>>
>>Following is the check list:
>>
>>- [ ] Double check the License and dependency
>>
>>- [ ] Double check ASF headers
>>
>>- [ ] Check spelling and naming
>>
>>
>>
>>
>>Any more check item?
>>
>>
>>
>>
>>[1] https://github.com/apache/incubator-shardingsphere/issues/3598
>>
>>
>>
>>--
>>
>>Yi Yang(Sion)
>>Apache ShardingSphere
>
>
>
>
>
> 

Re:Re: [VOTE] Graduate Apache ShardingSphere (incubating)

[Sion Yang]

+1 


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-03-05 12:16:53, "zhangli...@apache.org"  wrote:
>Please vote on the proposal for ShardingSphere graduation to TLP to submit
>to
>the Incubator PMC.
>
>Vote:
>[ ] +1 - Recommend Graduation of Apache ShardingSphere as a TLP
>[ ] -1 - Do not recommend graduation of Apache ShardingSphere because ….
>
>This vote will stay open for at least 72 hours.

Re:[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

Hello ShardingSphere Community,The Preparing has finished, detail see 
issue#4510[1].I will create pull request merge sharding-scaling and 
sharding-scaling-ui into master branch.- [x] Double check the License and 
dependency- [x] Double check ASF headers- [x] Check spelling and naming[1] 
https://github.com/apache/incubator-shardingsphere/issues/4510


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-28 15:12:13, "Sion Yang"  wrote:
>Hello ShardingSphere Community,
>
>
>
>
>ShardingScaling has finish some basic function for migrating and scaling out, 
>detail see #3598[1] .
>
>I think it is already available to merge into master branch.
>
>
>
>
>So I'd like to open a discussion and do some checks for merging 
>sharding-scaling/sharding-scaling-ui into master branch.
>
>
>
>
>Following is the check list:
>
>- [ ] Double check the License and dependency
>
>- [ ] Double check ASF headers
>
>- [ ] Check spelling and naming
>
>
>
>
>Any more check item?
>
>
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/3598
>
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere

Re:[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

Hello ShardingSphere Community,

The Preparing has finished, detail see issue#4510[1].


I will create pull request merge sharding-scaling and sharding-scaling-ui into 
master branch.


- [x] Double check the License and dependency
- [x] Double check ASF headers
- [x] Check spelling and naming


[1] https://github.com/apache/incubator-shardingsphere/issues/4510


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-28 15:12:13, "Sion Yang"  wrote:
>Hello ShardingSphere Community,
>
>
>
>
>ShardingScaling has finish some basic function for migrating and scaling out, 
>detail see #3598[1] .
>
>I think it is already available to merge into master branch.
>
>
>
>
>So I'd like to open a discussion and do some checks for merging 
>sharding-scaling/sharding-scaling-ui into master branch.
>
>
>
>
>Following is the check list:
>
>- [ ] Double check the License and dependency
>
>- [ ] Double check ASF headers
>
>- [ ] Check spelling and naming
>
>
>
>
>Any more check item?
>
>
>
>
>[1] https://github.com/apache/incubator-shardingsphere/issues/3598
>
>
>
>--
>
>Yi Yang(Sion)
>Apache ShardingSphere





 

[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

Hello ShardingSphere Community,




ShardingScaling has finish some basic function for migrating and scaling out, 
detail see #3598[1] .

I think it is already available to merge into master branch.




So I'd like to open a discussion and do some checks for merging 
sharding-scaling/sharding-scaling-ui into master branch.




Following is the check list:

- [ ] Double check the License and dependency

- [ ] Double check ASF headers

- [ ] Check spelling and naming




Any more check item?




[1] https://github.com/apache/incubator-shardingsphere/issues/3598



--

Yi Yang(Sion)
Apache ShardingSphere

Re:Re:[Scaling] Preparing to merge sharding-scaling and sharding-scaling-ui into master

[Sion Yang]

Thanks for your feedback,


I will open [VOTE] mail list after this preparing and checking finished.


--

Yi Yang(Sion)
Apache ShardingSphere

Re:Re: Talk about graduation as TLP for Apache ShardingSphere(Incubator)

[Sion Yang]

I think these statistics are enough.


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-06 11:28:02, "zhangli...@apache.org"  wrote:
>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)
>>> > E-mail: panj...@apache.org
>>> >
>>> >
>>> >
>>> >
>>> > On 02/5/2020 17:38，zhangli...@apache.org wrote：
>>> > I want discuss about project VP, PMC and committer list after
>>> graduation.
>>> > I would like to keep all PPMC members to PMC, and keep all current
>>> > committers as committers too.
>>> > The almost committers are new guys for ShardingSphere, they may need
>>> more
>>> > experiences for open source community governance, we can vote
>>> committers to
>>> > PMC one by one after graduation.
>>> > I nominate myself as project VP because my responsibility is monthly
>>> report
>>> > to incubator, and I will in charge of to report to ASF in future.
>>> >
>>> > Any suggestion?
>>> > --
>>> >
>>> > Liang Zhang (John)
>>> > Apache ShardingSphere & Dubbo
>>> >
>>> >
>>> > zhangli...@apache.org  于2020年1月20日周一 下午3:26写道：
>>> >
>>> > Got it, it means those threads are not block for our graduation, and
>>> > could be done anytime.
>>> >
>>> > Yes
>>> >
>>> > --
>>> >
>>> > Liang Zhang (John)
>>> > Apache ShardingSphere & Dubbo
>>> >
>>> >
>>> > Juan Pan  于2020年1月20日周一 上午10:14写道：
>>> >
>>> > Got it, it means those threads are not block for our graduation, and
>>> > could be done anytime.
>>> >
>>> >
>>> > Juan Pan (Trista)

Re:[IMPORTANT][PPMC] Invitation to be ShardingSphere PMC member

[Sion Yang]

Yes, I am willing to be part of PMC.

--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-11 15:40:26, "zhangli...@apache.org"  wrote:
>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] 4.0.1 stable version release plan

[Sion Yang]

Should we add the fix of Issue#4182[1] into 4.0.1?


[1] https://github.com/apache/incubator-shardingsphere/issues/4182


--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-02-09 15:44:05, "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

Re:[DISCUSS] merge docs and example repos into trunk repo

[Sion Yang]

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:Re: Discussion of pluggable platform of ShardingSphere

[Sion Yang]

I prefer Plan A too.








--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-01-03 00:13:07, "zhangli...@apache.org"  wrote:
>I have 2 ideas for the pluggable platform.
>
>Plan A:
>
>Design a unify DataSource to process all rules, it should be a transparent
>DataSource if no rule provided (but it should be valid). We can name it as
>`ShardingSphereDataSource`.
>There are lots of hooks in `ShardingSphereDataSource`, such as:
>  - route hook: for sharding, master-slave and shadow;
>  - SQL rewrite hook: for sharding, encrypt and shadow;
>  - execution hook: for sharding and transaction;
>  - merge hook: for sharding and encrypt;
>  - init hook: for orchestration;
>  - config refresh hook: for orchestration;
>
>The hook should load feature implementations via SPI and appended
>by pluggable platform automatically. (SPI should design the process order)
>
>Advantage:
>  - Only one API for `ShardingSphereDataSource` which should not confuse
>the users;
>  - Process logics internally, pretty high performance for this solution;
>  - Can be reused for Proxy.
>
>Disadvantage:
>  - Difficult for developers, they need to know every hooks.
>
>Plan B:
>
>Provide independent DataSources, every DataSources process oneself only.
>And we may have lots of DataSource, such as ShardingDataSource,
>MasterSlaveDataSource, EncryptDataSource, ShadowDataSource,
>TransactionDataSource, OrchestrationDataSource and so on.
>Every DataSources should composite by users themselves, ShardingSphere can
>privide a Facade class to simplify the usage.
>
>Advantage:
>  - Isolation by design level, every DataSource has clear and simple
>responsibility;
>  - Simple for developer, they need to know independent logic for one
>DataSource only, do not need expose internal implementations.
>
>Disadvantage:
>  - Can not reuse by Proxy;
>  - Difficult for user to find every possible combination of DataSource;
>  - Hide the internal implementation may cause low performance;
>
>By the way, I just discuss about how to design Proxy for Plan B. It should
>be every features have a independent proxy process (may consider about put
>them into one process in future).
>ShardingProxy visit EncryptProxy, and EncryptProxy visit ShadowProxy,
>the performance should not enough.
>
>Conclusion:
>Even the Plan B has better design, but I worry about the performance and
>the difficulty for user. So I prefer Plan A for now.
>
>--
>
>Liang Zhang (John)
>Apache ShardingSphere & Dubbo
>
>
>guangyuan wang  于2019年12月11日周三 下午2:21写道：
>
>> +1 It sounds great.
>> And is the platform suitable for JDTX? And Sharding may not be a necessary
>> function, maybe transaction will be more widely used. So, will JDTX will be
>> a plugin which is easily used in the platform?
>>
>> Zonglei Dong  于2019年12月9日周一 下午9:24写道：
>>
>> > +1, That sounds great!
>> >
>> >
>> > For a pluggable platform, contributors will be very convenient to
>> > contribute code, This will attract more people.
>> >
>> >
>> > Zonglei Dong
>> > Apache ShardingSphere
>> >
>> >
>> > On 12/9/2019 19:13，sunbufu wrote：
>> > +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 

Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0 round 2

[Sion Yang]

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

[Sion Yang]

Sorry, I want to change my vote to -1.


I think issue#3770[1] should be fixed and included in 4.0.0 release.


ML[2] 4.0.0 stable version release plan also discusses the issue.


[1] https://github.com/apache/incubator-shardingsphere/issues/3770
[2] 
https://lists.apache.org/thread.html/befefeb3a81c940b51b5059e097e620dbdbef7cff4539fe1cb1f7902%40%3Cdev.shardingsphere.apache.org%3E


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-12-24 18:06:45, "Sion Yang"  wrote:
>+1I checked the LICENSE, NOTICE, Checksums, PGP signatures and installing 
>source code.No problem happened.
>
>
>Checklist:
>[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-12-23 21:15:41, "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-1028/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/76d011b310554d1c03540038173f03841706d623
>>
>>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:4.0.0 stable version release plan

[Sion Yang]

I think issue #3770[1] need to be fixed before 4.0.0 stable version.


The issue is caused by PR#3663[2].
If we revert PR#3663[2], the encrypt can't only work in JPA with auto-ddl on, 
and users can avoid this problem by create tables manually.


But issue #3770[1] may cause encrypt can't work when plainColumn equals 
logicColumn,
which is designed to allow equal.


For the problem of encrypt in JPA, we should perfectly fix with implementing 
the DDL of encrypt.


[1] https://github.com/apache/incubator-shardingsphere/issues/3770
[2] https://github.com/apache/incubator-shardingsphere/pull/3663


--

Yi Yang(Sion)
Apache ShardingSphere



At 2019-12-07 17:18:12, "zhangli...@apache.org"  wrote:
>Hi, ShardingSphere community,
>
>I'd like to talk about the release plan of 4.0.0 stable version.
>As you know, after enter Apache incubator, ShardingSphere had released 3 RC
>versions during the past year. The features are stable more and more, it is
>the time to talk about task details before 4.0.0 release.
>
>I just list some tasks that I knew, please add if I missing something:
>
>1. Performance test display. The current result is in [1], we still need to
>do some adjust to make it better.
>2. Acceptance test. The repo is in [2], we still need docker and shell to
>make it run automatically. And we will transfer it to apache repo[3] soon.
>3. Remain bugs hot fix. I don't find any high priority bug to be fixed now.
>
>Any other tasks missing here?
>
>[1] https://shardingsphere.apache.org/benchmark/#/overview
>[2] https://github.com/OpenSharding/shardingsphere-acceptance-test
>[3] https://github.com/apache/incubator-shardingsphere-acceptance-test
>
>--
>
>Liang Zhang (John)
>Apache ShardingSphere & Dubbo

Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

[Sion Yang]

+1I checked the LICENSE, NOTICE, Checksums, PGP signatures and installing 
source code.No problem happened.


Checklist:
[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-12-23 21:15:41, "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-1028/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/76d011b310554d1c03540038173f03841706d623
>
>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:[ShardingScaling][Discuss] Add datasources check before start scaling job

[Sion Yang]

Nice idea.


We need to consider that implementing the check privileges function according 
to the database type, and loaded by SPI.


And for each type database, what's privileges we need to check.




--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-01-06 17:02:30, "sushixiang"  wrote:
>Hi everybody:
>
>
>We will add datasources check function before starting scaling job.
>
>
>It will help us check the validity of the datasources and the privileges of 
>the datasources's users before startingscaling job successfully.
>
>
>Here are the related issue:
>[1]https://github.com/apache/incubator-shardingsphere/issues/3849
>
>
>
>Comments or Suggestions on it are welcome!
>
>
>
>Thanks!

Re:[ANNOUNCE] New committer: Xiaofeng Jiang

[Sion Yang]

Welcome!




--

Yi Yang(Sion)
Apache ShardingSphere



At 2020-01-08 14:02:52, "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
>

[Discuss][Scaling] Re-design for Sharding-Scaling Job

[Sion Yang]

Dear ShardingSphere Community,


I am glad to discuss a new design for Sharding-Scaling Job.
Same issue in GitHub 
[Issue#5106](https://github.com/apache/incubator-shardingsphere/issues/5106).



## Current Job Design




Sharding-Scaling will extract `datasources` and `actualDataNodes` information 
from ShardingSphere's sharding configuration to generate Sharding-Scaling jobs. 
Each complete ShardingSphere configuration will generate a complete 
Sharding-Scaling job.




After checking datasources, Sharding-Scaling job will do the first time job 
spliting according to the datasource. Each datasource will be one task of 
Sharding-Scaling job.




In datasource sub-task, it also will be splited to inventory task(or named 
history task) and incremental task (or named real-time task). What's more, the 
inventory task will still be split further through the tables, and maybe then 
splited by primary key.




Job structure like following:




```

Sharding-Scaling Job

|--- Datasource1 Sub-task

||--- Inventory Task

|||--- TableA Task

|||--- TableA Task shard #1

|||--- TableA Task shard #2

||.

|||--- TableB Task

||.

||--- Incremental Task

|--- Datasource2 Sub-task

.

``` 




For each table task without sharding, table task shard and incremental task, 
there are at lease two thread to execute the task. One is `Reader` which query 
or subscribe change data and the other `Writer` which write data into targer 
ShardingSphere.




The design is not friendly for distribution:




- The leaf task may be the second layer(incremental task), third layer(table 
task without sharding and fourth layer(table task shard).

- Concurrency or thread pool size is hard to control.

- Limited thread pool may cause problem 
[Issue#5092](https://github.com/apache/incubator-shardingsphere/issues/5092)




## New Design




In new design, the Sharding-Scaling job will not be splited with logic of 
database structure rather by the logic of distributed jobs.




```

Sharding-Scaling Job

|--- Inventory Task

|--- Inventory Task #1

||--- Inner Inventory Task For ds1.table1

||--- Inner Inventory Task For ds1.table2 #1

|--- Inventory Task #2

||--- Inner Inventory Task For ds1.table2 #2

||--- Inner Inventory Task For ds2.table3

..

|--- Incremental Task

|--- Incremental Task #1 For ds1

|--- Incremental Task #2 For ds2

..

```




In new design, Sharding-Scaling split job to inventory and incremental first, 
and then split inventory task by `job concurrency` users configured. The leaf 
task is `Inventory Task #n` and `Incremental Task #n`, which can be equally 
distributed to different Sharding-Scaling nodes.




The inventory table task and inventory table task shard in old design will be 
as inner task of `Inventory Task #n`, and exeucte one by one.




For `Reader` and `Writer`, they are similar to old design. But for new design, 
the thread pool size and concurrency become easier to understand and configure. 
Users only need to understand `job concurrency` property.




Todo list:




- [ ] Rename `Reader` and `Writer` 
[Issue#4595](https://github.com/apache/incubator-shardingsphere/issues/4595)

- [ ] Rename `HistoryTask` and `RealtimeTask`

- [ ] Refactor `ExecuteEngine` in Sharding-Scaling

- [ ] Refactor `Inventory Task`

- [ ] Refactor `TaskController`

- [ ] Refactor `JobController` 




I think the new design is better, and more suitable for development of 
Sharding-Scaling.




Any suggestions? 







--

Yi Yang(Sion)
Apache ShardingSphere

Re:Re: [VOTE] Release Apache ShardingSphere 4.1.0 Round 2

[Sion Yang]

+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

[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 2020-04-27 22:41:20, "zhaojun"  wrote:
>+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
>
>
>zhangli...@apache.org  于2020年4月27日周一 下午8:29写道：
>
>> +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.
>>
>>
>>
>>
>> --
>>
>> Liang Zhang (John)
>> Apache ShardingSphere & Dubbo
>>
>>
>> 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
>> >
>>

Re:Re: [DISCUSS]About a hotfix release version 4.1.1

[Sion Yang]

+1 ,

I think we should solve some sharding-scaling bug and issue in 4.1.1 version.

And there is a enhancement in scaling for 5.0.0 before, I think it also can be 
enhance in 4.1.1

list:

[1] https://github.com/apache/shardingsphere/issues/5390
[2] https://github.com/apache/shardingsphere/issues/5389
[3] https://github.com/apache/shardingsphere/pull/5068




--
Yi Yang(Sion)
Apache ShardingSphere





在 2020-05-14 18:19:53，"zhaojun"  写道：
>+1,
>I found another mysql8 compatible issue[1], it's better to release it in
>4.1.1.
>
>since theMySQLServerInfo.SERVER_VERSION is fixed at 5.6.4, so jdbc-driver
>will send the sql contains query_cache_size, we should dynamically judge it
>based on the physical database version, also i'have made some enhancement
>advices.
>
>[1]: https://github.com/apache/shardingsphere/issues/3097
>
>Regards,
>cherrylzhao
>---
>Email：zhao...@apache.org
>Jun Zhao(cherrylzhao) Apache ShardingSphere
>
>
>Zhiyi Yan  于2020年5月14日周四 下午6:02写道：
>
>> Good idea.
>>
>> 
>> Zhiyi Yan (Zhyee)
>> Apache ShardingSphere
>>
>>
>> zhangli...@apache.org  于2020年5月14日周四 下午5:55写道：
>>
>> > +1, release 4.1.1 is necessary and we at least need to include #5436
>> which
>> > is break all Oracle dialect.
>> >
>> > IMO, release this one issue only is good enough.
>> >
>> > --
>> >
>> > Liang Zhang (John)
>> > Apache ShardingSphere & Dubbo
>> >
>> >
>> > TaoZhi  于2020年5月14日周四 下午4:16写道：
>> >
>> > > In my opnion, the releasing of the version 4.1.1 is better.
>> > >
>> > >
>> > >
>> > >
>> > > TaoZhi
>> > >
>> > > At 2020-05-14 14:46:23, "KimmKing"  wrote:
>> > > >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:[Vote] ElasticJob donation

[Sion Yang]

+1, ElasticJob has great potential in scenarios that required asynchronous 
scheduling.




--

Yi Yang(Sion)
Apache ShardingSphere





At 2020-05-24 21:55:39, "zhangli...@apache.org"  wrote:
>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:Re: [VOTE] Release Apache ShardingSphere UI 5.0.0-alpha [Round 2]

[Sion Yang]

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


--

Yi Yang(Sion)
Apache ShardingSphere





At 2020-11-20 14:16:08, "zhangli...@apache.org"  wrote:
>+1
>
>I checked:
>
>[X] Download links are valid.
>
>[X] Checksums and PGP signatures are valid.
>
>[X] Source code distributions have correct names matching the current
>release.
>
>[X] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>
>[X] All files have license headers if necessary.
>
>[X] No compiled archives bundled in source archive.
>
>--
>
>Sincerely,
>Liang Zhang (John)
>Apache ShardingSphere
>
>
>Zhang Yonglun  于2020年11月19日周四 下午6:30写道：
>
>> +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 ElasticJob-3.0.0

[Sion Yang]

+1 


I checked :


[x] Download source can work well.
[x] sha512 exist and check correctly.
[x] asc check correctly
[x] version check correctly.







--

Yi Yang(Sion)
Apache ShardingSphere





At 2021-06-26 20:44:50, "吴伟杰"  wrote:
>Hello ShardingSphere Community,
>
>This is a call for vote to release Apache ShardingSphere
>ElasticJob-3.0.0
>
>Release notes:
>https://github.com/apache/shardingsphere-elasticjob/blob/master/RELEASE-NOTES.md
>
>The release candidates:
>https://dist.apache.org/repos/dist/dev/shardingsphere/elasticjob-3.0.0/
>
>Maven 2 staging repository:
>https://repository.apache.org/content/repositories/orgapacheshardingsphere-1063/org/apache/shardingsphere/elasticjob/
>
>Git tag for the release:
>https://github.com/apache/shardingsphere-elasticjob/tree/3.0.0/
>
>Release Commit ID:
>https://github.com/apache/shardingsphere-elasticjob/commit/1b2b15d7bf653b1fd6d455d940eabb13793347bb
>
>Keys to verify the Release Candidate:
>https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS
>
>Look here for how to verify this release candidate:
>https://shardingsphere.apache.org/community/en/contribute/release-elasticjob/
>
>GPG key ID:
>
>2DE3A2A9
>
>The vote will be open for at least 72 hours or until the necessary number of
>votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>
>[ ] +0 no opinion
>
>[ ] -1 disapprove with the reason
>
>PMC vote is +1 binding, all others are +1 non-binding.
>
>Checklist for reference:
>
>[ ] Download links are valid.
>
>[ ] Checksums and PGP signatures are valid.
>
>[ ] Source code distributions have correct names matching the current
>release.
>
>[ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
>
>[ ] All files have license headers if necessary.
>
>[ ] No compiled archives bundled in source archive.
>
>--
>
>Sincerely,
>Weijie Wu (TeslaCN)
>Apache ShardingSphere