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
For English only, other languages will not accept.
When I use ShardingSphere-proxy for data migration, when the table name is a keyword, such as user or unit, when I use the command:
"MIGRATE TABLE ds_0.user INTO user"
The migration task fails to be created with the following error: ERROR 1064 (42000): You have an error in your SQL syntax: no viable alternative at input 'MIGRATE' near '[@0,0:6='MIGRATE',<449>,1:0]' at line 1.
When I changed it to
“MIGRATE TABLE ds_0.user INTO user”
The task can be created successfully, but the following error message is displayed in the log:
Can not get meta data for table 'user' when split by range.
This seems to be a bug, can you fix this problem?
The text was updated successfully, but these errors were encountered:
I noticed the issue regarding migration failure when using reserved keywords like user or unit as table names. This seems to be related to syntax handling and metadata fetching in ShardingSphere-Proxy during migration tasks.
I'd like to contribute by investigating and resolving this issue. Could you please assign it to me? I’ll ensure to follow the contribution guidelines and provide a detailed solution.
Bug Report
For English only, other languages will not accept.
When I use ShardingSphere-proxy for data migration, when the table name is a keyword, such as user or unit, when I use the command:
"MIGRATE TABLE ds_0.user INTO user"
The migration task fails to be created with the following error: ERROR 1064 (42000): You have an error in your SQL syntax: no viable alternative at input 'MIGRATE' near '[@0,0:6='MIGRATE',<449>,1:0]' at line 1.
When I changed it to
“MIGRATE TABLE ds_0.
user
INTOuser
”The task can be created successfully, but the following error message is displayed in the log:
Can not get meta data for table '
user
' when split by range.This seems to be a bug, can you fix this problem?
The text was updated successfully, but these errors were encountered: