-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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
[SPARK-4225][SQL] Resorts to SparkContext.version to inspect Spark version #3105
Conversation
Test build #22917 has started for PR 3105 at commit
|
Test build #22917 has finished for PR 3105 at commit
|
Test PASSed. |
@liancheng, you need rebase this:) |
@scwf Thanks for reminding, rebased. |
Test build #23053 has started for PR 3105 at commit
|
Test build #23053 has finished for PR 3105 at commit
|
Test PASSed. |
LGTM. |
Thanks! Merged to master and 1.2. |
…rsion This PR resorts to `SparkContext.version` rather than META-INF/MANIFEST.MF in the assembly jar to inspect Spark version. Currently, when built with Maven, the MANIFEST.MF file in the assembly jar is incorrectly replaced by Guava 15.0 MANIFEST.MF, probably because of the assembly/shading tricks. Another related PR is #3103, which tries to fix the MANIFEST issue. Author: Cheng Lian <lian@databricks.com> Closes #3105 from liancheng/spark-4225 and squashes the following commits: d9585e1 [Cheng Lian] Resorts to SparkContext.version to inspect Spark version (cherry picked from commit 86e9eaa) Signed-off-by: Michael Armbrust <michael@databricks.com>
This PR resorts to
SparkContext.version
rather than META-INF/MANIFEST.MF in the assembly jar to inspect Spark version. Currently, when built with Maven, the MANIFEST.MF file in the assembly jar is incorrectly replaced by Guava 15.0 MANIFEST.MF, probably because of the assembly/shading tricks.Another related PR is #3103, which tries to fix the MANIFEST issue.