cheese8 opened a new issue #13634: URL: https://github.com/apache/shardingsphere/issues/13634
## The purpose: 1、Enhance users' confidence in using SS. 2、Reduce test coverage and workload in using SS. ## Scenarios: Encrypt only. Why an optional parse skipped parse could enhance user confidence? 1、Encrypt and decrypt are generally compliance requirements, and when your system needs compliance, which means it is already large and the situation is complicated, for example, no unit test or unit test is not enough etc. Do you agree with this? 2、Then are there a lot of SQLs, and there are some SQLs containing encrypt tables/fields, others not at all. It is the reality. 3、The first solution is developers manually modify the SQLs which containing encrypt tables/fields one by one, it is the most simple, direct and easiest to accept solution, as the scope that needs to be developed and tested is fixed. Do you agree with this? 4、The SS's encrypt solution is almost perfect, but: > all SQLs should be parsed and some SQLs are not parsed well. > all SQLs need to be parsed, which cause the unacceptable by test. If SS says that only the SQLs which containing encrypt tables/fields is parsed and rewritten, the other SQLs parse phase can be skipped. Do you agree with this? Look forward to your opinions @strongduanmu @tristaZero @terrymanu -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
