Skip to content

Conversation

@gentlewangyu
Copy link

@gentlewangyu gentlewangyu commented May 24, 2018

What changes were proposed in this pull request?

compiling spark with scala-2.10 should use the -P parameter instead of -D

How was this patch tested?

JIRA_ID:SPARK-24376
using build/mvn clean package install deploy -DskipTests -Pscala-2.10

Please review http://spark.apache.org/contributing.html before opening a pull request.

git config --global user.name "gentlewangyu"
@gentlewangyu
Copy link
Author

I have verified this patch


./dev/change-scala-version.sh 2.10
./build/mvn -Pyarn -Dscala-2.10 -DskipTests clean package
./build/mvn -Pyarn -scala-2.10 -DskipTestsP clean package
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DskipTestsP?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry , It's -Pscala-2.10

@HyukjinKwon
Copy link
Member

Minor fix doesn't usually need a JIRA. Let's avoid next time.

@HyukjinKwon
Copy link
Member

ok to test

@SparkQA
Copy link

SparkQA commented May 25, 2018

Test build #91137 has finished for PR 21422 at commit bf6b801.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gentlewangyu
Copy link
Author

@HyukjinKwon thanks for your answer!
I have tested it by using the command (build/mvn clean package install deploy -DskipTests -Pscala-2.10)

image

@jerryshao
Copy link
Contributor

Why do you submit PR against branch 2.2?

Besides scala-2.10 profile is no longer valid after 2.3.

@HyukjinKwon
Copy link
Member

But isn't it still a valid fix for 2.2.x?

@jerryshao
Copy link
Contributor

Yes, but the PR should be against master branch.

@jerryshao
Copy link
Contributor

And in master/Spark 2.3 code, since we don't support Scala 2.10, instead we support 2.12, so we should change that part of doc accordingly.

@jerryshao
Copy link
Contributor

Seems this paragraph is already removed in master branch (https://issues.apache.org/jira/browse/SPARK-19810). So this is a branch 2.2- issue only.

@jerryshao
Copy link
Contributor

Do we still have a 2.2 release? If not, then this fix seems obsolete.

@HyukjinKwon
Copy link
Member

HyukjinKwon commented May 29, 2018

I don't know but the fix is open anyway and I thought we better just merge it since it's a valid fix to branch-2.3 anyway and there's no downside of it for example like making the backport harder or since the bit is removed in the master, or potential concern of new bug in this branch alone since it's just doc fix basically. PR size is small. I got that we don't usually fix things in a specific branch alone but this one seems fine.

@jerryshao
Copy link
Contributor

It is not valid for branch-2.3, 2.3 already removed the support of Scala 2.10.

@HyukjinKwon
Copy link
Member

Oops, I meant branch-2.2.

@HyukjinKwon
Copy link
Member

There was a similar(?) argument before - #18873 (comment), FYI.

@gentlewangyu, let's just close this then. The gain is small anyway.

@gentlewangyu
Copy link
Author

@HyukjinKwon @jerryshao ok , thanks

@HyukjinKwon
Copy link
Member

Thank you @gentlewangyu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants