-
Notifications
You must be signed in to change notification settings - Fork 28.8k
[SPARK-42841][SQL]Assign a name to the error class _LEGACY_ERROR_TEMP_2005 #51110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
"message" : [ | ||
"Type <dataType> does not support ordered operations." | ||
], | ||
"sqlState" : "0A000" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @MaxGekk FYI
Is this sqlState
correct?
friendly ping @MaxGekk |
also cc @srielau |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. 0A000 seems appropriate given that order can always(?) be defined later.
needs to be rebased. |
okk, ing. Thanks! |
…P_2005 ### What changes were proposed in this pull request? see https://issues.apache.org/jira/browse/SPARK-42841, replace _LEGACY_ERROR_TEMP_2005 with a meaningful name. Some points: - To make sure full UT coverage, method with "datatype" is refactored to call another one with "string". - sqlStat '0A000' means NOT_SUPPORTED or CANNOT. ### Why are the changes needed? see https://issues.apache.org/jira/browse/SPARK-42841 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? UT ### Was this patch authored or co-authored using generative AI tooling? No Closes apache#51110 from yuexing/SPARK-42841-2005. Lead-authored-by: xingyue <xingyue@baidu.com> Co-authored-by: Yue <xingyue@baidu.com> Signed-off-by: yangjie01 <yangjie01@baidu.com>
What changes were proposed in this pull request?
see https://issues.apache.org/jira/browse/SPARK-42841, replace _LEGACY_ERROR_TEMP_2005 with a meaningful name. Some points:
Why are the changes needed?
see https://issues.apache.org/jira/browse/SPARK-42841
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT
Was this patch authored or co-authored using generative AI tooling?
No