[fix][EC][spark] resolve spark engine task execution failures and optimize logging#992
Open
[fix][EC][spark] resolve spark engine task execution failures and optimize logging#992
Conversation
This file contains hidden or 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
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 is the purpose of the change
Background/Problem:
Currently, spark engine tasks fail during execution due to null pointer exceptions in logging initialization and exception handling issues. Additionally, dependency injection failures and inconsistent error logging affect system stability.
Purpose of Change:
To address these problems, this PR optimizes logging output, fixes spark init SQL exception handling, resolves dependency injection failures, and improves exception comments across multiple engine executors.
Value/Impact:
After the change, spark engine tasks execute more reliably with better error handling and logging, improving system stability and debugging capability.
Related issues/PRs
Related issues: close apache#5284
Related pr:none
Brief change log
Checklist