justbk2015 opened a new issue #12813:
URL: https://github.com/apache/shardingsphere/issues/12813


   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   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?
   master
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   proxy
   ### Expected behavior
   1. date/text/varchar2/time/bit/bytea/raw type can normal migrate from 2pcs 
proxy two 3pcs proxy.
   ### Actual behavior
   1. some convert format Exception reported in scaling increatemt task. 
   ### Reason analyze (If you can)
   most error because  replication data in mppdb_decoding was in quote 'xx', 
but MppdbDecodingPlugin not dispose it.
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   1. start scaling and proxy
   2. create a scaling task, the task table contain the issue type
   3. add increatement data, such as  date/text/varchar2/time/bit/bytea/raw 
type data
   4. look at proxy log, we can get some convert Exception.
   ### Example codes for reproduce this issue (such as a github link).
   see: [test 
code](https://gitee.com/justbk/jdbc_test/blob/master/src/test/java/ReplicationTest.java)
   in testReplication function.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to