[GitHub] [incubator-shardingsphere] coveralls commented on issue #3779: Decouple encrypt and sharding on merge and rewrite module
coveralls commented on issue #3779: Decouple encrypt and sharding on merge and rewrite module URL: https://github.com/apache/incubator-shardingsphere/pull/3779#issuecomment-568230341 ## Pull Request Test Coverage Report for [Build 1192](https://coveralls.io/builds/27748277) * **16** of **36** **(44.44%)** changed or added relevant lines in **15** files are covered. * No unchanged relevant lines lost coverage. * Overall coverage decreased (**-0.2%**) to **67.278%** --- | Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | | :-|--||---: | | [sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/statement/ShardingPreparedStatement.java](https://coveralls.io/builds/27748277/source?filename=sharding-jdbc%2Fsharding-jdbc-core%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fshardingjdbc%2Fjdbc%2Fcore%2Fstatement%2FShardingPreparedStatement.java#L148) | 1 | 2 | 50.0% | [sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/statement/ShardingStatement.java](https://coveralls.io/builds/27748277/source?filename=sharding-jdbc%2Fsharding-jdbc-core%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fshardingjdbc%2Fjdbc%2Fcore%2Fstatement%2FShardingStatement.java#L127) | 1 | 2 | 50.0% | [sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/JDBCDatabaseCommunicationEngine.java](https://coveralls.io/builds/27748277/source?filename=sharding-proxy%2Fsharding-proxy-backend%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fshardingproxy%2Fbackend%2Fcommunication%2Fjdbc%2FJDBCDatabaseCommunicationEngine.java#L137) | 0 | 1 | 0.0% | [shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/metadata/RelationMetas.java](https://coveralls.io/builds/27748277/source?filename=shardingsphere-sql-parser%2Fshardingsphere-sql-parser-relation%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fsql%2Fparser%2Frelation%2Fmetadata%2FRelationMetas.java#L43) | 0 | 1 | 0.0% | [sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/PreparedStatementExecutorWrapper.java](https://coveralls.io/builds/27748277/source?filename=sharding-proxy%2Fsharding-proxy-backend%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fshardingproxy%2Fbackend%2Fcommunication%2Fjdbc%2Fwrapper%2FPreparedStatementExecutorWrapper.java#L85) | 0 | 2 | 0.0% | [sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/StatementExecutorWrapper.java](https://coveralls.io/builds/27748277/source?filename=sharding-proxy%2Fsharding-proxy-backend%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fshardingproxy%2Fbackend%2Fcommunication%2Fjdbc%2Fwrapper%2FStatementExecutorWrapper.java#L85) | 0 | 2 | 0.0% | [sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/metadata/ShardingSphereMetaData.java](https://coveralls.io/builds/27748277/source?filename=sharding-core%2Fsharding-core-common%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fshardingsphere%2Fcore%2Fmetadata%2FShardingSphereMetaData.java#L42) | 0 | 12 | 0.0% | Totals | [](https://coveralls.io/builds/27748277) | | :-- | --: | | Change from base [Build 618](https://coveralls.io/builds/27730216): | -0.2% | | Covered Lines: | 11296 | | Relevant Lines: | 16790 | --- # - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-shardingsphere] terrymanu opened a new pull request #3779: Decouple encrypt and sharding on merge and rewrite module
terrymanu opened a new pull request #3779: Decouple encrypt and sharding on merge and rewrite module URL: https://github.com/apache/incubator-shardingsphere/pull/3779 For #3691. Changes proposed in this pull request: - Create encrypt-core module - Create underlying module - Decouple encrypt and sharding on rewrite module - Decouple encrypt and sharding on merge module This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-shardingsphere] yuboliang commented on issue #3778: Consistent Hashing
yuboliang commented on issue #3778: Consistent Hashing URL: https://github.com/apache/incubator-shardingsphere/issues/3778#issuecomment-568228861 ok！I will try to change a friendly title，but my English is worst， please forgive me！ ---Original--- From: "Liang Zhang"
[GitHub] [incubator-shardingsphere] terrymanu commented on issue #3778: Consistent Hashing
terrymanu commented on issue #3778: Consistent Hashing URL: https://github.com/apache/incubator-shardingsphere/issues/3778#issuecomment-568228721 Can you change the title for search friendly? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-shardingsphere-benchmark] branch master updated: for performance
This is an automated email from the ASF dual-hosted git repository. zhaoyanan pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-shardingsphere-benchmark.git The following commit(s) were added to refs/heads/master by this push: new dfacc0c for performance dfacc0c is described below commit dfacc0c36e89f4f5dca682f6123020b27b989d14 Author: nancyzrh AuthorDate: Sun Dec 22 02:46:47 2019 +0800 for performance --- report/data/3.0_single_delete_merge.log_plot| 1 + report/data/3.0_single_insert_merge.log_plot| 1 + report/data/3.0_single_select_merge.log_plot| 1 + report/data/3.0_single_update_merge.log_plot| 1 + report/data/3.0_sp_delete_raw_merge.log_plot| 1 + report/data/3.0_sp_insert_raw_merge.log_plot| 1 + report/data/3.0_sp_select_raw_merge.log_plot| 1 + report/data/3.0_sp_update_raw_merge.log_plot| 1 + report/data/4.0_single_delete_merge.log_plot| 1 + report/data/4.0_single_insert_merge.log_plot| 1 + report/data/4.0_single_update_merge.log_plot| 1 + report/data/4.0_sp_delete_raw_merge.log_plot| 1 + report/data/4.0_sp_insert_raw_merge.log_plot| 1 + report/data/4.0_sp_update_raw_merge.log_plot| 1 + report/data/direct_delete_merge.log_plot| 1 + report/data/direct_update_merge.log_plot| 1 + report/data/encrypt/4.0_sp_delete_enc.log_plot | 1 + report/data/encrypt/4.0_sp_delete_enc_sharding.log_plot | 1 + report/data/encrypt/4.0_sp_insert_enc.log_plot | 1 + report/data/encrypt/4.0_sp_insert_enc_sharding.log_plot | 1 + report/data/encrypt/4.0_sp_update_enc.log_plot | 1 + report/data/encrypt/4.0_sp_update_enc_sharding.log_plot | 1 + report/data/jdbc/3.0_sj_ms_delete.log_plot | 1 + report/data/jdbc/3.0_sj_ms_insert.log_plot | 1 + report/data/jdbc/3.0_sj_ms_select.log_plot | 1 + report/data/jdbc/3.0_sj_ms_sharding_delete.log_plot | 1 + report/data/jdbc/3.0_sj_ms_sharding_insert.log_plot | 1 + report/data/jdbc/3.0_sj_ms_sharding_update.log_plot | 1 + report/data/jdbc/3.0_sj_sharding_delete.log_plot| 1 + report/data/jdbc/3.0_sj_sharding_insert.log_plot| 1 + report/data/jdbc/3.0_sj_sharding_update.log_plot| 1 + report/data/jdbc/4.0_sj_delete_raw.log_plot | 1 + report/data/jdbc/4.0_sj_enc_delete.log_plot | 1 + report/data/jdbc/4.0_sj_enc_delete_sharding.log_plot| 1 + report/data/jdbc/4.0_sj_enc_insert.log_plot | 1 + report/data/jdbc/4.0_sj_enc_insert_sharding.log_plot| 1 + report/data/jdbc/4.0_sj_enc_update.log_plot | 1 + report/data/jdbc/4.0_sj_enc_update_sharding.log_plot| 1 + report/data/jdbc/4.0_sj_insert_raw.log_plot | 1 + report/data/jdbc/4.0_sj_ms_delete.log_plot | 1 + report/data/jdbc/4.0_sj_ms_insert.log_plot | 1 + report/data/jdbc/4.0_sj_ms_sharding_delete.log_plot | 1 + report/data/jdbc/4.0_sj_ms_sharding_insert.log_plot | 1 + report/data/jdbc/4.0_sj_ms_sharding_update.log_plot | 1 + report/data/jdbc/4.0_sj_ms_update.log_plot | 1 + report/data/jdbc/4.0_sj_sharding_delete.log_plot| 1 + report/data/jdbc/4.0_sj_sharding_insert.log_plot| 1 + report/data/jdbc/4.0_sj_sharding_update.log_plot| 1 + report/data/jdbc/4.0_sj_update_raw.log_plot | 1 + report/data/master_slave/3.0_sp_delete_ms.log_plot | 1 + report/data/master_slave/3.0_sp_delete_ms_sharding.log_plot | 1 + report/data/master_slave/3.0_sp_insert_ms.log_plot | 1 + report/data/master_slave/3.0_sp_insert_ms_sharding.log_plot | 1 + report/data/master_slave/3.0_sp_select_ms.log_plot | 1 + report/data/master_slave/3.0_sp_select_ms_sharding.log_plot | 1 + report/data/master_slave/3.0_sp_update_ms.log_plot | 1 + report/data/master_slave/3.0_sp_update_ms_sharding.log_plot | 1 + report/data/master_slave/4.0_sp_delete_ms.log_plot | 1 + report/data/master_slave/4.0_sp_delete_ms_sharding.log_plot | 1 + report/data/master_slave/4.0_sp_insert_ms.log_plot | 1 + report/data/master_slave/4.0_sp_insert_ms_sharding.log_plot | 1 + report/data/master_slave/4.0_sp_update_ms.log_plot | 1 + report/data/master_slave/4.0_sp_update_ms_sharding.log_plot | 1 + report/jtl_json/full_route_test.json| 2 +- report/jtl_json/master_slave_encrypt_sharding_test.json | 2 +- report/jtl_json/master_slave_test.json | 2 +- report/jtl_json/single_route_test.json | 2 +- 67 files changed, 67
[GitHub] [incubator-shardingsphere] yuboliang opened a new issue #3778: Consistent Hashing
yuboliang opened a new issue #3778: Consistent Hashing URL: https://github.com/apache/incubator-shardingsphere/issues/3778 Does Sharding JDBC have "Consistent Hashing " sharding table strategy? Or "Consistent Hashing " need myself to implement it? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
