dongyun-coder opened a new issue, #35529:
URL: https://github.com/apache/shardingsphere/issues/35529
### Which version of ShardingSphere did you use?
5.5.3-SNAPSHOT
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
binlog parse error
### Actual behavior
binlog parse ok
### Reason analyze (If you can)
mysql column type is json specical case parse error
### Steps to reproduce the behavior
CREATE TABLE `reproduce_json_parse_error`
(
`id` bigint NOT NULL AUTO_INCREMENT,
`settlement_assets` json NOT NULL,
PRIMARY KEY (`id`)
) ENGINE = InnoDB;
insert into reproduce_json_parse_error(settlement_assets) values('null');
org.apache.shardingsphere.infra.exception.generic.UnsupportedSQLOperationException:
Unsupported SQL operation: 4.
### More
when parse error， binlog client is corrupt，
now binlog implement skip parse error event without skip unresloved byte,
and continue to parse , which is wrong
--
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]
