-
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
redo(ticdc): use uuid in s3 log file to avoid name conflict (#5595) #5613
redo(ticdc): use uuid in s3 log file to avoid name conflict (#5595) #5613
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has not been approved. 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 |
/run-integration-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9957db2
|
@ti-chi-bot: 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-dm-integration-test |
This is an automated cherry-pick of #5595
What problem does this PR solve?
Issue Number: ref #5486
What is changed and how it works?
commit-ts
, the file name will be conflict and lead to data lossgithub.com/pingcap/tiflow/engine/pkg/uuid
package togithub.com/pingcap/tiflow/pkg/uuid
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note