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 2020/07/17 10:31:31 UTC
[GitHub] [shardingsphere] waterMeteors opened a new issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
waterMeteors opened a new issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376
### Which version of ShardingSphere did you use?
the version is 4.1.0.
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
I user ShardingShpere-Proxy project.
### Expected behavior
Return sql statement to query normal data
### Actual behavior
Return statement is Table 'schemaName.tableName' doesn't exist. for example :'Table 'test.example_order' doesn't exist'.
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
The sharding rule file is :
------------
schemaName: test
dataSources:
ds0:
url: jdbc:mysql://ip地址:8809/test
username: root
password: 密码
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
ds1:
url: jdbc:mysql://ip地址:8809/test
username: root
password: 密码
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
shardingRule:
tables:
example_order:
actualDataNodes: ds${0..1}.example_order${0..1}
tableStrategy:
inline:
shardingColumn: order_id
algorithmExpression: example_order${order_id % 2}
keyGenerator:
type: SNOWFLAKE
column: order_id
bindingTables:
- example_order
defaultDatabaseStrategy:
inline:
shardingColumn: user_id
algorithmExpression: ds${user_id % 2}
defaultTableStrategy:
none:
------------
The statement error when i execute "select * from (select * from example_order) aa " in navicat. if i execute "select * from example_order" that is ok.
### Example codes for reproduce this issue (such as a github link).
----------------------------------------------------------------
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] waterMeteors commented on issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
waterMeteors commented on issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376#issuecomment-662215257
Thank you very much @jingshanglu.I will update source code in master branch
----------------------------------------------------------------
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] jingshanglu commented on issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
jingshanglu commented on issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376#issuecomment-662203387
@waterMeteors @kimmking @tristaZero Now, master branch has fixed it, new version will fix 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] waterMeteors commented on issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
waterMeteors commented on issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376#issuecomment-660437118
I will clone latest source code for dubbug to see the specific reasons. Directly upgrading the version may affect our previous services. Thank you very mach @kimmking
----------------------------------------------------------------
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] kimmking commented on issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376#issuecomment-660083996
Do you try 4.1.1 ?
----------------------------------------------------------------
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 #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376#issuecomment-660784315
Hi @waterMeteors
Thanks for your feedback. I am afraid `subquery` could not work well at the latest release. If it is available, you'd better debug it on our `master branch` which provides better support for `subquery`.
Welcome your tests.
Trista
----------------------------------------------------------------
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 closed issue #6376: ShardingSphere-Proxy Nested query exception in mysql data source
Posted by GitBox <gi...@apache.org>.
tristaZero closed issue #6376:
URL: https://github.com/apache/shardingsphere/issues/6376
----------------------------------------------------------------
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