[jira] [Created] (ZEPPELIN-2757) Enhance Authentication decrypting key generation

2017-07-09 Thread Yanbo Liang (JIRA)
Yanbo Liang created ZEPPELIN-2757:
-

 Summary: Enhance Authentication decrypting key generation
 Key: ZEPPELIN-2757
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2757
 Project: Zeppelin
  Issue Type: Bug
  Components: security
Reporter: Yanbo Liang


Enhance {{Authentication}} decrypting key generation by random {{KeyGenerator}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[GitHub] zeppelin pull request #2475: [ZEPPELIN-2757] Enhance Authentication decrypti...

2017-07-09 Thread yanboliang
GitHub user yanboliang opened a pull request:

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

[ZEPPELIN-2757] Enhance Authentication decrypting key generation.

### What is this PR for?
Enhance ```Authentication``` decrypting key generation by random 
```KeyGenerator```.

### What type of PR is it?
Improvement

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


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

$ git pull https://github.com/yanboliang/zeppelin zeppelin-2757

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

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


commit 76860df43ec3daaca3763b9ce7c918abf3c8a968
Author: Yanbo Liang 
Date:   2017-07-10T05:50:11Z

Enhance Authentication decrypting key generation.




---
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: Google OAuth in Zeppelin

2017-07-09 Thread Khalid Huseynov
Actually simple implementation for OpenId was done in
https://github.com/apache/zeppelin/pull/2373 through shiro using buji-pac4j
library as you said. This library provides integration realm for OAuth as
well, so I think good starting point would be to configure buji-pac4j with
OAuth realm, and theoretically it should be working or may need some
modifications to already existing flow.

On Mon, Jul 10, 2017 at 12:48 PM, Jongyoul Lee  wrote:

> Hi,
>
> AFAIK, we have talked about OAuth, but didn't decide anything including how
> to implement it and how to support it. We are using shiro for
> authentication. Do you have any idea to support OAuth using Shiro?
>
> On Thu, Jun 29, 2017 at 2:15 AM, Akash Mishra 
> wrote:
>
> > Hi *,
> >
> > Is there any plans to enable OAuth based Authentication mechanism for
> > Zeppelin. Going through some of the archive emails I found out people
> > suggesting to use buji-pac4j but it looks like the integration is not
> very
> > smooth. I was also looking at the Apache Oltu Project which helps in the
> > handling of OAuth.
> >
> > I am planning to add OAuth feature on Zeppelin but would require some
> input
> > from community,
> >
> >
> > 1. Do we have any brainstorm done on how to implement OAuth?
> > 2. Which library would be better suited for our case?
> >
> >
> > Thanks,
> >
> >
> >
> >
> >
> > --
> >
> > Regards,
> > Akash Mishra.
> >
> >
> > "It's not our abilities that make us, but our decisions."--Albus
> Dumbledore
> >
>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>


[GitHub] zeppelin issue #2471: [ZEPPELIN-2744] [minor] Increase error handling in JDB...

2017-07-09 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2471
  
Yes, that's what it is doing now (in the case of Phoenix SQL) it gives a 
valid result with error stack trace, and paragraph results in error. Hence, I 
thought we could either choose to improve it or leave it.


---
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 #2468: [ZEPPELIN-2733] Remove System Information Leak ...

2017-07-09 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2374: [ZEPPELIN-2593] Add storage settings to persist...

2017-07-09 Thread khalidhuseynov
GitHub user khalidhuseynov reopened a pull request:

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

[ZEPPELIN-2593] Add storage settings to persist on run and commit

### What is this PR for?
adding settings to storage layer to let user choose to persist continuously 
or only on commits


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

### Todos
* [x] - add notebook repo setting
* [x] - add persist on run & commit (checkpoint)
* [x] - add persist on commit (checkpoint) only
* [x] - add tests

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

### How should this be tested?
1. go to notebook repo menu and click on edit `Global settings` or do 
through env var `ZEPPELIN_NOTEBOOK_PERSISTENCE`
2. change value of `Note persistence` item to `Persist on note run and 
commits` or change value of `ZEPPELIN_NOTEBOOK_PERSISTENCE` into "run"
3. go change any note, although it will be changed in memory, it won't be 
persisted
4. to check above can reload notes in note list view -> will see original 
note
5. can save note either by `Run` or clicking `Commit` button in version 
control menu of note

### Screenshots (if appropriate)
https://user-images.githubusercontent.com/1642088/27996389-fd0a4a26-651b-11e7-91ed-ea22d135f875.png;>



## 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/zeppelin feat/ZEPPELIN-2593

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

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


commit 856fceed1b39e49461e68b1d97f1f736b1101f3a
Author: Khalid Huseynov 
Date:   2017-05-29T07:48:06Z

initial flow

commit ea82c9919f84252e7f4c0fce8d4a6d1cfe9a2bff
Author: Khalid Huseynov 
Date:   2017-06-09T07:14:07Z

add temp test

commit 1fd869a27e31ecadf271b483b951623801b312fd
Author: Khalid Huseynov 
Date:   2017-06-09T10:39:02Z

rework settings into global

commit dec53aeb44c7f1a97133511730b71ba24a8a94fe
Author: Khalid Huseynov 
Date:   2017-06-12T05:16:10Z

change checkpoint signature with recent note

commit 6b2ce75009bdb19b5df9e8c4ba46c1fcf3637076
Author: Khalid Huseynov 
Date:   2017-06-12T05:16:55Z

improve test

commit 298edf07b18501325a00c980ed9b5e97547270d8
Author: Khalid Huseynov 
Date:   2017-06-12T06:42:01Z

add large test for global setting change

commit 1be654a3d4c3ccdc32ed7020a5a4aa2bc8ea4ce8
Author: Khalid Huseynov 
Date:   2017-06-12T08:52:02Z

add save & commit from note action bar

commit c283c00a207786d595d217ec3893c2ccab8527b5
Author: Khalid Huseynov 
Date:   2017-06-12T12:31:32Z

fix test, set property back

commit 5f24004096b0fa043173238a0ed9f976adf75cfb
Author: Khalid Huseynov 
Date:   2017-06-12T13:34:01Z

move setting from global to per repo and apply to remote s3 and zh

commit a6f572be272d458217858937a3ef4ecdfcfd96cc
Author: Khalid Huseynov 
Date:   2017-06-26T18:22:20Z

add conditional save in s3

commit d04452a214709e3e5dbe40b19030369adc1e2a99
Author: Khalid Huseynov 
Date:   2017-06-30T08:11:28Z

fix spelling

commit fca6d4a570c8f1f1a146be6afde3a25277c9395d
Author: Khalid Huseynov 
Date:   2017-06-30T09:29:04Z

make option as non-actionable, don't broadcast

commit f912f83db174359df1cbd450e1f0b597321dd949
Author: Khalid Huseynov 
Date:   2017-06-30T10:47:10Z

send note inside checkpoint payload

commit 5d1b66ca9afede6801046ee5c390a2372020d93b
Author: Khalid Huseynov 
Date:   2017-06-30T11:37:49Z

fix test

commit 6ab2e1e434a3326f22c938a7e7ebdddb6d3234f4
Author: Khalid Huseynov 
Date:   2017-07-06T14:06:21Z

separate persist for run and update actions in notebook

commit a44caa85ff27887ea0cc200c3f4db36f8a75a013
Author: Khalid Huseynov 
Date:   2017-07-06T17:34:49Z

change env var name with 3 default values

commit 3d1ea5393bfce9ea8ef31a77932974aef13a9809
Author: Khalid Huseynov 
Date:   2017-07-07T01:48:44Z

move settings to base class

commit 0c3d97099f4e4f0a5d207815cdb341531c351846
Author: Khalid Huseynov 
Date:   2017-07-07T05:51:13Z

add rest test for setting update

commit 846a3d13031023408fd6e723afafecc1c2cab679
Author: Khalid Huseynov 
Date:  

[GitHub] zeppelin pull request #2374: [ZEPPELIN-2593] Add storage settings to persist...

2017-07-09 Thread khalidhuseynov
Github user khalidhuseynov closed the pull request at:

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


---
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 #2466: [ZEPPELIN-2731] GetUserList with JDBCRealm shou...

2017-07-09 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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: Google OAuth in Zeppelin

2017-07-09 Thread Jongyoul Lee
Hi,

AFAIK, we have talked about OAuth, but didn't decide anything including how
to implement it and how to support it. We are using shiro for
authentication. Do you have any idea to support OAuth using Shiro?

On Thu, Jun 29, 2017 at 2:15 AM, Akash Mishra 
wrote:

> Hi *,
>
> Is there any plans to enable OAuth based Authentication mechanism for
> Zeppelin. Going through some of the archive emails I found out people
> suggesting to use buji-pac4j but it looks like the integration is not very
> smooth. I was also looking at the Apache Oltu Project which helps in the
> handling of OAuth.
>
> I am planning to add OAuth feature on Zeppelin but would require some input
> from community,
>
>
> 1. Do we have any brainstorm done on how to implement OAuth?
> 2. Which library would be better suited for our case?
>
>
> Thanks,
>
>
>
>
>
> --
>
> Regards,
> Akash Mishra.
>
>
> "It's not our abilities that make us, but our decisions."--Albus Dumbledore
>



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net


[GitHub] zeppelin issue #2470: [ZEPPELIN-2648] Fix spark module build problem with sc...

2017-07-09 Thread reminia
Github user reminia commented on the issue:

https://github.com/apache/zeppelin/pull/2470
  
@zjffdu  remove scala version in spark-dependencies. 


---
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] Reducing default interpreters while building and releasing Zeppelin

2017-07-09 Thread Jongyoul Lee
Hi,

I think it's time to move to the next step. Zeppelin's web site is already
changed. Zeppelin's default package also provide same interpreters and
include markdown and shell. How do you think of it?

Regards,
Jongyoul

On Sun, Jun 18, 2017 at 11:08 PM, Jongyoul Lee  wrote:

> @Rafffele,
>
> After we discuss it with community, then will make a JIRA issue for
> handling it. :-)
>
> On Fri, Jun 16, 2017 at 1:28 PM, Park Hoon <1am...@gmail.com> wrote:
>
>> @Jeff > , we need to integrate the install script in zeppelin UI.
>>
>> AFAIK, helium has UI to list all available interpreters which are
>> registered in the central maven repo although this feature doesn't work
>> currently.
>>
>> We can improve this page is used to install interpreters which will be
>> not included in the default distribution.
>>
>>
>>
>>
>>
>> [image: Inline image 1]
>>
>>
>> On Wed, Jun 14, 2017 at 8:48 PM, Raffaele S  wrote:
>>
>>> I believe it's a good idea to select which interpreters to keep in the
>>> "default release", should we track this through JIRA?
>>>
>>> 2017-06-11 17:05 GMT+02:00 Jongyoul Lee :
>>>
 Thanks, Alex.

 I left comments we started to discuss on it recently.

 On Sun, Jun 11, 2017 at 6:50 PM, Alexander Bezzubov 
 wrote:

> Hey guys,
>
> great effort! I think people in few other communities will be very
> happy
> with it i.e [1] and [2].
>
> Is there an issue that tracks current status or something like that?
> Does
> anyone have concrete plans to work on it in this/next release?
>
> Sorry if I have missed that out. And please, keep up a good work!
>
>
> --
>
> Alex
>
>
> 1. https://issues.apache.org/jira/browse/BIGTOP-2269
> 2.
> https://github.com/kubernetes/kubernetes/tree/master/example
> s/spark#known-issues-with-zeppelin
>
> On Mon, Jun 5, 2017, 06:54 Jongyoul Lee  wrote:
>
> > Felix,
> > Yes, I said a bit confused. I want to release Zeppelin with some -
> not-all
> > - interpreters, but deploy all interpreters into maven to install
> them if
> > users want to use them.
> >
> > Moon,
> > I think it's the best to fit the list as same as homepage by default
> as it
> > makes users confused less. But if we want to add more interpreters,
> I think
> > mailing questions and related issues are one of the proper criteria.
> >
> > Jeff,
> > Agreed. We already had a menu but it just shows how to use
> > install-interpreter.sh.
> >
> > On Mon, Jun 5, 2017 at 9:36 AM, Jeff Zhang  wrote:
> >
> >>
> >> If possible, we need to integrate the install script in zeppelin
> UI. As I
> >> would expect many users would ask why some interpreter is missing
> and how
> >> to install them.
> >>
> >>
> >>
> >> moon soo Lee 于2017年6月5日周一 上午2:06写道:
> >>
> >>> Following is last discussion related to release package size.
> >>>
> >>>
> >>> https://lists.apache.org/thread.html/69f606409790d7ba11422e8
> c6df941a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
> >>>
> >>> at this time, we have discussed about having bin-all (every
> >>> interpreters), bin-min (selected interpreters), bin-netinst (no
> >>> interpreters) package but didn't conclude the criteria and how we
> make a
> >>> decision.
> >>>
> >>> Jongyoul, do you have any idea about criteria?
> >>>
> >>> Thanks,
> >>> moon
> >>>
> >>> On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung <
> felixcheun...@hotmail.com>
> >>> wrote:
> >>>
>  Sure - I think it will be important to discuss what criteria to
> use to
>  decide what is included vs what will be released separately.
> 
>  _
>  From: Jongyoul Lee 
> 
> >>> Sent: Sunday, June 4, 2017 9:47 AM
>  Subject: Re: [DISCUSS] Reducing default interpreters while
> building and
>  releasing Zeppelin
>  To: dev 
> 
> >>> Cc: 
> 
> >>>
> 
> 
>  It means we release with some interpreters and deploy all
> interpreters
>  into
>  maven separately. We already had a install-interpreter script
> inside
>  it. If
>  someone wants to install specific interpreter not included in
> default
>  release package, they can use that script to install specific one.
> 
>  On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung <
> felixcheun...@hotmail.com
>  >
>  wrote:
> 
>  > Are we proposing some interpreters to be built and released
>  separately?
>  >

[GitHub] zeppelin issue #2329: [ZEPPELIN-2040] ClusterManager to support launching in...

2017-07-09 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2329
  
CI passed: https://travis-ci.org/jongyoul/zeppelin/builds/251742660


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-07-09 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

### What is this PR for?
This is the first step for implement IPython Interpreter in Zeppelin.  I 
just use the jupyter_client to create and manage the ipython kernel. We don't 
need to care about python compilation and execution, all the things are 
delegated to ipython kernel. Ideally all the features of ipython should be 
available in Zeppelin as well.  

### What type of PR is it?
[Feature ]

### Todos
* [ ] - Task

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

### How should this be tested?
Unit is added. 

### Screenshots (if appropriate)
Verify bokeh in IPython Interpreter

![image](https://user-images.githubusercontent.com/164491/27999716-756d749e-6552-11e7-90bb-4c6b08f4ab5c.png)

### 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-2753

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

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


commit e2fbf75e0bf3a814122fa51ea3a88da2823f0487
Author: Jeff Zhang 
Date:   2017-07-02T07:51:14Z

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter




---
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-2754) Support ZeppelinContext in IPython Interpreter

2017-07-09 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-2754:


 Summary: Support ZeppelinContext in IPython Interpreter
 Key: ZEPPELIN-2754
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2754
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ZEPPELIN-2756) Enable colorized output in frontend

2017-07-09 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-2756:


 Summary: Enable colorized output in frontend
 Key: ZEPPELIN-2756
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2756
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ZEPPELIN-2753) Basic Implementation of IPython Interpreter

2017-07-09 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-2753:


 Summary: Basic Implementation of IPython Interpreter
 Key: ZEPPELIN-2753
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2753
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ZEPPELIN-2755) Support Matplotlib in IPythonInterpreter

2017-07-09 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-2755:


 Summary: Support Matplotlib in IPythonInterpreter
 Key: ZEPPELIN-2755
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2755
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[GitHub] zeppelin pull request #2429: [ZEPPELIN-2675] Distributing Jars when using an...

2017-07-09 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2471: [ZEPPELIN-2744] [minor] Increase error handling in JDB...

2017-07-09 Thread felixcheung
Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2471
  
It should then report an error in the InterpreterResult?





---
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 #2374: [ZEPPELIN-2593] Add storage settings to persist on com...

2017-07-09 Thread khalidhuseynov
Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2374
  
@1ambda @zjffdu addressed the feedback and added persist on `run` as well. 
Also moved the logic out of storage classes. Please help further review and 
test this one to move on.


---
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 #2473: [fix] Check runtimeInfos is not null

2017-07-09 Thread ebuildy
GitHub user ebuildy opened a pull request:

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

[fix] Check runtimeInfos is not null

This fix NullPointer exception when restart interpreter after it crashed:

```
Caused by: java.lang.NullPointerException
at 
org.apache.zeppelin.notebook.Paragraph.clearRuntimeInfo(Paragraph.java:735)
at 
org.apache.zeppelin.socket.NotebookServer.clearParagraphRuntimeInfo(NotebookServer.java:2480)
at 
org.apache.zeppelin.rest.InterpreterRestApi.restartSetting(InterpreterRestApi.java:198)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at 
org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at 
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at 
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at 
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at 
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
... 26 more
```

To reproduce:

1- Create a Spark notebook with ``exit`` as content
2- Run notebook, Spark should disconnect interpreter
3- Try restart Spark interpreter -> NullPointer exception (must restart 
Zeppelin)


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

$ git pull https://github.com/ebuildy/zeppelin patch-1

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

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


commit 4f0095120ce5395936dcdba30bce3edf7c95d2af
Author: Thomas Decaux 
Date:   2017-07-09T10:28:34Z

[fix] Check runtimeInfos is not null

This fix NullPointer exception when restart interpreter after it crashed:

Caused by: java.lang.NullPointerException
at 
org.apache.zeppelin.notebook.Paragraph.clearRuntimeInfo(Paragraph.java:735)
at 
org.apache.zeppelin.socket.NotebookServer.clearParagraphRuntimeInfo(NotebookServer.java:2480)
at 
org.apache.zeppelin.rest.InterpreterRestApi.restartSetting(InterpreterRestApi.java:198)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
at 

[GitHub] zeppelin pull request #2472: [ZEPPELIN-2749] Use scalable file structure for...

2017-07-09 Thread 1ambda
GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2749] Use scalable file structure for zeppelin web

### What is this PR for?

We have improved zeppelin-web, but some parts are still messy. As part of 
keeping zeppelin-web module healthy 
([ZEPPELIN-2725](https://issues.apache.org/jira/browse/ZEPPELIN-2725)), I 
suggest having these file structure. (Refer the screenshot section)

Here are few reasons.

- unified directory, file name helps us to recognize, find which part we 
should modify / fix
- [this 
structure](https://github.com/toddmotto/angularjs-styleguide#file-naming-conventions)
 is what the angularjs community has verified for few years. so newly joined 
developers can feel more comfortable.
- this is necessary for [Modular 
archiecture](https://issues.apache.org/jira/browse/ZEPPELIN-2750) and it 
eventually helps us to make a smooth transition toward next technologies (even 
whatever we will use)

Additionally, 

- This is not the meaningless refactoring PR and doesn't block developing 
new features / fixes (Please refer the `Some Details` section)
- I will handle conflicts for few days would be brought by other WIPs

For your information, 

- https://github.com/toddmotto/angularjs-styleguide#file-naming-conventions
- 
https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#naming

 How to Review This PR?

Please follow the commits. I modified submodules by splitting commits. Thus 
commit message includes what has been done in that PR. For example,


![image](https://user-images.githubusercontent.com/4968473/27993114-d8ac45e6-64dd-11e7-8130-f3fa887054a1.png)

 Some Details

- Didn't change the widely used variable names not to make many conflicts. 
For example, `websocketMsgSrv`, `arrayOrderingSrv`
- Since there are helium packages already published, didn't changed the 
html names like `pivot_setting.html` (it's better to use `pivot-setting.html` 
if we following the rule)

### What type of PR is it?
[Improvement | Refactoring]

### Todos

Please refer the commit message.

### What is the Jira issue?

[ZEPPELIN-2749](https://issues.apache.org/jira/browse/ZEPPELIN-2749)

### How should this be tested?

**All functionalities must work** as like before, CI will test it. 

### Screenshots (if appropriate)

 Before: messy, mixed directory structure


![image](https://user-images.githubusercontent.com/4968473/27993126-0a94aca6-64de-11e7-93db-548b6fcc6913.png)


 After: only the shared components will be placed under `components/`


![image](https://user-images.githubusercontent.com/4968473/27993118-ee1bd2d4-64dd-11e7-95b6-f71dc628a94e.png)


### 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/1ambda/zeppelin 
ZEPPELIN-2749/use-scalable-file-structure-for-zeppelin-web

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

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


commit c1c210de28579bb0ada8f2b64434f0914e78274a
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:12:27Z

rename: repository-dialog -> repository-create

commit a9a6368a663fce28e8c62a7cebed647fa52075a8
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:14:41Z

fix: remove useless dir interpreter-create

commit 4e7f6d9c1119a1f82cb34596d089a8c6ef919594
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:16:25Z

fix: Move repository-create into interpreter/

commit d7d7434a722ef161289b043f42e5051581fb51bf
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:31:06Z

move: note specific service saveAsService into notebook/

commit 3f02c5038cd723cc4882c87e8194033ff1ff816b
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:33:10Z

fix: Remove unused saveAsService from paragraph ctrl

commit 701f44320b44675b60f00ab80542944fbc7902fe
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:39:52Z

move: note specific service into notebook/

commit ad99c04b7c0216dabcf01ba3705e30f7c46fc68c
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:50:02Z

move: note specific dialog into notebook/

commit c21a1237bc2cee4bc8e1fe5e5aef97c68bc9ac1e
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T03:58:42Z

move: paragraph specific ctrl into paragraph/

commit a25275307e373737b465b349d8f9d9f0d25133bc
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-09T04:02:04Z

fix: Remove meaningless 

[GitHub] zeppelin pull request #2456: [ZEPPELIN-2714] Soft-code Spark UI button visua...

2017-07-09 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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-2752) Support IPython in PythonInterpreter

2017-07-09 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-2752:


 Summary: Support IPython in PythonInterpreter
 Key: ZEPPELIN-2752
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2752
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)