Distributed SQL transaction & query engine for data sharding, scaling, encryption, and more - on any database.
19.83k
stars
6.71k
forks
source link
Is it possible to detect unmatched DATANODES and DATABASE_STRATEGY / TABLE_STRATEGY for tables rule #18424
Open
sandynz opened 2 years ago
Feature Request
Is your feature request related to a problem?
Yes
Describe the feature you would like.
I've found several times in GitHub issues and our forums, unmatched DATANODES and DATABASE_STRATEGY / TABLE_STRATEGY might cause issue.
Is it possible to detect unmatched DATANODES and DATABASE_STRATEGY / TABLE_STRATEGY for tables rule?
2 examples that cause issue
Example 1:
DATANODES("ds_${0..1}.t_order_0")
is wrong, it should beDATANODES("ds_${0..1}.t_order_${0..1}")
, but it's not detected.Example 2:
Possible solution?
It might be difficult to detect it, since we could not iterate all values and evaluate
algorithm-expression
to get all data nodes.Any ideas?