You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/04/26 06:29:25 UTC
[GitHub] [shardingsphere] 243006306 opened a new issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
243006306 opened a new issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196
The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
1. Why does hint still need to go through the parsing process? Because my SQL is relatively complex (subquery, Union). Now if I find that the problem can not be resolved, I will randomly select a data source and do not enter the hash function of the hint algorithm. This makes me puzzled. I feel that if I can't resolve it, I can throw out the exception, A data source should not be randomly selected, and the hint mode should be able to skip the parsing process and merging process.
2. When I only split the database, the default partition rule does not take effect. I need to configure actual data nodes. I have hundreds of tables in a database. I think this is unreasonable. I should use wildcards, or if it is not configured by default, it is the whole database, or add and exclude some tables to configure.
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] RaigorJiang commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
RaigorJiang commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-827489397
Hi @243006306
Could you please provide a configuration and SQL, so we can reproduce 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:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-828108524
Configuration is like this ：
`spring.shardingsphere.sharding.binding-tables[0]=A,B
spring.shardingsphere.sharding.tables.A.actual-data-nodes=
spring.shardingsphere.sharding.tables.B.actual-data-nodes=
spring.shardingsphere.sharding.default-database-strategy.hint.algorithm-class-name=com.szjz.cloud.algorithm.IdHintAlgorithm
`
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-828110932
我DEBUG测试发现解释SQL失败，所以选择了随机数据源的路由，就像未指定默认数据源启动项目后发送的ping SQL测试所走的路由一样，我想`HINT`模式不经过解析，直接走向我的`HintAlgorithm`类，因为我只需要分库，我测试发现去除最外层包裹的`SELECT X.X FROM `，就可以解析成功并走向自定义的`HintAlgorithm`分片算法,我很疑惑，为什么解析失败不报错
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-829929054
@tristaZero My debug observation did not report an error, because there was a sub query in SQL that could not parse the table name, resulting in routing to the random data source
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] tristaZero commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-829926839
Hi, have you ever check the log? Is there any exception info?
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-828110459
My debug test found that the interpretation of SQL failed, so I chose the route of the random data source, just like the route of the Ping SQL test sent after starting the project without specifying the default data source. I want the 'hint' mode to go directly to my 'hintalgorithm' class without parsing, because I only need the sub database. I found that the 'select x.x from' with the outermost package removed, You can parse successfully and go to the custom 'hintalgorithm' slicing algorithm. I wonder why the parsing fails without reporting an error
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] tristaZero commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-830776202
Hi, `sub query` is supported better from the 5.x release, could you try the 5.0.0-alpha?
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-828107404
SQL is like this `SELECT x.column_1,x.column_2 FROM( SELECT a.column_1,o.column_2 FROM A a INNER JOIN b b ON b.id = a.order_id AND b.mof_id = 'xxxxxx' WHERE a.xxx='xxx' and b.xxx='xxx' UNION SELECT a.column_,o.column_1 FROM A a INNER JOIN b b ON b.id = a.order_id AND b.mof_id = 'xxxxxx' WHERE a.xxx='xxx' and b.xxx='xxx') x order by column_1,column_2 `
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] terrymanu closed issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] 243006306 commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
243006306 commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-827352268
Force routing does not work, do not enter 'HintShardingAlgorithm`
--
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:
users@infra.apache.org
[GitHub] [shardingsphere] terrymanu commented on issue #10196: The following problems are found in the project transformation sharding-jdbc 4.1.1 scheme
Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #10196:
URL: https://github.com/apache/shardingsphere/issues/10196#issuecomment-927275966
Closed because of no response anymore.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org