[GitHub] zeppelin issue #1935: [gh-pages][ZEPPELIN-1973] List all available Helium pa...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1935
  
@1ambda Thanks for testing it out. Merge into `gh-pages` 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.0 (RC4)

[Hyung Sung Shim]

+1
Thanks mina for your effort.

2017-02-03 11:58 GMT+09:00 Renjith Kamath :

> +1
>
> On Fri, Feb 3, 2017 at 8:01 AM, Prabhjyot Singh  >
> wrote:
>
> > +1
> >
> > On Feb 2, 2017 8:25 PM, "Alexander Bezzubov"  wrote:
> >
> >> +1,
> >>
> >> and thank you for an awesome work Mina!
> >> Your persistence in making RCs and incorporating feedback is admirable.
> >>
> >> Verified:
> >>  - checksums, signatures + keys for sources and bin-all
> >>  - bin-all can run all Spark Zeppelin Tutorial in local mode
> >>  - sources do compile, but only without tests.
> >>Build \w tests fails on zeppelin-zengine for me
> >>
> >> 1) Failed tests:
> >>   NotebookTest.testSchedulePoolUsage:397 expected: but
> >> was:
> >>
> >> 2) frontend build on Linux also failed mysteriously executing yarn
> >> command, most probably due to local env configuration.
> >>
> >>
> >> --
> >> Alex
> >>
> >> On Thu, Feb 2, 2017 at 5:28 PM, Jeff Zhang  wrote:
> >>
> >>> +1
> >>>
> >>> Ahyoung Ryu 于2017年2月2日周四 下午9:36写道：
> >>>
> >>> +1
> >>>
> >>> On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:
> >>>
> >>> +1
> >>> 2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:
> >>>
> >>> +1
> >>>
> >>> On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov 
> >>> wrote:
> >>>
> >>> > +1
> >>> >
> >>> > On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan 
> >>> wrote:
> >>> >
> >>> > +1
> >>> >
> >>> > On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
> >>> >
> >>> > > I propose the following RC to be released for the Apache Zeppelin
> >>> 0.7.0
> >>> > > release.
> >>> > >
> >>> > > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
> >>> > > corresponds to the tag v0.7.0-rc4:
> >>> > > *
> >>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
> >>> rtlog;h=refs/tags/v0.7.0-rc4
> >>> > > <
> >>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
> >>> rtlog;h=refs/tags/v0.7.0-rc4
> >>>
> >>> > >*
> >>> > >
> >>> > > The release archives (tgz), signature, and checksums are here
> >>> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> 7.0-rc4/
> >>> > >
> >>> > > The release candidate consists of the following source distribution
> >>> > > archive
> >>> > > zeppelin-0.7.0.tgz
> >>> > >
> >>> > > In addition, the following supplementary binary distributions are
> >>> > provided
> >>> > > for user convenience at the same location
> >>> > > zeppelin-0.7.0-bin-all.tgz
> >>> > > zeppelin-0.7.0-bin-netinst.tgz
> >>> > >
> >>> > > The maven artifacts are here
> >>> > >
> >>> > https://repository.apache.org/content/repositories/orgapache
> >>> zeppelin-1027
> >>> > >
> >>> > > 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=12336544=12316221
> >>> > >
> >>> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
> >>> > >
> >>> > > [ ] +1 approve
> >>> > > [ ] 0 no opinion
> >>> > > [ ] -1 disapprove (and reason why)
> >>> > >
> >>> >
> >>> >
> >>> >
> >>>
> >>> --
> >>> Taejun Kim
> >>>
> >>> Data Mining Lab.
> >>> School of Electrical and Computer Engineering
> >>> University of Seoul
> >>>
> >>>
> >>>
> >>
>

Re: [VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[Renjith Kamath]

+1

On Fri, Feb 3, 2017 at 8:01 AM, Prabhjyot Singh 
wrote:

> +1
>
> On Feb 2, 2017 8:25 PM, "Alexander Bezzubov"  wrote:
>
>> +1,
>>
>> and thank you for an awesome work Mina!
>> Your persistence in making RCs and incorporating feedback is admirable.
>>
>> Verified:
>>  - checksums, signatures + keys for sources and bin-all
>>  - bin-all can run all Spark Zeppelin Tutorial in local mode
>>  - sources do compile, but only without tests.
>>Build \w tests fails on zeppelin-zengine for me
>>
>> 1) Failed tests:
>>   NotebookTest.testSchedulePoolUsage:397 expected: but
>> was:
>>
>> 2) frontend build on Linux also failed mysteriously executing yarn
>> command, most probably due to local env configuration.
>>
>>
>> --
>> Alex
>>
>> On Thu, Feb 2, 2017 at 5:28 PM, Jeff Zhang  wrote:
>>
>>> +1
>>>
>>> Ahyoung Ryu 于2017年2月2日周四 下午9:36写道：
>>>
>>> +1
>>>
>>> On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:
>>>
>>> +1
>>> 2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:
>>>
>>> +1
>>>
>>> On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov 
>>> wrote:
>>>
>>> > +1
>>> >
>>> > On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan 
>>> wrote:
>>> >
>>> > +1
>>> >
>>> > On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
>>> >
>>> > > I propose the following RC to be released for the Apache Zeppelin
>>> 0.7.0
>>> > > release.
>>> > >
>>> > > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
>>> > > corresponds to the tag v0.7.0-rc4:
>>> > > *
>>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
>>> rtlog;h=refs/tags/v0.7.0-rc4
>>> > > <
>>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
>>> rtlog;h=refs/tags/v0.7.0-rc4
>>>
>>> > >*
>>> > >
>>> > > The release archives (tgz), signature, and checksums are here
>>> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
>>> > >
>>> > > The release candidate consists of the following source distribution
>>> > > archive
>>> > > zeppelin-0.7.0.tgz
>>> > >
>>> > > In addition, the following supplementary binary distributions are
>>> > provided
>>> > > for user convenience at the same location
>>> > > zeppelin-0.7.0-bin-all.tgz
>>> > > zeppelin-0.7.0-bin-netinst.tgz
>>> > >
>>> > > The maven artifacts are here
>>> > >
>>> > https://repository.apache.org/content/repositories/orgapache
>>> zeppelin-1027
>>> > >
>>> > > 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=12336544=12316221
>>> > >
>>> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
>>> > >
>>> > > [ ] +1 approve
>>> > > [ ] 0 no opinion
>>> > > [ ] -1 disapprove (and reason why)
>>> > >
>>> >
>>> >
>>> >
>>>
>>> --
>>> Taejun Kim
>>>
>>> Data Mining Lab.
>>> School of Electrical and Computer Engineering
>>> University of Seoul
>>>
>>>
>>>
>>

Re: [VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[Prabhjyot Singh]

+1

On Feb 2, 2017 8:25 PM, "Alexander Bezzubov"  wrote:

> +1,
>
> and thank you for an awesome work Mina!
> Your persistence in making RCs and incorporating feedback is admirable.
>
> Verified:
>  - checksums, signatures + keys for sources and bin-all
>  - bin-all can run all Spark Zeppelin Tutorial in local mode
>  - sources do compile, but only without tests.
>Build \w tests fails on zeppelin-zengine for me
>
> 1) Failed tests:
>   NotebookTest.testSchedulePoolUsage:397 expected: but
> was:
>
> 2) frontend build on Linux also failed mysteriously executing yarn
> command, most probably due to local env configuration.
>
>
> --
> Alex
>
> On Thu, Feb 2, 2017 at 5:28 PM, Jeff Zhang  wrote:
>
>> +1
>>
>> Ahyoung Ryu 于2017年2月2日周四 下午9:36写道：
>>
>> +1
>>
>> On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:
>>
>> +1
>> 2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:
>>
>> +1
>>
>> On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov 
>> wrote:
>>
>> > +1
>> >
>> > On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan 
>> wrote:
>> >
>> > +1
>> >
>> > On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
>> >
>> > > I propose the following RC to be released for the Apache Zeppelin
>> 0.7.0
>> > > release.
>> > >
>> > > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
>> > > corresponds to the tag v0.7.0-rc4:
>> > > *
>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
>> rtlog;h=refs/tags/v0.7.0-rc4
>> > > <
>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
>> rtlog;h=refs/tags/v0.7.0-rc4
>> > >*
>> > >
>> > > The release archives (tgz), signature, and checksums are here
>> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
>> > >
>> > > The release candidate consists of the following source distribution
>> > > archive
>> > > zeppelin-0.7.0.tgz
>> > >
>> > > In addition, the following supplementary binary distributions are
>> > provided
>> > > for user convenience at the same location
>> > > zeppelin-0.7.0-bin-all.tgz
>> > > zeppelin-0.7.0-bin-netinst.tgz
>> > >
>> > > The maven artifacts are here
>> > >
>> > https://repository.apache.org/content/repositories/orgapache
>> zeppelin-1027
>> > >
>> > > 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=12336544=12316221
>> > >
>> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
>> > >
>> > > [ ] +1 approve
>> > > [ ] 0 no opinion
>> > > [ ] -1 disapprove (and reason why)
>> > >
>> >
>> >
>> >
>>
>> --
>> Taejun Kim
>>
>> Data Mining Lab.
>> School of Electrical and Computer Engineering
>> University of Seoul
>>
>>
>>
>

[jira] [Created] (ZEPPELIN-2046) The final output is a little inconsistent with the streaming output

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2046:


 Summary: The final output is a little inconsistent with the 
streaming output
 Key: ZEPPELIN-2046
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2046
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Priority: Minor
 Fix For: 0.7.1


As the attachment screenshot shows, the final output is not consistent with the 
streaming output. The final output has one extra blank lines between outputs. I 
believe the previous behavior is not like this. 



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

[GitHub] zeppelin issue #1970: ZEPPELIN-2045. Pass interpreter properties with "spark...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1970
  
@Leemoonsoo @felixcheung Please help review. 


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

[GitHub] zeppelin issue #1962: [ZEPPELIN-2014] Jetty Directory Listing on app, assets...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1962
  
@vboginskii Thanks for the contribution. LGTM and merge to master if no 
further 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.
---

[GitHub] zeppelin pull request #1970: ZEPPELIN-2045. Pass interpreter properties with...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-2045. Pass interpreter properties with "spark." as prefix to 
SparkConf

### What is this PR for?
Minor change to only pass interpreter properties with "spark." as prefix to 
SparkConf. Other properties is used by zeppelin interpreter process, so don't 
need to be passed to SparkConf.


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

### Todos
* [ ] - Task

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

### How should this be tested?
Tested manually, this is the log after this PR
```
 INFO [2017-02-03 09:05:33,664] ({pool-2-thread-2} 
SparkInterpreter.java[createSparkContext_1]:384) - -- Create new 
SparkContext yarn-client ---
DEBUG [2017-02-03 09:05:33,668] ({pool-2-thread-2} 
SparkInterpreter.java[createSparkContext_1]:467) - SparkConf: key = 
[spark.cores.max], value = [2]
DEBUG [2017-02-03 09:05:33,668] ({pool-2-thread-2} 
SparkInterpreter.java[createSparkContext_1]:467) - SparkConf: key = 
[spark.app.name], value = [Zeppelin]
```

### Screenshots (if appropriate)

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


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

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

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

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


commit 3a146d3e0022f70576f34634910f3bd39c911ac3
Author: Jeff Zhang 
Date:   2017-02-03T01:01:09Z

ZEPPELIN-2045. Pass interpreter properties with "spark." as prefix to 
SparkConf




---
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-2045) Pass interpreter properties with "spark." as prefix to SparkConf

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2045:


 Summary: Pass interpreter properties with "spark." as prefix to 
SparkConf
 Key: ZEPPELIN-2045
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2045
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
 Fix For: 0.7.1






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

[GitHub] zeppelin pull request #1969: [ZEPPELIN-1465] Add an option to allow S3 serve...

[jeff-cyft]

GitHub user jeff-cyft opened a pull request:

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

[ZEPPELIN-1465] Add an option to allow S3 server-side encryption

### What is this PR for?
Provide a configuration option that will cause the S3 Notebook repo to 
request server-side encryption of saved notebooks.

### What type of PR is it?
Improvement

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

### How should this be tested?
Enable the configuration option, save a notebook in zeppelin, and confirm 
in the AWS S3 Console that the related file was saved with AES-256 encryption 
on the server-side.  (Properties tab, Detail section)

### Questions:
* Does the licenses files need update?
No

* Is there breaking changes for older versions?
No.

* Does this needs documentation?
I added mentions of the new option in existing documentation.

Thank you!

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

$ git pull https://github.com/jeff-cyft/zeppelin s3_sse

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

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


commit 3c657ac64bc2d2b264d27a747a47020b0a42a527
Author: Jeff Plourde 
Date:   2017-02-02T16:03:49Z

Configuration option to request S3 SSE when notebooks are saved.

commit 26f5264a0694249f6b5880e5de5a476d3cb9beaf
Author: Jeff Plourde 
Date:   2017-02-02T16:09:57Z

code style - remove tab




---
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-2044) Table display does not render all rows, when height is large

[Andreas Koch (JIRA)]

Andreas Koch created ZEPPELIN-2044:
--

 Summary: Table display does not render all rows, when height is 
large
 Key: ZEPPELIN-2044
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2044
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Affects Versions: 0.7.0
Reporter: Andreas Koch
Priority: Minor


When displaying a table with embedded html, not all rows are being rendered if 
the row heights are large.

For examle:
{code:title=Table with html|borderStyle=solid}
println(s"""%table Image\tNumber
%html \t100
%html \t100
%html \t100
""")
{code}

This example will only render the first row. But all rows are rendered if the 
size of the last row is changed:
{code:title=Table with html|borderStyle=solid}
println(s"""%table Image\tNumber
%html \t100
%html \t100
%html \t100
""")
{code}





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

Re: [VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[Alexander Bezzubov]

+1,

and thank you for an awesome work Mina!
Your persistence in making RCs and incorporating feedback is admirable.

Verified:
 - checksums, signatures + keys for sources and bin-all
 - bin-all can run all Spark Zeppelin Tutorial in local mode
 - sources do compile, but only without tests.
   Build \w tests fails on zeppelin-zengine for me

1) Failed tests:
  NotebookTest.testSchedulePoolUsage:397 expected: but
was:

2) frontend build on Linux also failed mysteriously executing yarn command,
most probably due to local env configuration.


--
Alex

On Thu, Feb 2, 2017 at 5:28 PM, Jeff Zhang  wrote:

> +1
>
> Ahyoung Ryu 于2017年2月2日周四 下午9:36写道：
>
> +1
>
> On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:
>
> +1
> 2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:
>
> +1
>
> On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov  wrote:
>
> > +1
> >
> > On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan 
> wrote:
> >
> > +1
> >
> > On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
> >
> > > I propose the following RC to be released for the Apache Zeppelin 0.7.0
> > > release.
> > >
> > > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
> > > corresponds to the tag v0.7.0-rc4:
> > > *
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
> rtlog;h=refs/tags/v0.7.0-rc4
> > > <
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=sho
> rtlog;h=refs/tags/v0.7.0-rc4
> > >*
> > >
> > > The release archives (tgz), signature, and checksums are here
> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
> > >
> > > The release candidate consists of the following source distribution
> > > archive
> > > zeppelin-0.7.0.tgz
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location
> > > zeppelin-0.7.0-bin-all.tgz
> > > zeppelin-0.7.0-bin-netinst.tgz
> > >
> > > The maven artifacts are here
> > >
> > https://repository.apache.org/content/repositories/orgapache
> zeppelin-1027
> > >
> > > 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=12336544=12316221
> > >
> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> >
> >
> >
>
> --
> Taejun Kim
>
> Data Mining Lab.
> School of Electrical and Computer Engineering
> University of Seoul
>
>
>

