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/03/23 18:30:17 UTC

[GitHub] [shardingsphere] jiang-wei opened a new issue #9792: SS cannot configure default non-sharding policy for newly created tables

jiang-wei opened a new issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792


   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response anymore and we cannot reproduce it on current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   5.0.0-alpha
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   SS-jdbc
   ### Expected behavior
   apply default non-sharding policy for newly created tables
   ### Actual behavior
   "Cannot route table for xxx, please make sure the tables are in the same schema"
   
   ### Reason analyze (If you can)
   configured two datasources in spring boot.
   one for liquibase & the other for hibernate & SS
   
   they are both created and liquibase needs some time to create the tables.
   
   Once tables created, SS complains "cannot route" for the newly created table
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   1. create a table directly in the database, not through SS
   2. query that table
   ### Example codes for reproduce this issue (such as a github link).
   
   link: #9782 


-- 
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] jiang-wei commented on issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
jiang-wei commented on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-805159014


   Log:
   
   ```
   2021-03-23 14:48:46.199  INFO 93803 --- [           main] ShardingSphere-metadata                  : Loading 0 tables' meta data for unconfigured tables.
   ```


-- 
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] jiang-wei edited a comment on issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
jiang-wei edited a comment on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-805143965


   I run liquibase scripts with another datasource because #9774 , SS cannot create sequence...


-- 
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] jiang-wei commented on issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
jiang-wei commented on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-805143965


   I run liquibase scripts with another datasource because #9774 


-- 
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 #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
RaigorJiang commented on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-927276711


   When the system is running, the single table created outside of SS will not be perceived. 
   This is not supported and does not conform to the design.


-- 
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] jiang-wei edited a comment on issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
jiang-wei edited a comment on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-805180499


   BTW, I found a way to fool SS to "create" the tables 
   just run `create table` in SS like
   ```
   create table foo if not exists (u_id BIGINT);
   ```
   then SS will configure it with default non-sharding policy 
   
   😎😎😎


-- 
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 #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-808868474


   You can run `create table`  with ShardingSphere. So the question is about `create sequence`, isn't 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] jiang-wei commented on issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
jiang-wei commented on issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792#issuecomment-805180499


   BTW, I found a way to fool SS to "create" the tables 
   just like
   ```
   create table foo if not exists (u_id BIGINT);
   ```
   then SS will configure it with default non-sharding policy 
   
   😎😎😎


-- 
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 closed issue #9792: SS cannot configure default non-sharding policy for newly created tables from outside SS

Posted by GitBox <gi...@apache.org>.
RaigorJiang closed issue #9792:
URL: https://github.com/apache/shardingsphere/issues/9792


   


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