-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sink: fix codec json encoding with non binary string #2764
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests /tikv=pr/10910 |
/run-integration-tests /tikv=pr/10910 |
1 similar comment
/run-integration-tests /tikv=pr/10910 |
Codecov Report
@@ Coverage Diff @@
## master #2764 +/- ##
================================================
+ Coverage 55.4760% 58.9821% +3.5060%
================================================
Files 165 177 +12
Lines 19841 18136 -1705
================================================
- Hits 11007 10697 -310
+ Misses 7786 6478 -1308
+ Partials 1048 961 -87 |
/run-all-tests |
/run-leak-tests |
/run-integration-tests |
/run-integration-tests |
2 similar comments
/run-integration-tests |
/run-integration-tests |
Could you check type assertion in other files? To further prevent similar panics. |
@overvenus .Good suggestion, I added a tracking issue. https://github.com/pingcap/ticdc/issues/2768 |
/cc |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8fd1cbf
|
@amyangfei: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-integration-tests |
6 similar comments
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
In response to a cherrypick label: new pull request created: #2781. |
In response to a cherrypick label: new pull request created: #2782. |
In response to a cherrypick label: new pull request created: #2783. |
In response to a cherrypick label: new pull request created: #2784. |
What problem does this PR solve?
Close #2758
Note we still don't known in which scenario the column value is
string
instead of[]byte
, need more investigation.What is changed and how it works?
The column value type of
mysql.TypeString
,mysql.TypeVarString
,mysql.TypeVarchar
could be eitherstring
or[]byte
, we should consider both of these two types when converting a row column value to json encoding.Check List
Tests
Release note