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

   ## Bug Report
   
   **For English only**, other languages will not accept.
   Error reported when JSON data exists during incremental migration
   
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   4.2.1
   
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   Incremental migration is executing normally
   
   ### Actual behavior
   Incremental migration not executed
   
   ### Reason analyze (If you can)
   Incremental migration may convert `\\r` to `\r` when reading binlog logs
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   1, setup proxy cluster use hell
   2, create a source table with json colum
   3, start migrate this table and complete migration all the rows
   4, then insert a row with and row's json field value contains \ r
   5, incremental migration should failed with error
   
   
   ### 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

Reply via email to