You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sharding does not support configuring ActualDataNodes to ${01.. 02}. If I want to split the table by month, regardless of year, how should I configure it
#26111
Closed
ThisOnly opened this issue
Jun 8, 2023
· 3 comments
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.1.2
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
The above configuration can be executed correctly
Actual behavior
error
Reason analyze (If you can)
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).
The text was updated successfully, but these errors were encountered:
In fact you can use Groovy Shell to verify, I think you want to use 0${1..2} instead of ${01..02}.
For the second question, there is actually no need to consider Groovy syntax. You can directly dynamically modify the actualDataNodes through DistSQL, or take out the ContextManager and modify it manually.
Bug Report
Configure the table according to the following diagram, but it cannot be successful. Why is it
For English only, other languages will not accept.
Before report a bug, make sure you have:
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.1.2
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
The above configuration can be executed correctly
Actual behavior
error
Reason analyze (If you can)
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).
The text was updated successfully, but these errors were encountered: