[GitHub] zeppelin issue #2195: [ZEPPELIN-2319] new methods for ZeppelinContext

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2195
  
@meniluca Great initiative! Thanks for detailed explanation and it makes 
sense to me as well. That would be helpful to any other reviewers. 
But before you go further, need to setup travis account for Zeppelin first.

 - Please take a look 
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
 - The repository name must be Zeppelin (not incubator-zeppelin, ...)
 - It's not mandatory to pass all tests to be reviewed. But some reviewers 
might select passed PRs first

Trigger travis CI by pushing new commits.


---
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 #2135: Groovy Interpreter for Apazhe Zeppelin [ZEPPELIN-2176]

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
Looks good to me :)


---
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 #2197: ZEPPELIN-2324. Add property zeppelin.spark.enableSuppo...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2197
  
Will merge it if no more 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 #2135: Groovy Interpreter for Apazhe Zeppelin [ZEPPELIN-2176]

[dlukyanov]

Github user dlukyanov commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
@Leemoonsoo , @AhyoungRyu , any other comments?


---
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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[moon soo Lee]

Verified

 - signature
 - no unexpected binary in source package
 - build from source
 - basic features on binary package

I've found a problem that Note is refreshing when NoteList broadcast (e.g.
Note creation, deletion, rename). Explained the problem in the issue
https://issues.apache.org/jira/browse/ZEPPELIN-2336.

Hope this can be fixed in 0.7.2.

+1.

On Thu, Mar 30, 2017 at 9:35 PM Felix Cheung 
wrote:

> +1
>
> Tested bin, checked signature, ran through a bunch of tests, checked
> report mode, UI etc
>
> I don't think it's a blocker:
> When I search I see a list of note names but with empty white boxes under
> each of them. Isn't it suppose to show where the match is found?
>
> 
> From: Khalid Huseynov 
> Sent: Thursday, March 30, 2017 9:27:01 PM
> To: dev@zeppelin.apache.org
> Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
>
> +1
>
> On Fri, Mar 31, 2017 at 12:32 PM, Ahyoung Ryu  wrote:
>
> > +1
> > tested binary package
> >  - Spark and Python tutorial note
> >  - Zombie process issue
> >
> > and could successfully build Zeppelin from source.
> > Thanks always Mina for your effort.
> >
> >
> > On Fri, Mar 31, 2017 at 12:20 PM, Anthony Corbacho <
> > anthonycorba...@apache.org> wrote:
> >
> > > +1
> > >
> > > Tested with my usual cases.
> > >
> > > Thank you mina!!!
> > >
> > > On Fri, Mar 31, 2017 at 12:13 PM, Jun Kim  wrote:
> > >
> > > > +1
> > > > 2017년 3월 31일 (금) 오후 12:13, Jongyoul Lee 님이 작성:
> > > >
> > > > > +1
> > > > >
> > > > > tested about zombie processes
> > > > >
> > > > >
> > > > > On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev <
> > > cloverhearts...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > -Original Message-
> > > > > > From: Windy Qin [mailto:windyqinchaof...@163.com]
> > > > > > Sent: Friday, March 31, 2017 11:56 AM
> > > > > > To: dev 
> > > > > > Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > > >
> > > > > > +1
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > > WindyQin
> > > > > >
> > > > > > From: Mina Lee
> > > > > > Date: 2017-03-31 09:46
> > > > > > To: dev
> > > > > > Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > > > +1
> > > > > >
> > > > > > On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim <
> hss...@nflabs.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > > > > > > Thank you for your effort mina!
> > > > > > >
> > > > > > > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> > > > > > >
> > > > > > > > +1
> > > > > > > > Le 29 mars 2017 07:06, "Jeff Zhang"  a
> > écrit :
> > > > > > > >
> > > > > > > > > Thanks Jongyoul for explanation, let's improve it later.
> > > > > > > > >
> > > > > > > > > +1.
> > > > > > > > >
> > > > > > > > > * Build zeppelin from source successfully
> > > > > > > > > * Run pig tutorial using tez mode successfully
> > > > > > > > > * Run spark tutorial using livy interpreter successfully.
> > > > > > > > > * Verify interpreter fail error can be propagated to
> > frontend.
> > > > > > > > > * Verify the restart button works in several scenarios.
> Works
> > > > > > properly.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > > > > > > >
> > > > > > > > > > Jeff,
> > > > > > > > > >
> > > > > > > > > > Moon and I discuss the behaviors of clicking restart
> > buttons
> > > > > > > > > > from
> > > > > > > > > notebook
> > > > > > > > > > page and interpreter page. In your case, it's intended
> > fully.
> > > > > > > > > > For
> > > > > > > more
> > > > > > > > > > detail, In case of "per user", we can do the same thing
> in
> > > note
> > > > > > > > > > and interpreter pages, but in case of "per note", we
> cannot
> > > get
> > > > > > > > > > the exact
> > > > > > > > > note
> > > > > > > > > > when users click restart button in interpreter tab. Thus
> > Moon
> > > > > > > > > > and I
> > > > > > > > > decided
> > > > > > > > > > not to change original behaviors of interpreter page. It
> > > would
> > > > > > > > > > be
> > > > > > > > changed
> > > > > > > > > > when we add admin feature.
> > > > > > > > > >
> > > > > > > > > > Thanks for testing it.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Jongyoul
> > > > > > > > > >
> > > > > > > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang <
> > > zjf...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Might find another bug about restarting button. The
> > > > restarting
> > > > > > > button
> > > > > > > > > on
> > > > > > > > > > > note page behaves differently from that of interpreter
> > > page.
> > > > > > > > > > > This
> > > > > > > > > might
> > > > > 

[jira] [Created] (ZEPPELIN-2336) Note is refreshed on Note creation/deletion/rename

[Lee moon soo (JIRA)]

Lee moon soo created ZEPPELIN-2336:
--

 Summary: Note is refreshed on Note creation/deletion/rename
 Key: ZEPPELIN-2336
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2336
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.1
Reporter: Lee moon soo
Priority: Critical
 Fix For: 0.7.2


Open two browser windows, A, B.

One window A, open a notebook.
The other window B, try create / remove / rename note.

The note on browser window A is get refreshed, which is unnecessary.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2208: [HOTFIX][gh-pages] Fix Maven web link for INTERPRETER ...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2208
  
@felixcheung Thanks! 
CI failure is irrelevant with `gh-pages` change. Merge into gh-pages as a 
hotfix if there are no more comments on this. 


---
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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Felix Cheung]

+1

Tested bin, checked signature, ran through a bunch of tests, checked report 
mode, UI etc

I don't think it's a blocker:
When I search I see a list of note names but with empty white boxes under each 
of them. Isn't it suppose to show where the match is found?


From: Khalid Huseynov 
Sent: Thursday, March 30, 2017 9:27:01 PM
To: dev@zeppelin.apache.org
Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

+1

On Fri, Mar 31, 2017 at 12:32 PM, Ahyoung Ryu  wrote:

> +1
> tested binary package
>  - Spark and Python tutorial note
>  - Zombie process issue
>
> and could successfully build Zeppelin from source.
> Thanks always Mina for your effort.
>
>
> On Fri, Mar 31, 2017 at 12:20 PM, Anthony Corbacho <
> anthonycorba...@apache.org> wrote:
>
> > +1
> >
> > Tested with my usual cases.
> >
> > Thank you mina!!!
> >
> > On Fri, Mar 31, 2017 at 12:13 PM, Jun Kim  wrote:
> >
> > > +1
> > > 2017년 3월 31일 (금) 오후 12:13, Jongyoul Lee 님이 작성:
> > >
> > > > +1
> > > >
> > > > tested about zombie processes
> > > >
> > > >
> > > > On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev <
> > cloverhearts...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > -Original Message-
> > > > > From: Windy Qin [mailto:windyqinchaof...@163.com]
> > > > > Sent: Friday, March 31, 2017 11:56 AM
> > > > > To: dev 
> > > > > Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > >
> > > > > +1
> > > > >
> > > > >
> > > > >
> > > > > Thanks
> > > > > WindyQin
> > > > >
> > > > > From: Mina Lee
> > > > > Date: 2017-03-31 09:46
> > > > > To: dev
> > > > > Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > > +1
> > > > >
> > > > > On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  >
> > > > wrote:
> > > > >
> > > > > > +1
> > > > > > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > > > > > Thank you for your effort mina!
> > > > > >
> > > > > > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> > > > > >
> > > > > > > +1
> > > > > > > Le 29 mars 2017 07:06, "Jeff Zhang"  a
> écrit :
> > > > > > >
> > > > > > > > Thanks Jongyoul for explanation, let's improve it later.
> > > > > > > >
> > > > > > > > +1.
> > > > > > > >
> > > > > > > > * Build zeppelin from source successfully
> > > > > > > > * Run pig tutorial using tez mode successfully
> > > > > > > > * Run spark tutorial using livy interpreter successfully.
> > > > > > > > * Verify interpreter fail error can be propagated to
> frontend.
> > > > > > > > * Verify the restart button works in several scenarios. Works
> > > > > properly.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > > > > > >
> > > > > > > > > Jeff,
> > > > > > > > >
> > > > > > > > > Moon and I discuss the behaviors of clicking restart
> buttons
> > > > > > > > > from
> > > > > > > > notebook
> > > > > > > > > page and interpreter page. In your case, it's intended
> fully.
> > > > > > > > > For
> > > > > > more
> > > > > > > > > detail, In case of "per user", we can do the same thing in
> > note
> > > > > > > > > and interpreter pages, but in case of "per note", we cannot
> > get
> > > > > > > > > the exact
> > > > > > > > note
> > > > > > > > > when users click restart button in interpreter tab. Thus
> Moon
> > > > > > > > > and I
> > > > > > > > decided
> > > > > > > > > not to change original behaviors of interpreter page. It
> > would
> > > > > > > > > be
> > > > > > > changed
> > > > > > > > > when we add admin feature.
> > > > > > > > >
> > > > > > > > > Thanks for testing it.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Jongyoul
> > > > > > > > >
> > > > > > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang <
> > zjf...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Might find another bug about restarting button. The
> > > restarting
> > > > > > button
> > > > > > > > on
> > > > > > > > > > note page behaves differently from that of interpreter
> > page.
> > > > > > > > > > This
> > > > > > > > might
> > > > > > > > > > confuse users.
> > > > > > > > > >
> > > > > > > > > > e.g. For livy interpreter, if I click the restart button
> in
> > > > > > > > > > note
> > > > > > > page,
> > > > > > > > > then
> > > > > > > > > > only my livy session will be shutdown. But If I click the
> > > > > > > > > > restart
> > > > > > > > button
> > > > > > > > > in
> > > > > > > > > > interpreter page, all the sessions will be shut down.
> This
> > > > > > > > > > kind of differences will confuse users IMO.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > > > > > > >
> > > > > > > > > > > I propose the following RC to be released for the
> Apache
> > > > > > 

Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Khalid Huseynov]

+1

On Fri, Mar 31, 2017 at 12:32 PM, Ahyoung Ryu  wrote:

> +1
> tested binary package
>  - Spark and Python tutorial note
>  - Zombie process issue
>
> and could successfully build Zeppelin from source.
> Thanks always Mina for your effort.
>
>
> On Fri, Mar 31, 2017 at 12:20 PM, Anthony Corbacho <
> anthonycorba...@apache.org> wrote:
>
> > +1
> >
> > Tested with my usual cases.
> >
> > Thank you mina!!!
> >
> > On Fri, Mar 31, 2017 at 12:13 PM, Jun Kim  wrote:
> >
> > > +1
> > > 2017년 3월 31일 (금) 오후 12:13, Jongyoul Lee 님이 작성:
> > >
> > > > +1
> > > >
> > > > tested about zombie processes
> > > >
> > > >
> > > > On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev <
> > cloverhearts...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > -Original Message-
> > > > > From: Windy Qin [mailto:windyqinchaof...@163.com]
> > > > > Sent: Friday, March 31, 2017 11:56 AM
> > > > > To: dev 
> > > > > Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > >
> > > > > +1
> > > > >
> > > > >
> > > > >
> > > > > Thanks
> > > > > WindyQin
> > > > >
> > > > > From: Mina Lee
> > > > > Date: 2017-03-31 09:46
> > > > > To: dev
> > > > > Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > > +1
> > > > >
> > > > > On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  >
> > > > wrote:
> > > > >
> > > > > > +1
> > > > > > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > > > > > Thank you for your effort mina!
> > > > > >
> > > > > > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> > > > > >
> > > > > > > +1
> > > > > > > Le 29 mars 2017 07:06, "Jeff Zhang"  a
> écrit :
> > > > > > >
> > > > > > > > Thanks Jongyoul for explanation, let's improve it later.
> > > > > > > >
> > > > > > > > +1.
> > > > > > > >
> > > > > > > > * Build zeppelin from source successfully
> > > > > > > > * Run pig tutorial using tez mode successfully
> > > > > > > > * Run spark tutorial using livy interpreter successfully.
> > > > > > > > * Verify interpreter fail error can be propagated to
> frontend.
> > > > > > > > * Verify the restart button works in several scenarios. Works
> > > > > properly.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > > > > > >
> > > > > > > > > Jeff,
> > > > > > > > >
> > > > > > > > > Moon and I discuss the behaviors of clicking restart
> buttons
> > > > > > > > > from
> > > > > > > > notebook
> > > > > > > > > page and interpreter page. In your case, it's intended
> fully.
> > > > > > > > > For
> > > > > > more
> > > > > > > > > detail, In case of "per user", we can do the same thing in
> > note
> > > > > > > > > and interpreter pages, but in case of "per note", we cannot
> > get
> > > > > > > > > the exact
> > > > > > > > note
> > > > > > > > > when users click restart button in interpreter tab. Thus
> Moon
> > > > > > > > > and I
> > > > > > > > decided
> > > > > > > > > not to change original behaviors of interpreter page. It
> > would
> > > > > > > > > be
> > > > > > > changed
> > > > > > > > > when we add admin feature.
> > > > > > > > >
> > > > > > > > > Thanks for testing it.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Jongyoul
> > > > > > > > >
> > > > > > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang <
> > zjf...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Might find another bug about restarting button. The
> > > restarting
> > > > > > button
> > > > > > > > on
> > > > > > > > > > note page behaves differently from that of interpreter
> > page.
> > > > > > > > > > This
> > > > > > > > might
> > > > > > > > > > confuse users.
> > > > > > > > > >
> > > > > > > > > > e.g. For livy interpreter, if I click the restart button
> in
> > > > > > > > > > note
> > > > > > > page,
> > > > > > > > > then
> > > > > > > > > > only my livy session will be shutdown. But If I click the
> > > > > > > > > > restart
> > > > > > > > button
> > > > > > > > > in
> > > > > > > > > > interpreter page, all the sessions will be shut down.
> This
> > > > > > > > > > kind of differences will confuse users IMO.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > > > > > > >
> > > > > > > > > > > I propose the following RC to be released for the
> Apache
> > > > > > > > > > > Zeppelin
> > > > > > > > 0.7.1
> > > > > > > > > > > release.
> > > > > > > > > > >
> > > > > > > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b
> > 58e44b5be8
> > > > > > > > > > > which
> > > > > > is
> > > > > > > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > > > > > > >
> > > > > > > > > > > https://git-wip-us.apache.org/
> > repos/asf?p=zeppelin.git;h=
> > > > > > > > > > refs/tags/v0.7.1-rc3
> > > > > > > > > > >
> > > > > > > > > > > 

[GitHub] zeppelin issue #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
Nice!!


---
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 #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

[benoyantony]

Github user benoyantony commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
Thanks for the prompt review, @zjffdu .


---
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: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Ahyoung Ryu]

+1
tested binary package
 - Spark and Python tutorial note
 - Zombie process issue

and could successfully build Zeppelin from source.
Thanks always Mina for your effort.


On Fri, Mar 31, 2017 at 12:20 PM, Anthony Corbacho <
anthonycorba...@apache.org> wrote:

> +1
>
> Tested with my usual cases.
>
> Thank you mina!!!
>
> On Fri, Mar 31, 2017 at 12:13 PM, Jun Kim  wrote:
>
> > +1
> > 2017년 3월 31일 (금) 오후 12:13, Jongyoul Lee 님이 작성:
> >
> > > +1
> > >
> > > tested about zombie processes
> > >
> > >
> > > On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev <
> cloverhearts...@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > -Original Message-
> > > > From: Windy Qin [mailto:windyqinchaof...@163.com]
> > > > Sent: Friday, March 31, 2017 11:56 AM
> > > > To: dev 
> > > > Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > >
> > > > +1
> > > >
> > > >
> > > >
> > > > Thanks
> > > > WindyQin
> > > >
> > > > From: Mina Lee
> > > > Date: 2017-03-31 09:46
> > > > To: dev
> > > > Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > > +1
> > > >
> > > > On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim 
> > > wrote:
> > > >
> > > > > +1
> > > > > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > > > > Thank you for your effort mina!
> > > > >
> > > > > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> > > > >
> > > > > > +1
> > > > > > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> > > > > >
> > > > > > > Thanks Jongyoul for explanation, let's improve it later.
> > > > > > >
> > > > > > > +1.
> > > > > > >
> > > > > > > * Build zeppelin from source successfully
> > > > > > > * Run pig tutorial using tez mode successfully
> > > > > > > * Run spark tutorial using livy interpreter successfully.
> > > > > > > * Verify interpreter fail error can be propagated to frontend.
> > > > > > > * Verify the restart button works in several scenarios. Works
> > > > properly.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > > > > >
> > > > > > > > Jeff,
> > > > > > > >
> > > > > > > > Moon and I discuss the behaviors of clicking restart buttons
> > > > > > > > from
> > > > > > > notebook
> > > > > > > > page and interpreter page. In your case, it's intended fully.
> > > > > > > > For
> > > > > more
> > > > > > > > detail, In case of "per user", we can do the same thing in
> note
> > > > > > > > and interpreter pages, but in case of "per note", we cannot
> get
> > > > > > > > the exact
> > > > > > > note
> > > > > > > > when users click restart button in interpreter tab. Thus Moon
> > > > > > > > and I
> > > > > > > decided
> > > > > > > > not to change original behaviors of interpreter page. It
> would
> > > > > > > > be
> > > > > > changed
> > > > > > > > when we add admin feature.
> > > > > > > >
> > > > > > > > Thanks for testing it.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Jongyoul
> > > > > > > >
> > > > > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang <
> zjf...@gmail.com
> > >
> > > > > wrote:
> > > > > > > >
> > > > > > > > > Might find another bug about restarting button. The
> > restarting
> > > > > button
> > > > > > > on
> > > > > > > > > note page behaves differently from that of interpreter
> page.
> > > > > > > > > This
> > > > > > > might
> > > > > > > > > confuse users.
> > > > > > > > >
> > > > > > > > > e.g. For livy interpreter, if I click the restart button in
> > > > > > > > > note
> > > > > > page,
> > > > > > > > then
> > > > > > > > > only my livy session will be shutdown. But If I click the
> > > > > > > > > restart
> > > > > > > button
> > > > > > > > in
> > > > > > > > > interpreter page, all the sessions will be shut down. This
> > > > > > > > > kind of differences will confuse users IMO.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > > > > > >
> > > > > > > > > > I propose the following RC to be released for the Apache
> > > > > > > > > > Zeppelin
> > > > > > > 0.7.1
> > > > > > > > > > release.
> > > > > > > > > >
> > > > > > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b
> 58e44b5be8
> > > > > > > > > > which
> > > > > is
> > > > > > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > > > > > >
> > > > > > > > > > https://git-wip-us.apache.org/
> repos/asf?p=zeppelin.git;h=
> > > > > > > > > refs/tags/v0.7.1-rc3
> > > > > > > > > >
> > > > > > > > > > The release archives (tgz), signature, and checksums are
> > > > > > > > > > here
> > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > > > > > 7.1-rc3/
> > > > > > > > > >
> > > > > > > > > > The release candidate consists of the following source
> > > > > distribution
> > > > > > > > > archive
> > > > > > > > > > zeppelin-0.7.1.tgz
> > > > > > > > > >
> > > > > > > > > > In addition, 

[GitHub] zeppelin issue #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
@1ambda Yup thanks for letting me know 


---
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 #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
Let me rebase and comment again.


---
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: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Anthony Corbacho]

+1

Tested with my usual cases.

Thank you mina!!!

On Fri, Mar 31, 2017 at 12:13 PM, Jun Kim  wrote:

> +1
> 2017년 3월 31일 (금) 오후 12:13, Jongyoul Lee 님이 작성:
>
> > +1
> >
> > tested about zombie processes
> >
> >
> > On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev 
> > wrote:
> >
> > > +1
> > >
> > > -Original Message-
> > > From: Windy Qin [mailto:windyqinchaof...@163.com]
> > > Sent: Friday, March 31, 2017 11:56 AM
> > > To: dev 
> > > Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > >
> > > +1
> > >
> > >
> > >
> > > Thanks
> > > WindyQin
> > >
> > > From: Mina Lee
> > > Date: 2017-03-31 09:46
> > > To: dev
> > > Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> > > +1
> > >
> > > On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim 
> > wrote:
> > >
> > > > +1
> > > > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > > > Thank you for your effort mina!
> > > >
> > > > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> > > >
> > > > > +1
> > > > > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> > > > >
> > > > > > Thanks Jongyoul for explanation, let's improve it later.
> > > > > >
> > > > > > +1.
> > > > > >
> > > > > > * Build zeppelin from source successfully
> > > > > > * Run pig tutorial using tez mode successfully
> > > > > > * Run spark tutorial using livy interpreter successfully.
> > > > > > * Verify interpreter fail error can be propagated to frontend.
> > > > > > * Verify the restart button works in several scenarios. Works
> > > properly.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > > > >
> > > > > > > Jeff,
> > > > > > >
> > > > > > > Moon and I discuss the behaviors of clicking restart buttons
> > > > > > > from
> > > > > > notebook
> > > > > > > page and interpreter page. In your case, it's intended fully.
> > > > > > > For
> > > > more
> > > > > > > detail, In case of "per user", we can do the same thing in note
> > > > > > > and interpreter pages, but in case of "per note", we cannot get
> > > > > > > the exact
> > > > > > note
> > > > > > > when users click restart button in interpreter tab. Thus Moon
> > > > > > > and I
> > > > > > decided
> > > > > > > not to change original behaviors of interpreter page. It would
> > > > > > > be
> > > > > changed
> > > > > > > when we add admin feature.
> > > > > > >
> > > > > > > Thanks for testing it.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Jongyoul
> > > > > > >
> > > > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang  >
> > > > wrote:
> > > > > > >
> > > > > > > > Might find another bug about restarting button. The
> restarting
> > > > button
> > > > > > on
> > > > > > > > note page behaves differently from that of interpreter page.
> > > > > > > > This
> > > > > > might
> > > > > > > > confuse users.
> > > > > > > >
> > > > > > > > e.g. For livy interpreter, if I click the restart button in
> > > > > > > > note
> > > > > page,
> > > > > > > then
> > > > > > > > only my livy session will be shutdown. But If I click the
> > > > > > > > restart
> > > > > > button
> > > > > > > in
> > > > > > > > interpreter page, all the sessions will be shut down. This
> > > > > > > > kind of differences will confuse users IMO.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > > > > >
> > > > > > > > > I propose the following RC to be released for the Apache
> > > > > > > > > Zeppelin
> > > > > > 0.7.1
> > > > > > > > > release.
> > > > > > > > >
> > > > > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8
> > > > > > > > > which
> > > > is
> > > > > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > > > > >
> > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > > > > > refs/tags/v0.7.1-rc3
> > > > > > > > >
> > > > > > > > > The release archives (tgz), signature, and checksums are
> > > > > > > > > here
> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > > > > 7.1-rc3/
> > > > > > > > >
> > > > > > > > > The release candidate consists of the following source
> > > > distribution
> > > > > > > > archive
> > > > > > > > > zeppelin-0.7.1.tgz
> > > > > > > > >
> > > > > > > > > In addition, the following supplementary binary
> > > > > > > > > distributions are
> > > > > > > > provided
> > > > > > > > > for user convenience at the same location
> > > > > > > > > zeppelin-0.7.1-bin-all.tgz zeppelin-0.7.1-bin-netinst.tgz
> > > > > > > > >
> > > > > > > > > The maven artifacts are here
> > > > > > > > > https://repository.apache.org/content/repositories/
> > > > > > > > orgapachezeppelin-1035
> > > > > > > > >
> > > > > > > > > You can find the KEYS file here:
> > > > > > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > > > > > >

[GitHub] zeppelin issue #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
Thanks @benoyantony , LGTM


---
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: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Jongyoul Lee]

+1

tested about zombie processes


On Fri, 31 Mar 2017 at 12:03 CloverHeartsDev 
wrote:

> +1
>
> -Original Message-
> From: Windy Qin [mailto:windyqinchaof...@163.com]
> Sent: Friday, March 31, 2017 11:56 AM
> To: dev 
> Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
>
> +1
>
>
>
> Thanks
> WindyQin
>
> From: Mina Lee
> Date: 2017-03-31 09:46
> To: dev
> Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
> +1
>
> On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  wrote:
>
> > +1
> > Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> > Thank you for your effort mina!
> >
> > 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
> >
> > > +1
> > > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> > >
> > > > Thanks Jongyoul for explanation, let's improve it later.
> > > >
> > > > +1.
> > > >
> > > > * Build zeppelin from source successfully
> > > > * Run pig tutorial using tez mode successfully
> > > > * Run spark tutorial using livy interpreter successfully.
> > > > * Verify interpreter fail error can be propagated to frontend.
> > > > * Verify the restart button works in several scenarios. Works
> properly.
> > > >
> > > >
> > > >
> > > >
> > > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > > >
> > > > > Jeff,
> > > > >
> > > > > Moon and I discuss the behaviors of clicking restart buttons
> > > > > from
> > > > notebook
> > > > > page and interpreter page. In your case, it's intended fully.
> > > > > For
> > more
> > > > > detail, In case of "per user", we can do the same thing in note
> > > > > and interpreter pages, but in case of "per note", we cannot get
> > > > > the exact
> > > > note
> > > > > when users click restart button in interpreter tab. Thus Moon
> > > > > and I
> > > > decided
> > > > > not to change original behaviors of interpreter page. It would
> > > > > be
> > > changed
> > > > > when we add admin feature.
> > > > >
> > > > > Thanks for testing it.
> > > > >
> > > > > Regards,
> > > > > Jongyoul
> > > > >
> > > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang 
> > wrote:
> > > > >
> > > > > > Might find another bug about restarting button. The restarting
> > button
> > > > on
> > > > > > note page behaves differently from that of interpreter page.
> > > > > > This
> > > > might
> > > > > > confuse users.
> > > > > >
> > > > > > e.g. For livy interpreter, if I click the restart button in
> > > > > > note
> > > page,
> > > > > then
> > > > > > only my livy session will be shutdown. But If I click the
> > > > > > restart
> > > > button
> > > > > in
> > > > > > interpreter page, all the sessions will be shut down. This
> > > > > > kind of differences will confuse users IMO.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > > >
> > > > > > > I propose the following RC to be released for the Apache
> > > > > > > Zeppelin
> > > > 0.7.1
> > > > > > > release.
> > > > > > >
> > > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8
> > > > > > > which
> > is
> > > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > > >
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > > > refs/tags/v0.7.1-rc3
> > > > > > >
> > > > > > > The release archives (tgz), signature, and checksums are
> > > > > > > here
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > > 7.1-rc3/
> > > > > > >
> > > > > > > The release candidate consists of the following source
> > distribution
> > > > > > archive
> > > > > > > zeppelin-0.7.1.tgz
> > > > > > >
> > > > > > > In addition, the following supplementary binary
> > > > > > > distributions are
> > > > > > provided
> > > > > > > for user convenience at the same location
> > > > > > > zeppelin-0.7.1-bin-all.tgz zeppelin-0.7.1-bin-netinst.tgz
> > > > > > >
> > > > > > > The maven artifacts are here
> > > > > > > https://repository.apache.org/content/repositories/
> > > > > > orgapachezeppelin-1035
> > > > > > >
> > > > > > > You can find the KEYS file here:
> > > > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > > > >
> > > > > > > Release notes available at
> > > > > > >
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > version=12339166=12316221
> > > > > > >
> > > > > > > Vote will be open for next 72 hours (close at 04:00 31/Mar
> PDT).
> > > > > > >
> > > > > > > [ ] +1 approve
> > > > > > > [ ] 0 no opinion
> > > > > > > [ ] -1 disapprove (and reason why)
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 이종열, Jongyoul Lee, 李宗烈
> > > > > http://madeng.net
> > > > >
> > > >
> > >
> >
>
> --
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin issue #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
@cloverhearts Great! Tested this patch and it works well as you described. 
 - Before
![screen shot 2017-03-31 at 11 58 32 
am](https://cloud.githubusercontent.com/assets/10060731/24534665/58d81178-160a-11e7-88af-c1bd539d2252.png)

 - After 
![screen shot 2017-03-31 at 12 04 38 
pm](https://cloud.githubusercontent.com/assets/10060731/24534668/5c20511a-160a-11e7-921a-73e08197578b.png)

If @astroshim feedback can also be addressed, looks GOOD to me.   


---
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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
@cloverhearts It looks also great!  👍 


---
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: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[CloverHeartsDev]

+1

-Original Message-
From: Windy Qin [mailto:windyqinchaof...@163.com] 
Sent: Friday, March 31, 2017 11:56 AM
To: dev 
Subject: Re: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

+1



Thanks
WindyQin
 
From: Mina Lee
Date: 2017-03-31 09:46
To: dev
Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
+1
 
On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  wrote:
 
> +1
> Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> Thank you for your effort mina!
>
> 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
>
> > +1
> > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> >
> > > Thanks Jongyoul for explanation, let's improve it later.
> > >
> > > +1.
> > >
> > > * Build zeppelin from source successfully
> > > * Run pig tutorial using tez mode successfully
> > > * Run spark tutorial using livy interpreter successfully.
> > > * Verify interpreter fail error can be propagated to frontend.
> > > * Verify the restart button works in several scenarios. Works properly.
> > >
> > >
> > >
> > >
> > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > >
> > > > Jeff,
> > > >
> > > > Moon and I discuss the behaviors of clicking restart buttons 
> > > > from
> > > notebook
> > > > page and interpreter page. In your case, it's intended fully. 
> > > > For
> more
> > > > detail, In case of "per user", we can do the same thing in note 
> > > > and interpreter pages, but in case of "per note", we cannot get 
> > > > the exact
> > > note
> > > > when users click restart button in interpreter tab. Thus Moon 
> > > > and I
> > > decided
> > > > not to change original behaviors of interpreter page. It would 
> > > > be
> > changed
> > > > when we add admin feature.
> > > >
> > > > Thanks for testing it.
> > > >
> > > > Regards,
> > > > Jongyoul
> > > >
> > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang 
> wrote:
> > > >
> > > > > Might find another bug about restarting button. The restarting
> button
> > > on
> > > > > note page behaves differently from that of interpreter page.  
> > > > > This
> > > might
> > > > > confuse users.
> > > > >
> > > > > e.g. For livy interpreter, if I click the restart button in 
> > > > > note
> > page,
> > > > then
> > > > > only my livy session will be shutdown. But If I click the 
> > > > > restart
> > > button
> > > > in
> > > > > interpreter page, all the sessions will be shut down. This 
> > > > > kind of differences will confuse users IMO.
> > > > >
> > > > >
> > > > >
> > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > >
> > > > > > I propose the following RC to be released for the Apache 
> > > > > > Zeppelin
> > > 0.7.1
> > > > > > release.
> > > > > >
> > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 
> > > > > > which
> is
> > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > >
> > > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > > refs/tags/v0.7.1-rc3
> > > > > >
> > > > > > The release archives (tgz), signature, and checksums are 
> > > > > > here https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > 7.1-rc3/
> > > > > >
> > > > > > The release candidate consists of the following source
> distribution
> > > > > archive
> > > > > > zeppelin-0.7.1.tgz
> > > > > >
> > > > > > In addition, the following supplementary binary 
> > > > > > distributions are
> > > > > provided
> > > > > > for user convenience at the same location 
> > > > > > zeppelin-0.7.1-bin-all.tgz zeppelin-0.7.1-bin-netinst.tgz
> > > > > >
> > > > > > The maven artifacts are here 
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapachezeppelin-1035
> > > > > >
> > > > > > You can find the KEYS file here:
> > > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > > >
> > > > > > Release notes available at
> > > > > >
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > version=12339166=12316221
> > > > > >
> > > > > > Vote will be open for next 72 hours (close at 04:00 31/Mar PDT).
> > > > > >
> > > > > > [ ] +1 approve
> > > > > > [ ] 0 no opinion
> > > > > > [ ] -1 disapprove (and reason why)
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 이종열, Jongyoul Lee, 李宗烈
> > > > http://madeng.net
> > > >
> > >
> >
>

[GitHub] zeppelin issue #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

[benoyantony]

Github user benoyantony commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
That seems to have worked. thanks @zjffdu .


---
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: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Windy Qin]

+1



Thanks
WindyQin
 
From: Mina Lee
Date: 2017-03-31 09:46
To: dev
Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)
+1
 
On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  wrote:
 
> +1
> Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> Thank you for your effort mina!
>
> 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
>
> > +1
> > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> >
> > > Thanks Jongyoul for explanation, let's improve it later.
> > >
> > > +1.
> > >
> > > * Build zeppelin from source successfully
> > > * Run pig tutorial using tez mode successfully
> > > * Run spark tutorial using livy interpreter successfully.
> > > * Verify interpreter fail error can be propagated to frontend.
> > > * Verify the restart button works in several scenarios. Works properly.
> > >
> > >
> > >
> > >
> > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > >
> > > > Jeff,
> > > >
> > > > Moon and I discuss the behaviors of clicking restart buttons from
> > > notebook
> > > > page and interpreter page. In your case, it's intended fully. For
> more
> > > > detail, In case of "per user", we can do the same thing in note and
> > > > interpreter pages, but in case of "per note", we cannot get the exact
> > > note
> > > > when users click restart button in interpreter tab. Thus Moon and I
> > > decided
> > > > not to change original behaviors of interpreter page. It would be
> > changed
> > > > when we add admin feature.
> > > >
> > > > Thanks for testing it.
> > > >
> > > > Regards,
> > > > Jongyoul
> > > >
> > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang 
> wrote:
> > > >
> > > > > Might find another bug about restarting button. The restarting
> button
> > > on
> > > > > note page behaves differently from that of interpreter page.  This
> > > might
> > > > > confuse users.
> > > > >
> > > > > e.g. For livy interpreter, if I click the restart button in note
> > page,
> > > > then
> > > > > only my livy session will be shutdown. But If I click the restart
> > > button
> > > > in
> > > > > interpreter page, all the sessions will be shut down. This kind of
> > > > > differences will confuse users IMO.
> > > > >
> > > > >
> > > > >
> > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > >
> > > > > > I propose the following RC to be released for the Apache Zeppelin
> > > 0.7.1
> > > > > > release.
> > > > > >
> > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which
> is
> > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > >
> > > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > > refs/tags/v0.7.1-rc3
> > > > > >
> > > > > > The release archives (tgz), signature, and checksums are here
> > > > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > 7.1-rc3/
> > > > > >
> > > > > > The release candidate consists of the following source
> distribution
> > > > > archive
> > > > > > zeppelin-0.7.1.tgz
> > > > > >
> > > > > > In addition, the following supplementary binary distributions are
> > > > > provided
> > > > > > for user convenience at the same location
> > > > > > zeppelin-0.7.1-bin-all.tgz
> > > > > > zeppelin-0.7.1-bin-netinst.tgz
> > > > > >
> > > > > > The maven artifacts are here
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapachezeppelin-1035
> > > > > >
> > > > > > You can find the KEYS file here:
> > > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > > >
> > > > > > Release notes available at
> > > > > >
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > version=12339166=12316221
> > > > > >
> > > > > > Vote will be open for next 72 hours (close at 04:00 31/Mar PDT).
> > > > > >
> > > > > > [ ] +1 approve
> > > > > > [ ] 0 no opinion
> > > > > > [ ] -1 disapprove (and reason why)
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 이종열, Jongyoul Lee, 李宗烈
> > > > http://madeng.net
> > > >
> > >
> >
>

[GitHub] zeppelin issue #2177: [ZEPPELIN-2301] DON'T overwrite editor text when note ...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2177
  
Sure. I'll test it and get back you soon. 


---
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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
@astroshim 
So what about `__zeppelin__`?
Actually, I feel similar like a python system environment word
It is less likely to be redefined by other libraries.


---
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 #2189: [branch-0.7] Minor styling for Helium menu

[AhyoungRyu]

Github user AhyoungRyu closed the pull request at:

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


---
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 #2189: [branch-0.7] Minor styling for Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2189
  
I already merged into `branch-0.7` but not closed yet. So closing this 
manually.


---
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 #2208: [HOTFIX][gh-pages] Fix Maven web link for INTER...

[AhyoungRyu]

GitHub user AhyoungRyu opened a pull request:

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

[HOTFIX][gh-pages] Fix Maven web link for INTERPRETER type pkg

### What is this PR for?
In current https://zeppelin.apache.org/helium_packages.html page, 
`INTERPRETER` type package web link is wrong. It should point Maven web link 
not npm. So I fixed it. 

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

### What is the Jira issue?
N/A

### How should this be tested?
Run the website(`gh-pages`) locally as described in 
[here](https://github.com/apache/zeppelin/tree/gh-pages#run-website) and click 
any `INTERPRETER` type of package name.

### Screenshots (if appropriate)
 - Before 

![maven_link_before](https://cloud.githubusercontent.com/assets/10060731/24534152/17780970-1607-11e7-82ef-8876590477b8.gif)

 - After

![maven_link_after](https://cloud.githubusercontent.com/assets/10060731/24534153/197ab100-1607-11e7-92a9-1718f0e5b9cb.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/AhyoungRyu/zeppelin fix/mavenLink

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

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


commit 9fdb50b5506b3a9b90690ed08a5e17b25b0490b8
Author: AhyoungRyu 
Date:   2017-03-31T02:37:11Z

Fix maven serach link for INTERPRETER type pkg




---
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-2335) Setting for maxClassfileName_ will cause class not found exception

[wuyonghua (JIRA)]

wuyonghua created ZEPPELIN-2335:
---

 Summary: Setting for maxClassfileName_ will cause class not found 
exception
 Key: ZEPPELIN-2335
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2335
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Reporter: wuyonghua


Code to run:
object Shell extends Serializable { // show
org.apache.spark.sql.catalyst.encoders.OuterScopes.addOuterScope(this)
case class Step4_Class(`id` : String,`factory` : String)
def main() {
def _1002() : org.apache.spark.rdd.RDD[String] = {
var retval : org.apache.spark.rdd.RDD[String] = null
retval = sc.parallelize(Array(
"id,factory",
",Nanjing"
))
retval
}
val __1002 = _1002()
def _1003(source1 : org.apache.spark.rdd.RDD[String]) : 
org.apache.spark.rdd.RDD[Step4_Class] = {
val retval : org.apache.spark.rdd.RDD[Step4_Class] = source1 
.filter(line => line != "id,factory") .mapPartitions(lines => 
{
  val csvParser = new au.com.bytecode.opencsv.CSVParser(',')
  lines.flatMap {
line => {
  try {
val field = csvParser.parseLine(line)
Seq(Step4_Class(field(0),field(1)))
  } catch {
case e: Throwable => {
  Seq()
}
  }
}
  }
}, 
true)
retval
}
val __1003 = _1003(__1002)

def _1004(source2 : org.apache.spark.rdd.RDD[Step4_Class]) : 
org.apache.spark.sql.DataFrame = {
val __mapresult2=source2.toDF("__2id","__2factory")
val retval=__mapresult2
retval
}
val __1004 = _1004(__1003)
}
}
Shell.main()

Exception:
java.lang.ClassNotFoundException: no Java class corresponding to class $iw found
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.scala$reflect$runtime$JavaMirrors$JavaMirror$$anonfun$$noClass$1(JavaMirrors.scala:1204)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1242)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache$$anonfun$toJava$1.apply(TwoWayCaches.scala:49)
  at scala.reflect.runtime.Gil$class.gilSynchronized(Gil.scala:19)
  at scala.reflect.runtime.JavaUniverse.gilSynchronized(JavaUniverse.scala:16)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache.toJava(TwoWayCaches.scala:44)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror.classToJava(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1218)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache$$anonfun$toJava$1.apply(TwoWayCaches.scala:49)
  at scala.reflect.runtime.Gil$class.gilSynchronized(Gil.scala:19)
  at scala.reflect.runtime.JavaUniverse.gilSynchronized(JavaUniverse.scala:16)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache.toJava(TwoWayCaches.scala:44)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror.classToJava(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1218)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache$$anonfun$toJava$1.apply(TwoWayCaches.scala:49)
  at scala.reflect.runtime.Gil$class.gilSynchronized(Gil.scala:19)
  at scala.reflect.runtime.JavaUniverse.gilSynchronized(JavaUniverse.scala:16)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache.toJava(TwoWayCaches.scala:44)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror.classToJava(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1218)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache$$anonfun$toJava$1.apply(TwoWayCaches.scala:49)
  at scala.reflect.runtime.Gil$class.gilSynchronized(Gil.scala:19)
  at scala.reflect.runtime.JavaUniverse.gilSynchronized(JavaUniverse.scala:16)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache.toJava(TwoWayCaches.scala:44)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror.classToJava(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1218)
  at 
scala.reflect.runtime.JavaMirrors$JavaMirror$$anonfun$classToJava$1.apply(JavaMirrors.scala:1203)
  at 
scala.reflect.runtime.TwoWayCaches$TwoWayCache$$anonfun$toJava$1.apply(TwoWayCaches.scala:49)
  at scala.reflect.runtime.Gil$class.gilSynchronized(Gil.scala:19)
  at 

[GitHub] zeppelin issue #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
Looks great. 
one thing i worrying about is that the `_zc` can be possibly used by user 
easily?
how about assigning more unique key word like `__zc__` ?


---
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 #2200: [HOTFIX] Remove unintended characters from r tu...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2202: [Minor][ZEPPELIN-2328] Separate Helium related docs fr...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2202
  
Thanks @1ambda for the confirmation!
Merge into master if there are no more comments on this. 


---
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 #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
Merge into master if there are no more comments on this. 


---
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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Mina Lee]

+1

On Wed, Mar 29, 2017 at 4:39 PM Hyung Sung Shim  wrote:

> +1
> Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
> Thank you for your effort mina!
>
> 2017-03-29 16:04 GMT+09:00 DuyHai Doan :
>
> > +1
> > Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
> >
> > > Thanks Jongyoul for explanation, let's improve it later.
> > >
> > > +1.
> > >
> > > * Build zeppelin from source successfully
> > > * Run pig tutorial using tez mode successfully
> > > * Run spark tutorial using livy interpreter successfully.
> > > * Verify interpreter fail error can be propagated to frontend.
> > > * Verify the restart button works in several scenarios. Works properly.
> > >
> > >
> > >
> > >
> > > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> > >
> > > > Jeff,
> > > >
> > > > Moon and I discuss the behaviors of clicking restart buttons from
> > > notebook
> > > > page and interpreter page. In your case, it's intended fully. For
> more
> > > > detail, In case of "per user", we can do the same thing in note and
> > > > interpreter pages, but in case of "per note", we cannot get the exact
> > > note
> > > > when users click restart button in interpreter tab. Thus Moon and I
> > > decided
> > > > not to change original behaviors of interpreter page. It would be
> > changed
> > > > when we add admin feature.
> > > >
> > > > Thanks for testing it.
> > > >
> > > > Regards,
> > > > Jongyoul
> > > >
> > > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang 
> wrote:
> > > >
> > > > > Might find another bug about restarting button. The restarting
> button
> > > on
> > > > > note page behaves differently from that of interpreter page.  This
> > > might
> > > > > confuse users.
> > > > >
> > > > > e.g. For livy interpreter, if I click the restart button in note
> > page,
> > > > then
> > > > > only my livy session will be shutdown. But If I click the restart
> > > button
> > > > in
> > > > > interpreter page, all the sessions will be shut down. This kind of
> > > > > differences will confuse users IMO.
> > > > >
> > > > >
> > > > >
> > > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > > >
> > > > > > I propose the following RC to be released for the Apache Zeppelin
> > > 0.7.1
> > > > > > release.
> > > > > >
> > > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which
> is
> > > > > > corresponds to the tag v0.7.1-rc3:
> > > > > >
> > > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > > refs/tags/v0.7.1-rc3
> > > > > >
> > > > > > The release archives (tgz), signature, and checksums are here
> > > > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> > 7.1-rc3/
> > > > > >
> > > > > > The release candidate consists of the following source
> distribution
> > > > > archive
> > > > > > zeppelin-0.7.1.tgz
> > > > > >
> > > > > > In addition, the following supplementary binary distributions are
> > > > > provided
> > > > > > for user convenience at the same location
> > > > > > zeppelin-0.7.1-bin-all.tgz
> > > > > > zeppelin-0.7.1-bin-netinst.tgz
> > > > > >
> > > > > > The maven artifacts are here
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapachezeppelin-1035
> > > > > >
> > > > > > You can find the KEYS file here:
> > > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > > >
> > > > > > Release notes available at
> > > > > >
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > version=12339166=12316221
> > > > > >
> > > > > > Vote will be open for next 72 hours (close at 04:00 31/Mar PDT).
> > > > > >
> > > > > > [ ] +1 approve
> > > > > > [ ] 0 no opinion
> > > > > > [ ] -1 disapprove (and reason why)
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 이종열, Jongyoul Lee, 李宗烈
> > > > http://madeng.net
> > > >
> > >
> >
>

[GitHub] zeppelin issue #2195: [ZEPPELIN-2319] new methods for ZeppelinContext

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2195
  
Sorry for late response. @meniluca I am very interested in your scenario. 
It make sense to me for adding these api, another concern is whether it is more 
proper to expose it via ui or expose this api directly ? Any advantage for 
exposing it via api directly for your scenario ? And it would be better to add 
test case for it 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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
Great! Then, Please close issue and re-open :) then jenkins will be 
triggered again.


---
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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

[markito]

Github user markito commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
@1ambda indeed! I've restarted the CI job and now it's all green! 
https://travis-ci.org/markito/zeppelin/builds/216598188


---
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 #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
Thanks for review! @AhyoungRyu, @soralee


---
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 #2207: [Zeppelin-802] Support for Zeppelin Context red...

[cloverhearts]

GitHub user cloverhearts opened a pull request:

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

[Zeppelin-802] Support for Zeppelin Context redefinition on Python and 
Pyspark 

### What is this PR for?
If you override the reserved word ZeppelinContext such as `z` in the python 
language, the whole paragraph output problem occurred.
I have taken care to avoid this issue.

`z` == `_zc` == zeppelin context


### What type of PR is it?
Improvement

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

### How should this be tested?
The error should not occur in the following situations:
```
%python
z = 1
print("Hello Zeppelin")
```

```
%pyspark
z = 1
print("Hello Zeppelin")
```


### Screenshots (if appropriate)

 before
![replace zeppelin 
context-err](https://cloud.githubusercontent.com/assets/10525473/24521772/319946be-15c8-11e7-96cf-7fdf41c70a66.png)

 after
![replace zeppelin 
context](https://cloud.githubusercontent.com/assets/10525473/24521775/349fa7cc-15c8-11e7-8fe4-4f3f5597deff.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/cloverhearts/zeppelin 
ZEPPELIN-802-pyspark-zeppelin-context

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

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


commit 7edb1ad4196f4d9e9791545ad25980727ad418db
Author: CloverHearts 
Date:   2017-03-30T18:26:07Z

replace name zeppelin context on pyspark

commit 2d0ea1a030109243a7d530d0e88793859b3f9a14
Author: CloverHearts 
Date:   2017-03-30T18:35:28Z

added test code

commit b54209da0bd60ce0ae1e46a41ed1695e5fa442b8
Author: CloverHearts 
Date:   2017-03-30T18:44:53Z

fix pyspark test case

commit 0eaf9a896c30037dd4e51dc18df0a2c5b9abf69c
Author: CloverHearts 
Date:   2017-03-30T18:46:08Z

replace name zeppelin context on python

commit f3805b3b73c533fc8dabcc39c15dfcecae0259a4
Author: CloverHearts 
Date:   2017-03-30T18:46:27Z

added test case on python




---
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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
I am not sure but the failed test is due to one of flaky tests. Please 
restart it.

```

Results :

Tests in error: 
  InterpreterIT.testShowDescriptionOnInterpreterCreate:69 » 
ElementNotVisible El...
```


---
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 #2202: [Minor][ZEPPELIN-2328] Separate Helium related docs fr...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2202
  
Great!


---
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 #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

[benoyantony]

Github user benoyantony commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
There seems to be a problem with Jenkins as the error is " 
java.io.IOException: Remote call on ubuntu-2 failed". Any idea on howto 
overcome this ?

The travis build has all checks passed. 


---
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-2334) S3NotebookRepo does not play well with shiro multiuser auth

[Luis Guzman (JIRA)]

Luis Guzman created ZEPPELIN-2334:
-

 Summary: S3NotebookRepo does not play well with shiro multiuser 
auth
 Key: ZEPPELIN-2334
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2334
 Project: Zeppelin
  Issue Type: Bug
  Components: security
Affects Versions: 0.7.0
 Environment: CentOS, in docker container.
Reporter: Luis Guzman
Priority: Minor


Hi!

We've noticed that when you activate:
{quote}

  zeppelin.notebook.s3.user
  username
  user name for s3 folder structure

{quote}
Plus, user authorization provided by shiro, we cannot find a way to save the 
notebooks in a "per user basis"

That's it, we would expect to be able to do:
{quote}

  zeppelin.notebook.s3.user
  zeppelin/{username}
  user name for s3 folder structure

{quote}

And whenever a user is logged in, notebooks are stored in a different 
"directory" inside S3.
s3://mybucket/zeppelin/user1/notebook/...
s3://mybucket/zeppelin/user2/notebook/...
s3://mybucket/zeppelin/user3/notebook/...
...

Is there a way for this, if not, it is right to qualify this as a 
bug/improvement needed? Or I am making here some really bad mistake?

Thanks!

Luis



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
Tested and LGTM


---
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 #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
@FRosner If auto-save works properly, 

- User B's local change will update server state
- And User A's paragraph text will be updated because he/she doesn't have 
local change
- If they have local change, their paragraph will ignore newly propagated 
text and will overwrite User b's text later.



---
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 #2177: [ZEPPELIN-2301] DON'T overwrite editor text when note ...

[FRosner]

Github user FRosner commented on the issue:

https://github.com/apache/zeppelin/pull/2177
  
Thanks @1ambda. I'm quite busy at this moment so if someone else (e.g. 
@AhyoungRyu) can also take a look that would be greatly appreciated.


---
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 #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

[FRosner]

Github user FRosner commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
Sorry I was traveling @1ambda :(

I understand what you are saying but I still don't understand exactly how 
it will work after this PR. Consider the following situation:

- User A and B edit a paragraph at the same time
- User A executes the paragraph
- User B will not get his changes overwritten (due to this PR, correct?)
- ...

Then how does User B ever get back in sync with the server state? How will 
the conflict be resolved? Will User A then lose his modifications?


---
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-2333) Spark interpreter mixes code results with interpreter logs

[Igor Drozdov (JIRA)]

Igor Drozdov created ZEPPELIN-2333:
--

 Summary: Spark interpreter mixes code results with interpreter logs
 Key: ZEPPELIN-2333
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2333
 Project: Zeppelin
  Issue Type: Bug
Reporter: Igor Drozdov
Assignee: Igor Drozdov


For example

{code}
%spark
println("%table")
val a = 1
println("1")
val b = 2
println("2")
val c = 3
println("3")
{code}

results to 

||a: Int = 1||
|1|
|b: Int = 2|
|2|
|c: Int = 3|
|3|
(some rows are interpreter logs)

I expect to see two messages in result: table with 1, 2, 3 and text with 
interpreter details



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin pull request #2206: [ZEPPELIN-1856] Flaky Test: InterpreterRestApiT...

[AlexanderShoshin]

GitHub user AlexanderShoshin opened a pull request:

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

[ZEPPELIN-1856] Flaky Test: 
InterpreterRestApiTest.testRestartInterpreterPerNote

### What is this PR for?
A _NullPointerException_ occurs occasionally in 
`InterpreterRestApiTest.testRestartInterpreterPerNote()` test when 
`p.getResult()` returns _null_ in the following line of test method:
```
assertEquals(p.getResult().message().get(0).getData(), 
getSimulatedMarkdownResult("markdown"));
```
It happens when we recieve an _OUTPUT_UPDATE_ALL_ event in 
_RemoteInterpreterEventPoller_ after `RemoteInterpreter.interpret(..)` is done. 
The `Paragraph.result` which already contains its final value is setted to 
_null_ by `NotebookServer.onOutputClear(..)` method. As a result we recieve a 
_NPE_ in assertion.

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

### Todos
* [ ] - To fix this issue we need to ignore an _OUTPUT_UPDATE_ALL_ event 
after job is finished.

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

### 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/AlexanderShoshin/zeppelin ZEPPELIN-1856

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

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


commit bcf01bd999fc853e08058a77443153338f85c5d4
Author: Alexander Shoshin 
Date:   2017-03-24T13:27:35Z

do not clear a paragraph output if the paragraph is already done




---
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 #2205: [ZEPPELIN-2330] Helium.html doesn't render spell infor...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2205
  
LGTM


---
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-2332) HeliumApplicationFactoryTest in Zeppelin Zengine hangs

[Pravin Dsilva (JIRA)]

Pravin Dsilva created ZEPPELIN-2332:
---

 Summary: HeliumApplicationFactoryTest in Zeppelin Zengine hangs 
 Key: ZEPPELIN-2332
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2332
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-zengine
Affects Versions: 0.8.0
 Environment: Ubuntu 14.04.5 
x86, ppc64le
Reporter: Pravin Dsilva


On the Master branch of Zeppelin, HeliumApplicationFactoryTest test gets hanged 
indefinitely at the following point:
{code}
09:51:34,664  INFO org.apache.zeppelin.interpreter.remote.RemoteInterpreter:552 
- Push local angular object registry from ZeppelinServer to remote interpreter 
group 2CESSVJH8:shared_process
09:51:34,770 ERROR 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterEventPoller:263 - Can't 
handle event RemoteInterpreterEvent(type:OUTPUT_UPDATE_ALL, 
data:{"messages":[],"noteId":"2CDNWC2XB","paragraphId":"20170330-095133_41605"})
java.lang.NullPointerException
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterEventPoller.run(RemoteInterpreterEventPoller.java:194)
09:51:34,924  INFO org.apache.zeppelin.interpreter.InterpreterGroup:185 - Close 
interpreter group 2CESSVJH8:shared_process for session: shared_session
09:51:34,968  INFO 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:123 - shutdown 
interpreter process
09:51:35,927 ERROR org.apache.zeppelin.interpreter.remote.AppendOutputRunner:68 
- Wait for OutputBuffer queue interrupted: null
09:51:37,449  INFO 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:133 - Exception 
in RemoteInterpreterProcess while synchronized dereference, can safely ignore 
exception while client.shutdown() may terminates remote process
09:51:37,473  INFO 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:186 - 
Interpreter process exited 0
{code}

Commands used for building:
{code}
 mvn clean install -Pspark-1.6  -Ppyspark -Phadoop-2.7 -DskipTests
{code}

For running the tests:
{code}
mvn  test -Pspark-1.6  -Ppyspark -Phadoop-2.7
{code}

I have attached the complete console log. There isn't any surefire report 
generated for additional debug logs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #571: Remove author tag

[minahlee]

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/571
  
@dlukyanov The reason I removed the author is not `@author` tag itself but 
because of ownership of the code. All code contributed to this repository is 
owned by Zeppelin community not by specific author.

I found one [jira issue](https://issues.apache.org/jira/browse/TAVERNA-897) 
from Apache Taverna community which listed out discussion around it. Hope this 
help you to understand why we don't leave footprint in the code.


---
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-2331) Zeppelin hangs in air-gapped environments

[Raffaele Saggino (JIRA)]

Raffaele Saggino created ZEPPELIN-2331:
--

 Summary: Zeppelin hangs in air-gapped environments
 Key: ZEPPELIN-2331
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2331
 Project: Zeppelin
  Issue Type: Improvement
  Components: helium
Affects Versions: 0.7.0
 Environment: RHEL 7.2
Reporter: Raffaele Saggino


Starting Zeppelin in air-gapped environment requires up to 10 minutes because 
it fails to download nodejs and npm.

Downloading these files manually leads to the same result since 
HeliumBundleFactory tries to connect to "http://registry.npmjs.org/; without 
success.

I think we should check for internet availability and skip those steps.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #571: Remove author tag

[dlukyanov]

Github user dlukyanov commented on the issue:

https://github.com/apache/zeppelin/pull/571
  
@minahlee , could the class comment `created by` be used instead of @author 
tag in zeppelin sources?


---
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 #2205: [ZEPPELIN-2330] Helium.html doesn't render spel...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2330] Helium.html doesn't render spell information only in 
production build

### What is this PR for?

Helium.html doesn't render spell information only in production build.

That's because self-closed div doesn't work with `ng-bind-html` when it's 
minified. 


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

### Todos

NONE

### What is the Jira issue?

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

### How should this be tested?

1. Build `mvn clean package -DskipTests;`
2. Open `localhost:8080/#/helium.html`
3. Click the `Spell` tab

### Screenshots (if appropriate)

 Before


![2330](https://cloud.githubusercontent.com/assets/4968473/24493212/04338b30-1569-11e7-9b20-63eab389c9a5.gif)

 After

https://cloud.githubusercontent.com/assets/4968473/24493204/fca731d2-1568-11e7-9550-b1e975dbdd55.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-2330/cannot-render-spell-info-in-prod

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

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






---
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 #2204: [WIP] ZEPPELIN-2189. The order of dynamic forms should...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2204
  
Change it to WIP for adding test. 


---
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-2330) Can't open spell config panel only in production mode

[Hoon Park (JIRA)]

Hoon Park created ZEPPELIN-2330:
---

 Summary: Can't open spell config panel only in production mode
 Key: ZEPPELIN-2330
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2330
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end, helium
Reporter: Hoon Park


Can't open spell config panel only in production mode



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2098
  
@1ambda Appreciate for such detailed explanation! 
Regarding `no-group`, I can assume the other ppl can be confused like me. 
So it'll be better to add some description for that to the documentation. (you 
already wrote all needed contents in your comments :D)

FYI I suggested to separate Helium related docs page from "Contribute" 
section in the dropdown menu and create new section "Helium Framework" in 
#2202(Helium is worth to have its own kk). So your new docs page "Writing 
Zeppelin Visualization: Transformation(or another name?)" can be put under this 
section.
And maybe more self-descriptive name would be better instead of just 
`Transformation`(hard to recognize at a glance what kind of transformation is). 
Something like `Writing Zeppelin Visualization: Advanced Chart Configuration`.. 
But I don't wanna hang this PR because of docs. Surely you can handle it in 
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 issue #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda Thanks! 
Will merge into master if there are no further discussions.


---
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 #2204: ZEPPELIN-2189. The order of dynamic forms should be th...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2204
  
Tested and it works well now. Thanks for fixing it. LGTM 


---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@AhyoungRyu Tested and works as described. LGTM!


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