[SPARK-38110] Use error classes in the compilation errors of windows

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.3.0
• Component/s: SQL
• Assignee: Unassigned
• Reporter: Max Gekk
• Shepherd: Max Gekk
• Created: 04/Feb/22 16:43
• Updated: 07/Apr/22 11:28

Description

Migrate the following errors in QueryCompilationErrors:

• windowSpecificationNotDefinedError
• windowAggregateFunctionWithFilterNotSupportedError
• windowFunctionInsideAggregateFunctionNotAllowedError
• expressionWithoutWindowExpressionError
• expressionWithMultiWindowExpressionsError
• windowFunctionNotAllowedError
• cannotSpecifyWindowFrameError
• windowFrameNotMatchRequiredFrameError
• windowFunctionWithWindowFrameNotOrderedError
• multiTimeWindowExpressionsNotSupportedError
• sessionWindowGapDurationDataTypeError
• invalidLiteralForWindowDurationError
• emptyWindowExpressionError
• foundDifferentWindowFunctionTypeError

onto use error classes. Throw an implementation of SparkThrowable. Also write a test per every error in QueryCompilationErrorsSuite.

Feel free to split this to sub-tasks.

Issue Links

• is cloned by: SPARK-38687 Use error classes in the compilation errors of generators
• is related to: SPARK-38296 Error Classes AnalysisException is not propagated in FunctionRegistry