Fix hive view case sensitivity #52694
Closed
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?
Issue Number: close #52557
Related PR: N/A
Problem Summary:
When querying Hive views through External Catalog, the view SQL text retrieved from Hive Metastore may contain uppercase table names and column names. Since Hive is case-insensitive but Doris may be case-sensitive in certain contexts, this can cause query failures when the view SQL contains mixed case identifiers.
Specific Issues:
SELECT * FROM MyTablebut Doris expectsmytableExample Failure Scenario:
Release note
Fix case sensitivity issue in Hive view SQL processing to ensure reliable querying of Hive views through External Catalog.
Check List (For Author)
Check List (For Reviewer)
Detailed Solution
1. Root Cause Analysis
The issue occurs in the
BindRelationphase when processing Hive views:2. Solution Design
Add HiveViewSqlTransformer utility class to normalize Hive view SQL:
3. Implementation Details
HiveViewSqlTransformer.java
BindRelation.java Integration
4. Test Cases
Basic Case Transformation
Preserve Quoted Strings
Complex Query with Aggregation
5. Before vs After
Before Fix:
After Fix:
6. Performance Impact
7. Compatibility
8. Edge Cases Handled
9. Files Modified
10. Risk Assessment
Risk Level: LOW
Mitigation: