[Fix](Insert-Job)Resolving Task Status Discrepancies in Query Execution Records #45342
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on Records When querying the execution records of tasks, the current system has two sources that may describe task status: Task status in the scheduling module: Represents the processing status of tasks within the scheduling system. Task status in LoadManager: Specifically refers to the status of Insert-type tasks, containing more detailed execution information. When the data in the LoadManager is deleted or expires, the completion status will revert to the task status from the scheduling system, which could cause confusion. Therefore, consistency needs to be maintained. Since these two sources may have inconsistencies in their status information, they can easily cause confusion for users and developers.
|
run buildall |
github-actions
bot
added
the
approved
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
hubgeter
approved these changes
Dec 13, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Dec 13, 2024
…on Records (#45342) ### What problem does this PR solve? When querying the execution records of tasks, the current system has two sources that may describe task status: Task status in the scheduling module: Represents the processing status of tasks within the scheduling system. Task status in LoadManager: Specifically refers to the status of Insert-type tasks, containing more detailed execution information. When the data in the LoadManager is deleted or expires, the completion status will revert to the task status from the scheduling system, which could cause confusion. Therefore, consistency needs to be maintained. Since these two sources may have inconsistencies in their status information, they can easily cause confusion for users and developers.
CalvinKirs
added a commit
that referenced
this pull request
Dec 16, 2024
…uery Execution Records #45342 (#45405) Cherry-picked from #45342 Co-authored-by: Calvin Kirs <[email protected]>
CalvinKirs
added a commit
to CalvinKirs/incubator-doris
that referenced
this pull request
Dec 16, 2024
…ery Execution Records (apache#45342) (cherry picked from commit 41e554d) apache#45432
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
When querying the execution records of tasks, the current system has two sources that may describe task status:
Task status in the scheduling module: Represents the processing status of tasks within the scheduling system.
Task status in LoadManager: Specifically refers to the status of Insert-type tasks, containing more detailed execution information.
When the data in the LoadManager is deleted or expires, the completion status will revert to the task status from the scheduling system, which could cause confusion. Therefore, consistency needs to be maintained.
Since these two sources may have inconsistencies in their status information, they can easily cause confusion for users and developers.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)