[GitHub] zeppelin pull request #1195: [WIP] [ZEPPELIN-759] Spark 2.0 support

2016-07-15 Thread Leemoonsoo
GitHub user Leemoonsoo opened a pull request:

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

[WIP] [ZEPPELIN-759] Spark 2.0 support

### What is this PR for?
This PR implement spark 2.0 support based on #747.
This PR has approach from #980 which is reimplementing code in scala.

You can try build this branch

```
mvn clean package -Dscala-2.11 -Pspark-2.0 -Dspark.version=2.0.0-preview 
-Ppyspark -Psparkr -Pyarn -Phadoop-2.6 -DskipTests
```

### What type of PR is it?
Improvements

### Todos
* [x] - Spark 2.0 support
* [x] - Rebase after #747 merge
* [ ] - .travis.yml to use spark version 2.0.0 instead of 2.0.0-preview 
after spark 2.0.0 release
* [ ] - Update LICENSE file
* [ ] - Update related document (build)

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

### How should this be tested?

Build and try
```
mvn clean package -Dscala-2.11 -Pspark-2.0 -Dspark.version=2.0.0-preview 
-Ppyspark -Psparkr -Pyarn -Phadoop-2.6 -DskipTests
```

### Screenshots (if appropriate)

![spark2](https://cloud.githubusercontent.com/assets/1540981/16771611/fe804038-4805-11e6-8447-3fa4258bb51d.gif)

### Questions:
* Does the licenses files need update? yes
* Is there breaking changes for older versions? no
* Does this needs documentation? yes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Leemoonsoo/zeppelin spark-20

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

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


commit 836438a54404017a65f43a60326750972c07820f
Author: Lee moon soo 
Date:   2016-07-15T23:51:16Z

Spark 2.0 support

commit f3ab14e09b1b56eeddcee559305fe4dd9a3c4adc
Author: Lee moon soo 
Date:   2016-07-16T00:20:21Z

Update SparkSqlInterpreterTest

commit f4671316d731d1b0358b60c0e58720cdd2858069
Author: Lee moon soo 
Date:   2016-07-16T01:10:00Z

Update .travis.yml

commit 81801d231cda2176cc92259c4aaf57d514cfee75
Author: Lee moon soo 
Date:   2016-07-16T01:40:54Z

Update SPARK_HOME directory detection pattern for 2.0.0-preview in the test

commit 05b95a066069e61ec3a574dc9e04b652fa2caef1
Author: Lee moon soo 
Date:   2016-07-16T02:22:32Z

Make ZeppelinSparkClusterTest.java work with spark 2




---
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 issue #1170: BigQuery Interpreter for Apazhe Zeppelin[ZEPPELIN-1153...

2016-07-15 Thread babupe
Github user babupe commented on the issue:

https://github.com/apache/zeppelin/pull/1170
  
Please clarify regarding the LICENSE file.
Also, if you have any other feedback, would be happy to take a look.


---
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 #1194: [ZEPPELIN-1193] Update Node JS related dependen...

2016-07-15 Thread lresende
GitHub user lresende opened a pull request:

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

[ZEPPELIN-1193] Update Node JS related dependencies to avoid RegExp DoS

### What is this PR for?
Update Node JS related dependencies to avoid intermittent build issues that 
suggest updates to avoid RegExp DoS

### What type of PR is it?
[Bug Fix]

### Todos
* [update minimatch] - Force minimatch to version 3.0.2 and up

### What is the Jira issue?
* [ZEPPELIN-1193](https://issues.apache.org/jira/browse/ZEPPELIN-1193)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lresende/incubator-zeppelin node

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

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


commit c199421f644c0ab0bc289da470f713653c0af70f
Author: Luciano Resende 
Date:   2016-07-07T21:27:56Z

Update node.js and related plugins

commit b6709b6d84d577c837d29cfc23a588d425dff544
Author: Luciano Resende 
Date:   2016-07-07T21:42:38Z

Put dependencies in alphabetical order




---
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.
---


[jira] [Created] (ZEPPELIN-1193) Update Node JS dependencies to avoid RegExp DoS

2016-07-15 Thread Luciano Resende (JIRA)
Luciano Resende created ZEPPELIN-1193:
-

 Summary: Update Node JS dependencies to avoid RegExp DoS
 Key: ZEPPELIN-1193
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1193
 Project: Zeppelin
  Issue Type: Bug
  Components: build, front-end
Reporter: Luciano Resende
Assignee: Luciano Resende


I was having some intermittent build issues complaining about some node 
dependencies that needs to be updated to avoid RegExp DoS issues  :

[ERROR] npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 
or higher to avoid a RegExp DoS issue

[ERROR] npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 
or higher to avoid a RegExp DoS issue

[ERROR] npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before 
will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon 
as possible. Use 'npm ls graceful-fs' to find it in the tree.

[ERROR] npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before 
will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon 
as possible. Use 'npm ls graceful-fs' to find it in the tree.

[ERROR] npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 
or higher to avoid a RegExp DoS issue

[ERROR] npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before 
will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon 
as possible. Use 'npm ls graceful-fs' to find it in the tree.

[ERROR] npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer 
maintained. Upgrade to lodash@^4.0.0.

[ERROR] npm WARN deprecated CSSselect@0.7.0: the module is now available as 
'css-select'

[ERROR] npm WARN optional dep failed, continuing fsevents@1.0.12

[ERROR] npm WARN deprecated CSSwhat@0.4.7: the module is now available as 
'css-what'

[ERROR] npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 
or higher to avoid a RegExp DoS issue
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

2016-07-15 Thread rawkintrevo
Github user rawkintrevo commented on the issue:

https://github.com/apache/zeppelin/pull/418
  
@bzz took advantage of the break in the action on 116 to finish this off. 
Should be GTG now. 

Updated to Flink 1.0, Maven 3.3.9, Spark 1.6.  Also added some points on 
just using Spark/Flink binaries, as I have run into multiple headaches when 
trying to build all projects from source. 



---
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 #1193: [ZEPPELIN-1192] Block pyspark paragraph hang.

2016-07-15 Thread astroshim
GitHub user astroshim opened a pull request:

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

[ZEPPELIN-1192] Block pyspark paragraph hang.

### What is this PR for?
This PR block pyspark paragraph hang.


### What type of PR is it?
Bug Fix


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


### How should this be tested?
1. build zeppelin without pyspark (just mvn clean package -DskipTests)
2. open note and set paragraph interpreter as "spark.pyspark" 
3. hit "Ctrl+." for auto completion.
4. try run paragraph.
- please refer to the screenshot.

### Screenshots (if appropriate)
- before

![b](https://cloud.githubusercontent.com/assets/3348133/16881827/ee30e248-4af6-11e6-9409-7e7b9f622121.gif)

- after

![a](https://cloud.githubusercontent.com/assets/3348133/16881840/f4d6d2ec-4af6-11e6-89b3-1e4e2806a742.gif)


### 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/astroshim/zeppelin ZEPPELIN-1192

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

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


commit 288eca7ddb8bffd271221ad21805f07d2181f8b5
Author: astroshim 
Date:   2016-07-15T16:37:04Z

block infinite loop.




---
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.
---


[jira] [Created] (ZEPPELIN-1192) pyspark paragraph hang.

2016-07-15 Thread Shim HyungSung (JIRA)
Shim HyungSung created ZEPPELIN-1192:


 Summary: pyspark paragraph hang.
 Key: ZEPPELIN-1192
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1192
 Project: Zeppelin
  Issue Type: Bug
Reporter: Shim HyungSung


Paragraph is hanging when zeppelin build without including pyspark 
and execute completion shortcut on a paragraph with pyspark.
And RemoteInterpreterServer thread count increases every request completion.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] zeppelin pull request #1145: [ZEPPELIN-1012] Support Interpreter Aliases

2016-07-15 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 issue #1145: [ZEPPELIN-1012] Support Interpreter Aliases

2016-07-15 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1145
  
@Leemoonsoo Thanks for detail review!!


---
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 issue #1187: [ZEPPELIN-1163] Change some parameter name properly in...

2016-07-15 Thread zmhassan
Github user zmhassan commented on the issue:

https://github.com/apache/zeppelin/pull/1187
  
@jongyoul 
Sounds good. From what I understand we have to let ZEPPELIN-1012 PR  get 
merged before merging this one, is that correct?  

@zjffdu 
Is it okay if I complete this work as I've already started?




---
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.
---


[jira] [Created] (ZEPPELIN-1191) Support running paragraph with interpreterSetting.group in case that interpreterSetting doesn't have it

2016-07-15 Thread Jongyoul Lee (JIRA)
Jongyoul Lee created ZEPPELIN-1191:
--

 Summary: Support running paragraph with interpreterSetting.group 
in case that interpreterSetting doesn't have it
 Key: ZEPPELIN-1191
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1191
 Project: Zeppelin
  Issue Type: New Feature
  Components: zeppelin-zengine
Reporter: Jongyoul Lee
Assignee: Jongyoul Lee
 Fix For: 0.7.0


For backward compatibility, we should support in case that users run a 
paragraph with legacy way like using {{%interpreterSetting.group}}. For 
example, if users' settings' name are {{spark-prod}} and {{spark-dev}}, user 
can run with {{%spark}} with selecting one of interpreterSetting, but in a new 
version, user cannot run a paragraph with {{%spark}} even though they bind all 
of spark interpreter including {{spark-prod}} and {{spark-dev}}. It is proper 
behaviour for new one, but we need to support old way in order to move user 
experience smoothly from old to new.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] zeppelin issue #1187: [ZEPPELIN-1163] Change some parameter name properly in...

2016-07-15 Thread zmhassan
Github user zmhassan commented on the issue:

https://github.com/apache/zeppelin/pull/1187
  
Thank you. I'll make some more updates and push fix's to these as well.


---
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 issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

2016-07-15 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
Thank you for your answer.
I would restart operations soon to organize your information.
I plan to expand the .
If anyone have a different opinion, please write to comment.
Thank you.


---
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 #1192: Versioning/get note revision api

2016-07-15 Thread khalidhuseynov
GitHub user khalidhuseynov opened a pull request:

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

Versioning/get note revision api

### What is this PR for?
Adds websocket api for getting note revision.

### What type of PR is it?
Improvement | Feature

### Todos
* [x] - add backend websocket handle
* [x] - add frontend call


### What is the Jira issue?
[#1189](https://issues.apache.org/jira/browse/ZEPPELIN-1189)

### How should this be tested?
green CI (can be tested once frontend implemented)

### 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/khalidhuseynov/incubator-zeppelin 
versioning/get-note-revision-api

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

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


commit 79f8ac9525fb2f58fbde43511e742f65f47bf36e
Author: Khalid Huseynov 
Date:   2016-07-15T09:03:06Z

add getNoteRevision to front

commit 3783fc95439391125205c2393f10466088773561
Author: Khalid Huseynov 
Date:   2016-07-15T09:12:26Z

receive ws NOTE_REVISION msg

commit d9751c3117c0171076d5232f62b46ea9dd50b1bb
Author: Khalid Huseynov 
Date:   2016-07-15T10:05:54Z

add backend ws api to get note revision

commit baaa704fbf9ba24db09ef631a4ef2ceb32809396
Author: Khalid Huseynov 
Date:   2016-07-15T10:32:33Z

change NotebookRepo api to get note revision from Revision object to String 
revId




---
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.
---


[jira] [Created] (ZEPPELIN-1190) Get note revision - websocket api

2016-07-15 Thread Khalid Huseynov (JIRA)
Khalid Huseynov created ZEPPELIN-1190:
-

 Summary: Get note revision - websocket api
 Key: ZEPPELIN-1190
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1190
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Khalid Huseynov
Assignee: Khalid Huseynov
 Fix For: 0.7.0


This is a subtask for the issue under version control. In frontend we should be 
able to request certain revision of note through websocket api.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (ZEPPELIN-1189) Get note revision - websocket api

2016-07-15 Thread Khalid Huseynov (JIRA)
Khalid Huseynov created ZEPPELIN-1189:
-

 Summary: Get note revision - websocket api
 Key: ZEPPELIN-1189
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1189
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Khalid Huseynov
Assignee: Khalid Huseynov
 Fix For: 0.7.0


This is a subtask for the issue under version control. In frontend we should be 
able to request certain revision of note through websocket api.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] zeppelin issue #1117: [ZEPPELIN-1086] Auto Completion for Interpreter.

2016-07-15 Thread astroshim
Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1117
  
@bzz Thank you kindly for telling like that. 
What do you think about tagging meta value than removing keywords like 
following image? 

![image](https://cloud.githubusercontent.com/assets/3348133/16870311/eb05d992-4abb-11e6-8172-99c90196a5c9.png)

I think it looks more nicer than removing keywords.
If it is okay, let me make it at the another PR.


---
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 #1162: [ZEPPELIN-909] Apply new mechanism to Elasticse...

2016-07-15 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 issue #1170: BigQuery Interpreter for Apazhe Zeppelin[ZEPPELIN-1153...

2016-07-15 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1170
  
@babupe great job, I have highlighted few issues inline in code above.

I would really appreciate if, for the sake of maintainability, you could 
please add `./bigquery/README.md` with some _technical_ information on 
interpreter implementation i.e

 - point to the sources of current BigQuery library that is beeing used

  ```
com.google.apis:google-api-services-bigquery:v2-rev265-1.21.0
  ```
  I had no luck locating it by searching online :\

 - small rationale why it was used or how it is compared to 
[GoogleCloudPlatform/gcloud-java](https://github.com/GoogleCloudPlatform/gcloud-java/)

 - mention authentication mechanism used


---
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.
---


Re: [DISCUSS] Zeppelin 0.6.1 release

2016-07-15 Thread Felix Cheung
Don't we need the official Spark 2.0.0 artifacts in maven central repo to 
official release support for it?





On Thu, Jul 14, 2016 at 5:39 PM -0700, "Vinay Shukla" 
> wrote:

We should not wait. I anticipate Spark 2.0 to be officially announced <
2weeks. Would be great to be the first notebook to support 2.0.

On Thursday, July 14, 2016, Luciano Resende  wrote:

> For Spark 2.0, do we need to wait for it's official release which is close
> by...
>
> On Thu, Jul 14, 2016 at 3:45 PM, moon soo Lee  > wrote:
>
> > Hi folks,
> >
> > We have released 0.6.0 July 2nd. During the 0.6.0 release discussion [1],
> > we could see consensus that having a release 0.6.1 when Zeppelin have
> Spark
> > 2.0 support.
> >
> > I have created a issue for 0.6.1 release [2]. The issue currently have
> > Spark 2.0 and scala 2.11 support as a blocker.
> >
> > There were some bug fixes on master branch since 0.6.0 release.
> > How about we discuss and backport some important bug fixes into
> > branch-0.6.0? (if any)
> > And how about we start release process of 0.6.1, as soon as all blockers
> of
> > [2] being resolved?
> >
> >
> > Thanks,
> > moon
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/e107c44df1a7fc4cd232144f6a24d81b32a7d988d5947093b79f05ee@1464110799@%3Cdev.zeppelin.apache.org%3E
> > [2] https://issues.apache.org/jira/browse/ZEPPELIN-1177
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>


[GitHub] zeppelin issue #1170: BigQuery Interpreter for Apazhe Zeppelin[ZEPPELIN-1153...

2016-07-15 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1170
  
@babupe thank you for taking care. @AhyoungRyu thank you for review. 

Let me do another pass on it and get back to you.


---
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 issue #1164: ZEPPELIN-1115: Python - interpreter for SQL over DataF...

2016-07-15 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1164
  
Done, merging after CI ♻️  if there is no further discussion


---
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 issue #747: [ZEPPELIN-605] Add support for Scala 2.11

2016-07-15 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/747
  
@bzz Sure


---
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 issue #747: [ZEPPELIN-605] Add support for Scala 2.11

2016-07-15 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/747
  
@Leemoonsoo could you into non-trivial merge conflicts that happen on 
merging to `branch-0.6` ?


---
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 #747: [ZEPPELIN-605] Add support for Scala 2.11

2016-07-15 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 issue #1187: [ZEPPELIN-1163] Change some parameter name properly in...

2016-07-15 Thread AhyoungRyu
Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1187
  
Is this PR WIP? I think `rest-notebook.md` file needs to be updated as well.

[docs/rest-api/rest-notebook.md](https://github.com/apache/zeppelin/blob/master/docs/rest-api/rest-notebook.md)

And there are still many `notebookId` in other files.  
 - 
[zeppelin-web/src/app/jobmanager/jobmanager.controller.js#L25](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/jobmanager/jobmanager.controller.js#L25)
 - 
[zeppelin-web/src/app/jobmanager/jobs/job.html#L26](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/jobmanager/jobs/job.html#L26)
 - 
[zeppelin-web/src/app/jobmanager/jobs/job-progressBar.html](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/jobmanager/jobs/job-progressBar.html)
 - 
[zeppelin-web/src/app/jobmanager/jobs/job-control.html#L15](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/jobmanager/jobs/job-control.html#L15)
 - 
[zeppelin-server/src/test/java/org/apache/zeppelin/rest/ZeppelinRestApiTest.java#L287](https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/test/java/org/apache/zeppelin/rest/ZeppelinRestApiTest.java#L287)
 - 
[zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/Notebook.java#L604](https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/Notebook.java#L604)


---
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 issue #1145: [ZEPPELIN-1012] Support Interpreter Aliases

2016-07-15 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1145
  
@jongyoul Thanks! I have tested and reviewed the code. and looks good 
except one behavior.

Let's say there're two interpreter settings. `spark1` and `spark2` (and no 
interpreter setting name `spark`).

previously '%spark' select `spark1` or `spark2` whichever in front of 
binded interpreter list.
now, '%spark' is printing `Prefix not found`.

So after this PR, in this specific case, notebook will not be run before 
user change interpreter selection text in every paragraphs.

How do you think about supporting previous interpreter selection mechanism, 
too? Will there be any side effect to support previous interpreter selection 
mechanism? Or do you think it's better support new selection mechanism only?


---
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 issue #1190: ZEPPELIN-1187. Redirect output of the process running ...

2016-07-15 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1190
  
\cc @Leemoonsoo  Could you help take look at this PR ? Since you are the 
original author of this file. Thanks.


---
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 #1190: ZEPPELIN-1187. Redirect output of the process r...

2016-07-15 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1187. Redirect output of the process running interpreter.sh to 
log4j

### What is this PR for?
For now the output of process running interpter.sh is lost, it would be 
nice to redirect it to log4j for debugging, especially debugging related with 
interpreter.sh

### What type of PR is it?
Improvement


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

### How should this be tested?
Tested manully, here's the output in the log file of the process running 
interpreter.sh

```
INFO [2016-07-15 15:30:10,537] ({Exec Stream Pumper} 
RemoteInterpreterManagedProcess.java[processLine]:179) - Spark Command: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/java -cp 
/Users/jzhang/github/zeppelin/interpreter/spark/*:/Users/jzhang/github/zeppelin/zeppelin-interpreter/target/lib/*:/Users/jzhang/github/zeppelin/conf/:/Users/jzhang/github/zeppelin/conf/:/Users/jzhang/github/zeppelin/zeppelin-interpreter/target/classes/Users/jzhang/github/zeppelin/interpreter/spark/zeppelin-spark-0.7.0-SNAPSHOT.jar:/Users/jzhang/Java/lib/spark-1.6.1/conf/:/Users/jzhang/Java/lib/spark-1.6.1/assembly/target/scala-2.10/spark-assembly-1.6.1-hadoop2.6.0.jar:/Users/jzhang/Java/lib/spark-1.6.1/lib_managed/jars/datanucleus-api-jdo-3.2.6.jar:/Users/jzhang/Java/lib/spark-1.6.1/lib_managed/jars/datanucleus-core-3.2.10.jar:/Users/jzhang/Java/lib/spark-1.6.1/lib_managed/jars/datanucleus-rdbms-3.2.9.jar:/Users/jzhang/Java/lib/hadoop-2.7.2/etc/hadoop/
 -Xms1g -Xmx1g -Dfile.encoding
 =UTF-8 
-Dlog4j.configuration=file:///Users/jzhang/github/zeppelin/conf/log4j.properties
 
-Dzeppelin.log.file=/Users/jzhang/github/zeppelin/logs/zeppelin-interpreter-spark-jzhang-jzhangMBPr.local.log
 org.apache.spark.deploy.SparkSubmit --conf 
spark.driver.extraClassPath=::/Users/jzhang/github/zeppelin/interpreter/spark/*:/Users/jzhang/github/zeppelin/zeppelin-interpreter/target/lib/*::/Users/jzhang/github/zeppelin/conf:/Users/jzhang/github/zeppelin/conf:/Users/jzhang/github/zeppelin/zeppelin-interpreter/target/classes/Users/jzhang/github/zeppelin/interpreter/spark/zeppelin-spark-0.7.0-SNAPSHOT.jar
 --conf spark.driver.extraJavaOptions= -Dfile.encoding=UTF-8 
-Dlog4j.configuration=file:///Users/jzhang/github/zeppelin/conf/log4j.properties
 
-Dzeppelin.log.file=/Users/jzhang/github/zeppelin/logs/zeppelin-interpreter-spark-jzhang-jzhangMBPr.local.log
 --class org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer 
/Users/jzhang/github/zeppelin/interpreter/spark/zeppelin-spark-0.7.0-SNA
 PSHOT.jar 55592
 INFO [2016-07-15 15:30:10,537] ({Exec Stream Pumper} 
RemoteInterpreterManagedProcess.java[processLine]:179) - 

 INFO [2016-07-15 15:30:11,058] ({Exec Stream Pumper} 
RemoteInterpreterManagedProcess.java[processLine]:179) - SLF4J: Class path 
contains multiple SLF4J bindings.
```


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zjffdu/incubator-zeppelin ZEPPELIN-1187

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

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


commit 977f42610f1dd0e556b4e3e63d1ccf3a6387dd89
Author: Jeff Zhang 
Date:   2016-07-15T07:36:22Z

ZEPPELIN-1187. Redirect output of the process running interpreter.sh to 
log4j




---
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.
---


[jira] [Created] (ZEPPELIN-1187) Redirect output of the process running interpreter.sh to log4j

2016-07-15 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-1187:


 Summary: Redirect output of the process running interpreter.sh to 
log4j
 Key: ZEPPELIN-1187
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1187
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.6.0
Reporter: Jeff Zhang
Priority: Minor


For now the output of process running interpter.sh is lost, it would be nice to 
redirect it to log4j for debugging, especially debugging related with 
interpreter.sh



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (ZEPPELIN-1186) Change interpreter binding throws NPE

2016-07-15 Thread Mina Lee (JIRA)
Mina Lee created ZEPPELIN-1186:
--

 Summary: Change interpreter binding throws NPE
 Key: ZEPPELIN-1186
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1186
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Mina Lee
Assignee: Mina Lee
 Fix For: 0.7.0


Here is the step to reproduce
1. Create notebook
2. type '%fake ' including space at the end
3. Unbind markdown interpreter from note binding and hit save

{code}
Caused by: java.lang.NullPointerException
at 
org.apache.zeppelin.helium.HeliumApplicationFactory.onUnbindInterpreter(HeliumApplicationFactory.java:447)
at 
org.apache.zeppelin.notebook.Notebook.fireUnbindInterpreter(Notebook.java:797)
at 
org.apache.zeppelin.notebook.Notebook.bindInterpretersToNote(Notebook.java:272)
at 
org.apache.zeppelin.rest.NotebookRestApi.bind(NotebookRestApi.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at 
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
... 50 more
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] zeppelin pull request #1189: ZEPPELIN-1185. ZEPPELIN_INTP_JAVA_OPTS should n...

2016-07-15 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1185. ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS

### What is this PR for?

Don't use ZEPPELIN_JAVA_OPTS as the default value of ZEPPELIN_INTP_JAVA_OPTS

### What type of PR is it?
Improvement

### Todos
* [ ] - Task

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

### How should this be tested?
Tested manually.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zjffdu/incubator-zeppelin ZEPPELIN-1185

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

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


commit a54d843979a7a7c843394d56b1678c0380ffa048
Author: Jeff Zhang 
Date:   2016-07-15T06:21:21Z

ZEPPELIN-1185. ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS as 
default value




---
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.
---


[jira] [Created] (ZEPPELIN-1185) ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS as default value

2016-07-15 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-1185:


 Summary: ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS 
as default value
 Key: ZEPPELIN-1185
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1185
 Project: Zeppelin
  Issue Type: Improvement
  Components: Core
Affects Versions: 0.6.0
Reporter: Jeff Zhang
Priority: Minor


For now, if ZEPPELIN_INTP_JAVA_OPTS is not defined it would use 
ZEPPELIN_JAVA_OPTS. I don't think it make sense to do that implicitly as it may 
not be the user intend to do.  If user want to specify custom java opts for 
interpreter process, then let them do it by himself.  

Besides this introduce some unexpected behavior, e.g. I set ZEPPELIN_JAVA_OPTS 
as following to remote debug, but this setting will also apply to the remote 
interpreter process which cause it hang there. 

{code}
export 
ZEPPELIN_JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005"
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)