nada-attia opened a new issue, #18151: URL: https://github.com/apache/hudi/issues/18151
### Describe the problem you faced When Spark SQL queries contain unresolved columns or tables (e.g., typos, missing table definitions), users receive a cryptic error message like "Invalid call to dataType on unresolved object" which provides no actionable information to identify and fix the issue. ### Describe the solution you'd like Improve error handling in Hudi's Spark SQL analysis phase to catch `UnresolvedException` and provide user-friendly error messages that help users identify and fix the issue. The error message should include: - List of unresolved references found in the query - Suggestions to check for typos, missing table definitions, incorrect schema references - Original error message for debugging Example improved error message: ``` Failed to resolve query. The query contains unresolved columns or tables. Unresolved references: [nonexistent_column]. Please check for: (1) typos in column or table names, (2) missing table definitions, (3) incorrect database/schema references, (4) columns that don't exist in the source tables. ``` ### Describe alternatives you've considered Leaving the current error messages, but this results in poor user experience and difficulty debugging query issues. ### Additional context Implementation PR: #18147 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
