Closed mergify[bot] closed 2 days ago
Cherry-pick of c68222ccf477345a815468afa6c179e64c267844 has failed:
On branch mergify/bp/branch-3.2/pr-50334
Your branch is up to date with 'origin/branch-3.2'.
You are currently cherry-picking commit c68222ccf4.
(fix conflicts and run "git cherry-pick --continue")
(use "git cherry-pick --skip" to skip this patch)
(use "git cherry-pick --abort" to cancel the cherry-pick operation)
Changes to be committed:
modified: fe/fe-core/src/main/java/com/starrocks/load/routineload/RoutineLoadJob.java
modified: fe/fe-core/src/main/java/com/starrocks/load/routineload/RoutineLoadTaskScheduler.java
modified: fe/fe-core/src/test/java/com/starrocks/load/routineload/RoutineLoadTaskSchedulerTest.java
Unmerged paths:
(use "git add/rm <file>..." as appropriate to mark resolution)
deleted by us: fe/fe-core/src/test/java/com/starrocks/load/routineload/RoutineLoadJobMetaTest.java
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Why I'm doing:
when runs routineLoadTaskInfo.createRoutineLoadTask got txn timeout cleared, routine load job unexpectly changed to cancelled state
fe master log
bug happened time order
What I'm doing:
change routine load job to cancelled state only when exception message is db does not exist or table does not exist
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #50334 done by Mergify.
Why I'm doing:
when runs routineLoadTaskInfo.createRoutineLoadTask got txn timeout cleared, routine load job unexpectly changed to cancelled state
fe master log
bug happened time order
What I'm doing:
change routine load job to cancelled state only when exception message is db does not exist or table does not exist
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: