[GitHub] [shardingsphere] azexcy opened a new issue, #25362: Increment task failed when using table without unique keys of migration

[via GitHub]

azexcy opened a new issue, #25362:
URL: https://github.com/apache/shardingsphere/issues/25362

   ## Bug Report
   
   When migration table without primary key,  increment task failed because of 
delete records parse failed
   
   <img width="1027" alt="image" 
src="https://user-images.githubusercontent.com/101622833/234808310-160aa751-9a9a-458a-82fc-dadad8739682.png";>
   
   <img width="1276" alt="image" 
src="https://user-images.githubusercontent.com/101622833/234809715-1d69fe32-a4a8-4146-8172-35c5f47d6637.png";>
   
   ### Which version of ShardingSphere did you use?
   
   master 
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-Proxy
   
   ### Expected behavior
   
   ### Actual behavior
   
   ### 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).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
notifications-unsubscr...@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org