You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by zjffdu <gi...@git.apache.org> on 2018/03/07 04:38:44 UTC
[GitHub] zeppelin pull request #2846: ZEPPELIN-3302. Update SparkVersion.java to supp...
GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2846
ZEPPELIN-3302. Update SparkVersion.java to support Spark 2.3
### What is this PR for?
Trivial PR to support 2.3 via updating SparkVersion.java. Unfortunately we cannot download spark 2.3 from http://d3kbcqa49mib13.cloudfront.net, will leave it in ZEPPELIN-3305
### What type of PR is it?
[Improvement]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-3302
### How should this be tested?
* CI pass
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-3302-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2846.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2846
----
commit e183d0646266e136d037077af3488f99bd359b3d
Author: Jeff Zhang <zj...@...>
Date: 2018-03-07T03:21:19Z
ZEPPELIN-3302. Officially support Spark 2.3
----
---
[GitHub] zeppelin pull request #2846: ZEPPELIN-3302. Update SparkVersion.java to supp...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2846
---
[GitHub] zeppelin issue #2846: ZEPPELIN-3302. Update SparkVersion.java to support Spa...
Posted by felixcheung <gi...@git.apache.org>.
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2846
hey @zjffdu thanks for making all these improvements, could we make sure there is at least one review before merging?
@Leemoonsoo
---