terrymanu commented on issue #38693: URL: https://github.com/apache/shardingsphere/issues/38693#issuecomment-4545639643
Hi @daoxincc, thanks for the question. This configuration is not supported by the current Encrypt rule model. `assistedQuery` and `likeQuery` are not two aliases of the same physical column. They represent two different derived-column roles: - `assistedQuery` is used for equivalent-query support. - `likeQuery` is used for `LIKE` query support. Therefore they should be mapped to different physical columns. If two different algorithms are used, one physical column cannot store both derived values at the same time. If the same algorithm is used, the current rule model still does not define one physical column as both the assisted-query column and the like-query column. The SQL rewrite engine handles these two slots independently, so generating both columns is expected behavior under the current design. So this is not considered a bug in ShardingSphere-JDBC 5.5.3. Please configure separate physical columns for `assistedQuery.name` and `likeQuery.name`. If there is a concrete use case for one derived column to support both equivalent query and `LIKE` query, please open a separate enhancement discussion with the expected algorithm semantics, write behavior, and compatibility considerations. For this issue, I suggest closing it as invalid usage / question. -- 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]
