Update the error message to be checked for 330 #5705
Closed
Conversation
This file contains 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
Signed-off-by: Firestarman <firestarmanllc@gmail.com>
|
build |
|
If this is 3.3.0 why isn't it targetted for 22.06? Also please be more specific in description about what error message has changed and preferrably point to the spark issue that has changed the error message. |
I found the PR and updated the description. This piece of code is different from 06, who has no branch for Spark 340. I will file another PR for it. |
Signed-off-by: Firestarman <firestarmanllc@gmail.com>
|
Here it is #5718 for 22.06 |
|
build |
|
Closing this, since #5718 will be picked into 08 by automation, and it will conflict. We can get this done by fixing the conflict. |
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.
PR #5675 updated the error message before but according to the old Spark 3.3.0 snapshot jars (May 3).
While spark 3.3.0 release is still being produced, and the error message has been changed by apache/spark#36428 according to its development branch
branch-3.3.Signed-off-by: Firestarman firestarmanllc@gmail.com