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/09/14 02:10:40 UTC

[GitHub] [shardingsphere] xfyang1988 opened a new issue #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

xfyang1988 opened a new issue #7430:
URL: https://github.com/apache/shardingsphere/issues/7430


   


----------------------------------------------------------------
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 #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

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


   Parsing-phase for ShardingSphere is MUST-BE now. No way to avoid 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] kimmking closed issue #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

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


   


----------------------------------------------------------------
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 #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

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


   > > @xfyang1988 If so, I suggest you configure the `non-sharding` table with `NoneShardingStratergy`. Plus, `defaultDataSource` is for the `non-sharding` table as well.
   > 
   > Even if "defaultDataSource" or "NoneShardingStratergy" is configured, this kind of table that does not require sharding will need to be parsed by ShardingSphere. I have configured the defaultDataSource now, but the tables that do not need to be sharded will still be parsed by ShardingSphere, which results in slow first parsing
   
   Hi @xfyang1988 
   Only by parsing this SQL it is possible for ShardingSphere to know your table is a sharding table or not. Therefore, SQL parsing is necessary. Actually, parsed SQL will be cached for the next request, which will help weaken parsing's side effects.
   
   Best,
   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] xfyang1988 commented on issue #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

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


   > @xfyang1988 If so, I suggest you configure the `non-sharding` table with `NoneShardingStratergy`. Plus, `defaultDataSource` is for the `non-sharding` table as well.
   
   Even if "defaultDataSource" or "NoneShardingStratergy" is configured, this kind of table that does not require sharding will need to be parsed by ShardingSphere. I have configured the defaultDataSource now, but the tables that do not need to be sharded will still be parsed by ShardingSphere, which results in slow first parsing


----------------------------------------------------------------
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 #7430: How to configure non-separated tables without ShardingSphere for SQL parsing？

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


   @xfyang1988 If so, I suggest you configure the `non-sharding` table with `NoneShardingStratergy`. Plus, `defaultDataSource` is for the `non-sharding` table as well.


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