Skip to content

Conversation

@Bidek56
Copy link
Contributor

@Bidek56 Bidek56 commented Oct 22, 2021

What changes were proposed in this pull request?

Modifying SystemRequirements to include Java <= 17

Why are the changes needed?

Currently Java is limited to version 11

Does this PR introduce any user-facing change? No

How was this patch tested?

$ build/mvn -Phadoop-3.2 -Psparkr -DskipTests package
$ R/install-dev.sh
$ R/run-tests.sh

@github-actions github-actions bot added the R label Oct 22, 2021
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@dongjoon-hyun dongjoon-hyun changed the title [SPARK-37091][R]Upgrading SystemRequirements to include Java <= 17 [SPARK-37091][R] Upgrading SystemRequirements to include Java <= 17 Oct 22, 2021
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

Thank you for the suggestion, @Bidek56 . Could you include your actual result if you test SparkR with Java 17 already?

$ build/mvn -Phadoop-3.2 -Psparkr -DskipTests package
$ R/install-dev.sh
$ R/run-tests.sh

At least, I agree that this PR unblocks SparkR installation on Java 17.

URL: https://www.apache.org https://spark.apache.org
BugReports: https://spark.apache.org/contributing.html
SystemRequirements: Java (>= 8, < 12)
SystemRequirements: Java (>= 8, <= 17)
Copy link
Member

Choose a reason for hiding this comment

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

Hey, I would like to double check this. Why does this matter? What issue did you face by this?

@HyukjinKwon
Copy link
Member

HyukjinKwon commented Oct 23, 2021

I agree with this change, and LGTM but I would like to understand how this change interacts with something external.

@Bidek56
Copy link
Contributor Author

Bidek56 commented Oct 23, 2021

I agree with this change, and LGTM but I would like to understand how this change interacts with something external.

This issue is affected by the Java 11 limit

@HyukjinKwon
Copy link
Member

https://github.com/jupyter/drumsticks repo seems private. Okay, if something is affected, then it's fine - I asked because this Java versions in description are not used in CRAN and rather just a metadata up to my knowledge.

@HyukjinKwon
Copy link
Member

Mind enabling GitHub Actions in your forked repository? Apache Spark leverages contributor's resources in forked repository in their PRs (https://github.com/apache/spark/pull/34371/checks?check_run_id=3977747161).

@Bidek56
Copy link
Contributor Author

Bidek56 commented Oct 23, 2021

https://github.com/jupyter/drumsticks repo seems private. Okay, if something is affected, then it's fine - I asked because this Java versions in description are not used in CRAN and rather just a metadata up to my knowledge.

It's a public repo

@HyukjinKwon
Copy link
Member

HyukjinKwon commented Oct 23, 2021

https://github.com/jupyter/drumsticks: I cannot access 😢 . Once it's enabled, you could rebase in this PR. That should kick the job

### What changes were proposed in this pull request?

Set `spark.sql.files.openCostInBytes` to bytesConf.

### Why are the changes needed?

The name is _*InBytes_, but it actually only accepts **long type**. This is confusing for users. After the changes, it can accept **String** as input which is more flexible to users.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Existing test.

Closes #34353 from RabbidHY/SPARK-37084.

Authored-by: RabbidHY <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
@srowen
Copy link
Member

srowen commented Oct 23, 2021

I also can't see the repo, but w/e. It seems fine to make this change - not sure any tests will test it anyway.
This is a fine change for 3.3, but, only Java 11 is supported in 3.2.0 anyway, note.

@HyukjinKwon
Copy link
Member

CRAN check in SparkR build validates the DESCRIPTION file. The check won't validate the values but at least format and etc. Might need to make sure that the tests pass anyway although it's unlikely that the tests are broken by this change.

@Bidek56
Copy link
Contributor Author

Bidek56 commented Oct 23, 2021

https://github.com/jupyter/drumsticks: I cannot access 😢 . Once it's enabled, you could rebase in this PR. That should kick the job

It's a public repo, not sure where the drumsticks came from, maybe Android share link, sorry.
Rebasing it now. Thanks for your help!

@Bidek56 Bidek56 changed the title [SPARK-37091][R] Upgrading SystemRequirements to include Java <= 17 [SPARK-37091][R] SystemRequirements to include Java < 18 Oct 23, 2021
@srowen
Copy link
Member

srowen commented Oct 24, 2021

This looks fine now. It wasn't a test problem, just some incorrect commits got merged when you rebased this branch. All set

@HyukjinKwon
Copy link
Member

Actually, I think the current PR is mergable and should look fine since it will be squashed .. although it should ideally be rebased.

Merged to master.

@dongjoon-hyun
Copy link
Member

dongjoon-hyun commented Oct 25, 2021

@HyukjinKwon , the final commit looks still wrong to me.

Could you check the final commit before pushing to the Apache repo, @HyukjinKwon ?

@HyukjinKwon
Copy link
Member

oops

@HyukjinKwon
Copy link
Member

HyukjinKwon commented Oct 25, 2021

This is a bit odds because the PR shows the diff only the one in description https://github.com/apache/spark/pull/34371/files, and I haven't had any problem in such cases so far.

@HyukjinKwon
Copy link
Member

sorry it was my bad. let me correct this one.

@dongjoon-hyun
Copy link
Member

Ya, this commit technically reverted [SPARK-37084][SQL] Set spark.sql.files.openCostInBytes to bytesConf

@dongjoon-hyun
Copy link
Member

No problem, @HyukjinKwon ~ We are okay because this is not released and we can fix it.

@HyukjinKwon
Copy link
Member

I cherry-picked 76a317a back to the master branch.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants