[GitHub] zeppelin pull request #1587: [ZEPPELIN-1609] using pyspark(python3) with liv...

2017-01-03 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/1587


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] zeppelin pull request #1587: [ZEPPELIN-1609] using pyspark(python3) with liv...

2017-01-02 Thread purechoc
GitHub user purechoc reopened a pull request:

https://github.com/apache/zeppelin/pull/1587

[ZEPPELIN-1609] using pyspark(python3) with livy interperter

### What is this PR for?
using pyspark(python3) with livy interperter

### What type of PR is it?
Improvement

### Todos

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1609

### How should this be tested?
%livy.pyspark3
3/2
check result is "1.5"

### 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/purechoc/zeppelin zeppelin-livy-pyspark3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1587.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 #1587


commit c0babf619006cc3a4ac66ffb0904b49e37f3a2ae
Author: purechoc 
Date:   2016-11-03T07:29:43Z

add %livy.python3

commit 3775e47158c7146a8d005af851dd17ca6bfaca7b
Author: purechoc 
Date:   2016-11-03T10:25:07Z

add %livy.python3

commit 7e4210807bcf7483240b06f11081d7cb07e79b88
Author: purechoc 
Date:   2016-11-03T10:49:25Z

add %livy.python3

commit d0e2293327f73fa8ebe89498652cc94db45a02bc
Author: purechoc 
Date:   2016-11-03T23:56:41Z

Trigger

commit 3fc98cd47f88e59f6ae5a0c9e35d476b74df15bf
Author: purechoc 
Date:   2016-11-04T05:33:45Z

add configuration

commit 51140f2686af2cf381ea25dd451097b850f2e396
Author: purechoc 
Date:   2016-11-06T23:39:13Z

Trigger

commit e5db6405e3e87f6425a9503e4fee66167e394b7a
Author: purechoc 
Date:   2016-11-07T00:10:29Z

add properties

commit 55d486ff5987e28f112e81d665c46c4276c47739
Author: purechoc 
Date:   2016-11-09T00:42:24Z

Trigger

commit 476ae2504e24544f44b8bff9a8ed428a6d1b7c04
Author: purechoc 
Date:   2016-12-11T23:38:07Z

Merge remote-tracking branch 'upstream3/master' into zeppelin-livy-pyspark3

Conflicts:
livy/src/main/java/org/apache/zeppelin/livy/LivyPySparkInterpreter.java

commit 7c0f70d6f48852b733f61272a787bd4438733ec7
Author: purechoc 
Date:   2016-12-11T23:53:24Z

refactor code

commit 6f7391fb706efc7f7db4751ac6035ad6e634a953
Author: purechoc 
Date:   2016-12-29T00:08:18Z

update template




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] zeppelin pull request #1587: [ZEPPELIN-1609] using pyspark(python3) with liv...

2017-01-02 Thread purechoc
Github user purechoc closed the pull request at:

https://github.com/apache/zeppelin/pull/1587


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---