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 2019/05/06 08:19:16 UTC
[GitHub] [incubator-shardingsphere] lalicw opened a new issue #2328:
ParsingResultCache should be changed when sharding data source was
reconstruct
lalicw opened a new issue #2328: ParsingResultCache should be changed when sharding data source was reconstruct
URL: https://github.com/apache/incubator-shardingsphere/issues/2328
## Bug Report
When we try to reconstrcut the sharding data source because of the table sharding state has been changed.(from not sharding to sharding)
the ParsingResultCache was not cleared because it is static instance and not associated with the sharding data source.
Please answer these questions before submitting your issue. Thanks!
### Which version of ShardingSphere did you use?
3.1.0
### Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
### Expected behavior
ParsingResultCache for sql will be clean
### Actual behavior
not clean
### Reason analyze (If you can)
1.create a sharding data source
2.use sql "select count(1) from xxx where a = 'x'", now xxx table is not in sharding
3.do table sharding in the database and reconstruct sharding data source without restart
4.the route result is not correct, still to all the shards
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
### 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
With regards,
Apache Git Services