[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...

[DrIgor]

GitHub user DrIgor reopened a pull request:

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

[ZEPPELIN-921] Apply new mechanism to KnitR and RRepl

### What is this PR for?
Applies new registration mechanism for R interpreter

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

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

### How should this be tested?
Build zeppelin with R profile enabled and run several R snippets

### 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/DrIgor/zeppelin ZEPPELIN-921

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

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


commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829
Author: Igor Drozdov 
Date:   2017-01-25T08:36:53Z

New registration mechanism for R 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.
---

[GitHub] zeppelin pull request #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...

[DrIgor]

Github user DrIgor closed the pull request at:

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


---
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.0 (RC4)

[Jeff Zhang]

+1

Ahyoung Ryu 于2017年2月2日周四 下午9:36写道：

+1

On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:

+1
2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:

+1

On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov  wrote:

> +1
>
> On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan  wrote:
>
> +1
>
> On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
>
> > I propose the following RC to be released for the Apache Zeppelin 0.7.0
> > release.
> >
> > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
> > corresponds to the tag v0.7.0-rc4:
> > *
>
https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
> > <
>
https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
> >*
> >
> > The release archives (tgz), signature, and checksums are here
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
> >
> > The release candidate consists of the following source distribution
> > archive
> > zeppelin-0.7.0.tgz
> >
> > In addition, the following supplementary binary distributions are
> provided
> > for user convenience at the same location
> > zeppelin-0.7.0-bin-all.tgz
> > zeppelin-0.7.0-bin-netinst.tgz
> >
> > The maven artifacts are here
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1027
> >
> > 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=12336544=12316221
> >
> > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
> >
> > [ ] +1 approve
> > [ ] 0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
>
>
>

-- 
Taejun Kim

Data Mining Lab.
School of Electrical and Computer Engineering
University of Seoul

[GitHub] zeppelin issue #1892: [MINOR] broken logo url in web dev mode

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1892
  
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 #1935: [gh-pages][ZEPPELIN-1973] List all available Helium pa...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1935
  
Tested and works 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.
---

Re: [VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[Ahyoung Ryu]

+1

On Thu, Feb 2, 2017 at 10:07 PM, Jun Kim  wrote:

> +1
> 2017년 2월 2일 (목) 오후 9:49, Sora Lee 님이 작성:
>
>> +1
>>
>> On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov 
>> wrote:
>>
>> > +1
>> >
>> > On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan 
>> wrote:
>> >
>> > +1
>> >
>> > On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
>> >
>> > > I propose the following RC to be released for the Apache Zeppelin
>> 0.7.0
>> > > release.
>> > >
>> > > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
>> > > corresponds to the tag v0.7.0-rc4:
>> > > *
>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=
>> shortlog;h=refs/tags/v0.7.0-rc4
>> > > <
>> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=
>> shortlog;h=refs/tags/v0.7.0-rc4
>> > >*
>> > >
>> > > The release archives (tgz), signature, and checksums are here
>> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
>> > >
>> > > The release candidate consists of the following source distribution
>> > > archive
>> > > zeppelin-0.7.0.tgz
>> > >
>> > > In addition, the following supplementary binary distributions are
>> > provided
>> > > for user convenience at the same location
>> > > zeppelin-0.7.0-bin-all.tgz
>> > > zeppelin-0.7.0-bin-netinst.tgz
>> > >
>> > > The maven artifacts are here
>> > >
>> > https://repository.apache.org/content/repositories/
>> orgapachezeppelin-1027
>> > >
>> > > 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=12336544=12316221
>> > >
>> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
>> > >
>> > > [ ] +1 approve
>> > > [ ] 0 no opinion
>> > > [ ] -1 disapprove (and reason why)
>> > >
>> >
>> >
>> >
>>
> --
> Taejun Kim
>
> Data Mining Lab.
> School of Electrical and Computer Engineering
> University of Seoul
>

[GitHub] zeppelin issue #1935: [gh-pages][ZEPPELIN-1973] List all available Helium pa...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1935
  
Thanks for GREAT suggestions @1ambda. 

>It would be great if helium package has version field considering local 
package and latest

I've just added `version` and `published` field to each pkg version's 
information. Please check 
[helium.json](https://s3.amazonaws.com/helium-package/helium.json)(used for 
Zeppelin Helium GUI menu) and 
[helium.js](https://s3.amazonaws.com/helium-package/helium.js)(used for 
zeppelin.apache.org). I also added `published` date for each version, to show 
latest package first. So now, it'll be look like below 
```
"0.0.3": {
  ...
},
"latest": {
  "type": "VISUALIZATION",
  "name": "zeppelin-bubblechart",
  "version": "0.0.4",
  "published": "2017-01-23T20:42:34.373Z",
  "artifact": "zeppelin-bubblechart@0.0.4",
  "author": "leemoonsoo",
  "description": "Animated bubble chart",
  "license": "BSD-2-Clause",
  "icon": ""
}
```

And here is the latest update.

![record](https://cloud.githubusercontent.com/assets/10060731/22551286/90bc376c-e997-11e6-8529-4dde534181d4.gif)


>If once people start to develop packages, there must be operational things 
like user complains. For example, "I published package to npm, but it's not 
collected by helium for last 2 days. What's the problem?" So, it's good for 
each package to have some information for debug and ops like createdAt, 
heliumFormatVersion.

Especially for this, totally agree with you. Actually there are lots of 
things to be improved and can be changed. So I need more time to rethink about 
how I can do that in Lambda function side. But as it doesn't affect directly to 
merge this PR, I'll update it later time if it's okay with you. Appreciate 
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 pull request #1968: [ZEPPELIN-1551] Remove the "default" text again...

[namanmishra91]

GitHub user namanmishra91 opened a pull request:

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

[ZEPPELIN-1551] Remove the "default" text against interpreters on 
interpreters screen as it is providing incorrect semantics


### What is this PR for?
This PR addresses the incorrect semantics and confusion caused by the 
"default" text against an interpreter group on interpreters page. 
The intent of of this tag seems to be informing the user which of the 
interpreters among a particular group will be used by default if the user 
doesn't specify any % tag. However, the "default" tag is always 
tied to the first interpreter of the first interpreter group on the page and 
isn't displayed for any other interpreter groups; therefore not serving any 
purpose. It also leads to confusion with the default interpreter bound to a 
notebook on bindings page.

It would be better to remove this default tag from interpreters in order to 
avoid the confusion.


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

### Todos

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

### How should this be tested?
Run Zeppelin server. Open Interpreters menu. "default" shouldn't be visible 
against any interpreter group.

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

### Screenshots (if appropriate)

![zeppelin-1551](https://cloud.githubusercontent.com/assets/6438072/22550188/f0efe0d4-e974-11e6-82a4-722b9662e5db.png)


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

$ git pull https://github.com/namanmishra91/zeppelin ZEPPELIN-1551

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

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


commit f9ded1d27b314aec618158710c86b1e172206e26
Author: Naman Mishra 
Date:   2017-02-02T10:58:50Z

Remove the "default" text against interpreters on interpreter settings 
screen as it is providing incorrect semantics.

"Default" is always tied to the first interpreter of the first interpreter 
group on the page; therefore not serving any purpose. It also leads to 
confusion with the default bound interpreter on bindings page.




---
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.0 (RC4)

[Sora Lee]

+1

On Thu, Feb 2, 2017 at 9:40 PM Khalid Huseynov  wrote:

> +1
>
> On Thu, Feb 2, 2017 at 9:21 PM, DuyHai Doan  wrote:
>
> +1
>
> On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:
>
> > I propose the following RC to be released for the Apache Zeppelin 0.7.0
> > release.
> >
> > The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
> > corresponds to the tag v0.7.0-rc4:
> > *
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
> > <
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
> >*
> >
> > The release archives (tgz), signature, and checksums are here
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
> >
> > The release candidate consists of the following source distribution
> > archive
> > zeppelin-0.7.0.tgz
> >
> > In addition, the following supplementary binary distributions are
> provided
> > for user convenience at the same location
> > zeppelin-0.7.0-bin-all.tgz
> > zeppelin-0.7.0-bin-netinst.tgz
> >
> > The maven artifacts are here
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1027
> >
> > 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=12336544=12316221
> >
> > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
> >
> > [ ] +1 approve
> > [ ] 0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
>
>
>

Re: [VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[DuyHai Doan]

+1

On Thu, Feb 2, 2017 at 9:56 AM, Mina Lee  wrote:

> I propose the following RC to be released for the Apache Zeppelin 0.7.0
> release.
>
> The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
> corresponds to the tag v0.7.0-rc4:
> *https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
> *
>
> The release archives (tgz), signature, and checksums are here
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
>
> The release candidate consists of the following source distribution
> archive
> zeppelin-0.7.0.tgz
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location
> zeppelin-0.7.0-bin-all.tgz
> zeppelin-0.7.0-bin-netinst.tgz
>
> The maven artifacts are here
> https://repository.apache.org/content/repositories/orgapachezeppelin-1027
>
> 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=12336544=12316221
>
> Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>

[GitHub] zeppelin issue #1962: [ZEPPELIN-2014] Jetty Directory Listing on app, assets...

[vboginskii]

Github user vboginskii commented on the issue:

https://github.com/apache/zeppelin/pull/1962
  
Build failed because some tests failed:

Tests in error: 

InterpreterRestApiTest.testRestartInterpreterPerNote:303 NullPointer
For this test already exist task: 
https://issues.apache.org/jira/browse/ZEPPELIN-1856  


ParagraphActionsIT.testClearOutputButton:274->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94
 » Timeout
Task for this test: https://issues.apache.org/jira/browse/ZEPPELIN-1073 


ZeppelinIT.testSparkInterpreterDependencyLoading:234->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94
 » Timeout
And for this test: https://issues.apache.org/jira/browse/ZEPPELIN-1797

During last build all tests passed, but build failed because "The job 
exceeded the maximum time limit for jobs, and has been terminated."


---
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-2043) getting this error while installing zeppelin-0.6.2-bin-all.tgz Zeppelin start [ OK ] Zeppelin process died [FAILED]

[Olumide Oyalola (JIRA)]

Olumide Oyalola created ZEPPELIN-2043:
-

 Summary: getting this error while installing 
zeppelin-0.6.2-bin-all.tgz  Zeppelin start [ OK ] Zeppelin process died [FAILED]
 Key: ZEPPELIN-2043
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2043
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-server
Affects Versions: 0.6.2
 Environment: Ubuntu 15.10
Reporter: Olumide Oyalola
 Fix For: 0.6.2


I have Java, Spark installed. However, when I start the zeppelin deamon, I get

- Zeppelin start [ OK ]
- Zeppelin process died [FAILED]




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

[GitHub] zeppelin issue #1892: [MINOR] broken logo url in web dev mode

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/1892
  
@1ambda I updated to extract `require('express')` module as variable and CI 
is green :)


---
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 #1886: [ZEPPELIN-1876] improved comptetion with schema/table/...

[sotnich]

Github user sotnich commented on the issue:

https://github.com/apache/zeppelin/pull/1886
  
@cloverhearts @astroshim 
Made a little change - now mysql also works as well as postgresql. I have 
tested 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.
---

[VOTE] Release Apache Zeppelin 0.7.0 (RC4)

[Mina Lee]

I propose the following RC to be released for the Apache Zeppelin 0.7.0
release.

The commit id is df007f2284a09caa7c8b35f8b59d5f1993fe8b64 which is
corresponds to the tag v0.7.0-rc4:
*https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.7.0-rc4
*

The release archives (tgz), signature, and checksums are here
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/

The release candidate consists of the following source distribution archive
zeppelin-0.7.0.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location
zeppelin-0.7.0-bin-all.tgz
zeppelin-0.7.0-bin-netinst.tgz

The maven artifacts are here
https://repository.apache.org/content/repositories/orgapachezeppelin-1027

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=12336544=12316221

Vote will be open for next 72 hours (close at 01:00 5/Feb PST).

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)

Re: Beginner issue

[moon soo Lee]

Done!

Thanks for contribution!

Regards,
moon

On Thu, Feb 2, 2017 at 5:31 PM Viktor Boginskii 
wrote:

> Hello,
>
> I would like to start contribute to Zeppelin.
>
> Could anyone assign issue
> https://issues.apache.org/jira/browse/ZEPPELIN-2014 to me (vboginskii) in
> jira?
>
> Viktor Boginskii
> Senior Software Engineer
>
> Office: +380 44 390 5457 <+380%2044%20390%205457>
> x 66644   Cell: +380 67 144 6117 
> <+380%2067%20144%206117>
>  Email: viktor_bogins...@epam.com
> Kyiv, Ukraine (GMT+2)   epam.com
>
> CONFIDENTIALITY CAUTION AND DISCLAIMER
> This message is intended only for the use of the individual(s) or
> entity(ies) to which it is addressed and contains information that is
> legally privileged and confidential. If you are not the intended recipient,
> or the person responsible for delivering the message to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. All unintended
> recipients are obliged to delete this message and destroy any printed
> copies.
>
>

Beginner issue

[Viktor Boginskii]

Hello,

I would like to start contribute to Zeppelin.

Could anyone assign issue https://issues.apache.org/jira/browse/ZEPPELIN-2014 
to me (vboginskii) in jira?

Viktor Boginskii
Senior Software Engineer

Office: +380 44 390 5457 x 66644   Cell: 
+380 67 144 6117   Email: 
viktor_bogins...@epam.com
Kyiv, Ukraine (GMT+2)   epam.com

CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or entity(ies) 
to which it is addressed and contains information that is legally privileged 
and confidential. If you are not the intended recipient, or the person 
responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. All unintended recipients are obliged to 
delete this message and destroy any printed copies.