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
DATA_NODE_SUFFIX_PATTERN implies a regex pattern to match all numbers, it then wrongly identifies the matching number as table name suffix even if the number is part of the actual tablename.
Eg : Suppose I have a table named AllPatientsV1 ... it returns AllPatientsV as prefix and suffix length as 1, thinking the 1, in the end, was a suffix but it is part of the table name.
This prevents me from adding bindingtableRules since ShardingRule.isValidActualTableName() returns false when contains a table like AllPatientsV1.
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:
Bug Report
Which version of ShardingSphere did you use?
5.4.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
TableRule.createTableDataNode() returns the correct value.
Actual behavior
TableRule.createTableDataNode() returns value with all number omitted
Reason analyze (If you can)
DATA_NODE_SUFFIX_PATTERN
implies a regex pattern to match all numbers, it then wrongly identifies the matching number as table name suffix even if the number is part of the actual tablename.Eg : Suppose I have a table named AllPatientsV1 ... it returns AllPatientsV as prefix and suffix length as 1, thinking the 1, in the end, was a suffix but it is part of the table name.
This prevents me from adding bindingtableRules since
ShardingRule.isValidActualTableName()
returnsfalse
when contains a table like AllPatientsV1.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: