-
Notifications
You must be signed in to change notification settings - Fork 287
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/mysql: explicit_defaults_for_timestamp compatibility with mysql (#1638) #1659
sink/mysql: explicit_defaults_for_timestamp compatibility with mysql (#1638) #1659
Conversation
Signed-off-by: ti-srebot <[email protected]>
/run-all-tests |
/run-all-tests |
/run-kafka-tests |
/lgtm |
[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 writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 19a5d95
|
/run-check-release-note |
/run-integration-tests |
@ti-srebot: 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. |
/lgtm |
/run-all-tests |
cherry-pick #1638 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In ticdc repo: git pr https://github.com/pingcap/ticdc/pull/1659
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Fix #1585
What is changed and how it works?
explicit_defaults_for_timestamp
toON
in MySQL sink, which will keep the same behavior between upstream TiDB and downstream MySQL 5.7.explicit_defaults_for_timestamp
in downstream isOFF
, because in TiDB variableexplicit_defaults_for_timestamp
is readonly.Check List
Tests
Related changes
Release note
explicit_defaults_for_timestamp
toON
to make downstream MySQL5.7 keeps the same behavior with upstream TiDB.