Fix spark lambdas#65
Merged
vertical-blank merged 2 commits intovertical-blank:masterfrom May 25, 2023
Merged
Conversation
vertical-blank
approved these changes
May 25, 2023
vertical-blank
requested changes
May 25, 2023
Owner
vertical-blank
left a comment
There was a problem hiding this comment.
@NathanEckert
Thanks for the PR.
Could you please run mvn spotless:apply and format the code?
Contributor
Author
Done |
Owner
|
LGTM |
Owner
|
@NathanEckert |
Contributor
Author
Thanks a lot ! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR solves the following issue:
In Spark SQL, it is possible to use lambda.
However, the formatter is breaking valid SQL statements:
The output is:
In order to be valid Spark SQL, the symbol
->should be kept as a whole and not split into- >