-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does actual-data-nodes work without specifying physical tables explicitly? #32591
Comments
The locking issue was just a mistake of hand. Can you debug the variables actualTarget and availableTargetNames? That sounds kind of weird. |
I have debugged the variables availableTargetNames and actualTarget as you suggested. Thank you for your help. |
|
I have observed an unexpected behavior in ShardingSphere's table sharding configuration. My configuration doesn't explicitly specify all physical tables, yet it works correctly. I'm trying to understand why this is possible.
Here's my current configuration and sharding code:
In my database, I have four physical tables: agreement_0, agreement_1, agreement_2, and agreement_3. However, in my configuration, I've only specified actual-data-nodes: ds0.agreement instead of actual-data-nodes: ds0.agreement_$->{0..3}.
Despite this, my sharding setup works correctly. The system successfully routes queries to the appropriate physical tables.
My questions are:
Is there some default behavior in ShardingSphere that I'm not aware of, or is it related to my custom sharding algorithm?
Thank you.
The text was updated successfully, but these errors were encountered: