[Enhancement] Replace 'Unknown error' with detailed view error messages #62473
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
| try { | ||
| logicalPlan = transform(node.getQueryStatement().getQueryRelation()); | ||
| } catch (Exception e) { | ||
| String viewName = node.getName() != null ? node.getName().toSql() : "unknown"; |
There was a problem hiding this comment.
I remember that error msg has already been printed in the connector view. wha't the e.getMessage in this block.
There was a problem hiding this comment.
The error received in the mysql client is Unknown error。
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.
Why I'm doing:
Users encounter confusing "Unknown error" messages when Hive view queries fail, making it difficult to diagnose and fix issues.
What I'm doing:
Replace generic "Unknown error" with detailed, actionable error messages for Hive view queries:
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: