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/12/02 06:32:49 UTC

[GitHub] [incubator-shardingsphere] crazyrunner01 opened a new issue #3634: sharding-jdbc If the query does not have a sharding condition, then the full route is taken. Could this process be more flexible?

crazyrunner01 opened a new issue #3634: sharding-jdbc If the query does not have a sharding condition, then the full route is taken. Could this process be more flexible?
URL: https://github.com/apache/incubator-shardingsphere/issues/3634
 
 
   i think If you choose sub-database and sub-table, then your business volume must be very large. If the business data of a single table in the transaction database exceeds 10 million, sub-tables will be used, and you also sub-database, the transaction data should exceed 100 million At this time, if it is a query without a partition key, such an access request should be rejected from the access middleware.
   
   Once such a request is sent to the database, it may consume a lot of database resources and cause business damage.
   

----------------------------------------------------------------
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