-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-50116][SQL] Assign appropriate error condition for _LEGACY_ERROR_TEMP_2067
: UNSUPPORTED_PARTITION_TRANSFORM
#48655
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
be71534
[SPARK-50016][SQL] Assign appropriate error condition for _LEGACY_ERR…
itholic 30eb69d
Improve error message
itholic 17cfccc
Merge branch 'master' of https://github.com/apache/spark into LEGACY_…
itholic 8e5f8f6
Merge branch 'master' of https://github.com/apache/spark into LEGACY_…
itholic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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.
Isn't
transform
an expression actually. If so, please, usetoSQLExpr
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.
I tried it but unfortunately it says
Transform
is not anExpression
:Is there happen to any way converting
Transform
toExpression
?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.
ah, I see.
Transform
extends anotherExpression
fromorg.apache.spark.sql.connector.expressions
. Could you add one more definition oftoSQLExpr
which acceptconnector.expressions.Expression
. It should quote in the same way as the existingtoSQLExpr
(usingquoteByDefault
).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.
Sure will add it. Thanks for the comment!
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.
Hi, @MaxGekk I just realized during addressing the comment that we also should add all internal functions such as
toPrettySQL(e: Expression)
,usePrettyExpression(e: Expression)
,Expression.sql
,transform
,dataType
, etc. that are used byquoteByDefault
internally.I believe the number of changes and complexity would not be very trivial so maybe we better open separate ticket and discuss there?
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.
I see. thank you for the investigation.