Uh oh!
There was an error while loading. Please reload this page.
[SPARK-17523] Support to generate build info file when building Spark in Windows - #15078
[SPARK-17523] Support to generate build info file when building Spark in Windows#15078Myasuka wants to merge 1 commit into
Conversation
srowen
commented
Sep 13, 2016
I don't think we support building on Windows. I think it's fine to make minor changes to accommodate Windows no matter what, but this is non-trivial. |
+@HyukjinKwon we do windows for R |
Thanks for cc'ing me @felixcheung. Actually, I took a look and wanted to leave a comment but I didn't because I couldn't find a concrete reason or reference to support my opinion and also I know @srowen is an expert in this area. FWIW and as I am already here - I tend to agree with Sean. I think it'd be nicer if all tests pass on Windows and pre-built releases work fine on Windows but it might not necessarily meam that we should support a proper build on Windows. Also, I know we mentioned that we support Windows in http://spark.apache.org/docs/latest/#downloading but I don't think this refers that we support to build Spark on Windows. I am willing to take a close look if Sean/comitters approve and confirm that it is worth being added. |
SparkQA
commented
Sep 16, 2016
Test build #3274 has finished for PR 15078 at commit
|
jodersky
commented
Sep 28, 2016
How wide-spread is powershell on windows computers? I assume that modern versions ship with it, but I also heard that they come with a bash-like shell in the latest version. Does the current build work in the new environment? |
FWIW, doesn't Power shell allows executing bash? (I haven't tried that by myself but I think I saw some usages and documentation before) (Oh, this is what @jodersky pointed out right above) |
I'm not sure older Windows versions have powershell installed by default.. It looks like Bash for Windows is Windows 10 only https://msdn.microsoft.com/en-us/commandline/wsl/install_guide |
HyukjinKwon
commented
Sep 29, 2016
From the discussion above, I would like to stay against this PR. |
Myasuka
commented
Sep 29, 2016
@jodersky Actually, BashOnWindows only exists on Windows10 Anniversary Update. Moreover, this feature needs to be manually enabled to take effects. And I don't think this bash environment in BashOnWindows worked very well and stably so that could be used in production built in the short term. |
srowen
commented
Oct 4, 2016
Let's close this PR for now. |
Closesapache#15303Closesapache#15078Closesapache#15080Closesapache#15135Closesapache#14565Closesapache#12355Closesapache#15404
In Linux |
HyukjinKwon
commented
Apr 21, 2017
@guoxiaolongzte, Let's ask a question to mailing list. Up to my knowledge, we should build first before running tests properly and maybe the errors are related with it. |
Closesapache#15303Closesapache#15078Closesapache#15080Closesapache#15135Closesapache#14565Closesapache#12355Closesapache#15404 Author: Sean Owen <sowen@cloudera.com> Closesapache#15451 from srowen/CloseStalePRs.
What changes were proposed in this pull request?
Currently, if we build Spark, it will generate a
spark-version-info.propertiesand merged intospark-core_2.11-*.jar. However, the scriptbuild/spark-build-infowhich generates this file can only be executed with bash environment.Without this file, errors like below will happen when submitting Spark application, which break the whole submitting phrase at beginning.
I add
build/spark-build-info.ps1to generatespark-version-info.propertiesfile in Windows, and modifycore/pom.xmlandproject/SparkBuild.scalato support this scenario when building Spark with maven or sbt.How was this patch tested?
Tested on my local Windows 10 machine, which generated the
spark-version-info.propertiesundercore/target/extra-resourcesfolder as expected.