[GitHub] zeppelin issue #1995: [ZEPPELIN-2086] Move zeppelin-web related test files i...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1995
  
@1ambda Sorry for my late response. Tested and could see what you 
described. Looks good 👍 


---
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 #2025: ZEPPELIN-2108. Livy interpreter job cancellation throw...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2025
  
@felixcheung @prabhjyotsingh 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 pull request #2028: [MINOR] Supported old note format in case of no...

[jongyoul]

GitHub user jongyoul opened a pull request:

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

[MINOR] Supported old note format in case of not having name of note

### What is this PR for?
Supporting old format of note which doesn't have name inside. Long time 
ago, when creating note without specific name, name field become empty string. 
but it become error while remove note for current master. It will fix this error


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

### Todos
* [ ] - Enable getName returns getId if it has empty value

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

### How should this be tested?
See the test added

### Screenshots (if appropriate)
N/A

### 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/jongyoul/zeppelin 
hotfix/remove-note-without-name

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

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


commit 821e4bf3c20521e4d18026670232229cf2098efe
Author: Jongyoul Lee 
Date:   2017-02-17T04:52:16Z

Supported old note format in case of not having name of note




---
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 #2021: [ZEPPELIN-2116]. livy interpreter needs to restart aft...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2021
  
Ran this couple of time on my local, works a expected.


---
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-2126) How to create zeppelin notebook like kibana,Hue dashboard with more effective widgets

[Narasimma varman (JIRA)]

Narasimma varman created ZEPPELIN-2126:
--

 Summary: How to create zeppelin notebook like kibana,Hue dashboard 
with more effective widgets
 Key: ZEPPELIN-2126
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2126
 Project: Zeppelin
  Issue Type: Bug
  Components: helium, Homepage, zeppelin-interpreter
Affects Versions: 0.6.1
 Environment: zeppelin
Reporter: Narasimma varman
 Fix For: 0.6.1


I'm using HDP 2.5. As I'm new to zeppelin notebook. I have seen hue, kibana 
dashboard, they deliver more dynamic data changes in every widget like pie, 
table, map, bar chart. My question is how I implement those features in 
zeppelin notebook. For example, if click bar chart at one portion it will 
affect entire notebook.Please tell me how to use zeppelin notebook more 
effective like hue and kibana dashboards.





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

[GitHub] zeppelin issue #1995: [ZEPPELIN-2086] Move zeppelin-web related test files i...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1995
  
Thanks @AhyoungRyu. This definitely help to write and check test easily.


---
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 #2021: [ZEPPELIN-2116]. livy interpreter needs to restart aft...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2021
  
LGTM
Waiting for CI and 
merging if no more comment


---
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-2127) socket error and ({Thread-25932} JobProgressPoller.java[run]:54) - Can not get or update progress

[JIRA]

吴志龙 created ZEPPELIN-2127:
-

 Summary: socket error and ({Thread-25932} 
JobProgressPoller.java[run]:54) - Can not get or update progress
 Key: ZEPPELIN-2127
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2127
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.7.0
 Environment: jdk 1.7
linux 8G zeppelin-server

Reporter: 吴志龙
 Fix For: 0.7.0



 INFO [2017-02-16 17:29:00,276] ({qtp1428414238-26876} 
NotebookServer.java[onOpen]:127) - New connection from 192.168.32.40 : 1855
 INFO [2017-02-16 17:29:00,356] ({qtp1428414238-26878} 
NotebookServer.java[sendNote]:559) - New operation from 192.168.32.40 : 1855 : 
coriatian : GET_NOTE : 2CBEY67VW
 INFO [2017-02-16 17:29:00,359] ({qtp1428414238-26878} 
NotebookServer.java[sendNote]:559) - New operation from 192.168.32.40 : 1855 : 
coriatian : GET_NOTE : 2CBEY67VW
 INFO [2017-02-16 17:29:05,679] ({pool-2-thread-61} Job.java[run]:180) - 
end jobRun Paragraph--
 INFO [2017-02-16 17:29:05,679] ({pool-2-thread-61} 
NotebookServer.java[afterStatusChange]:1500) - Job 20170216-161237_625814895 is 
finished
 INFO [2017-02-16 17:29:05,932] ({pool-2-thread-61} 
SchedulerFactory.java[jobFinished]:137) - Job 
paragraph_1487232757101_-941163964 finished by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1298915037
 INFO [2017-02-16 17:29:11,327] ({pool-2-thread-54} 
SchedulerFactory.java[jobStarted]:131) - Job paragraph_1487237223597_-425146538 
started by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1298915037
 INFO [2017-02-16 17:29:11,328] ({pool-2-thread-54} Job.java[run]:176) - 
start jobRun Paragraph--
 INFO [2017-02-16 17:29:11,328] ({pool-2-thread-54} Paragraph.java[jobRun]:338) 
- run paragraph 20170216-172703_35717830 using fkhive5 
org.apache.zeppelin.interpreter.LazyOpenInterpreter@7511f5d6
 INFO [2017-02-16 17:29:11,813] ({pool-2-thread-54} Job.java[run]:180) - 
end jobRun Paragraph--
 INFO [2017-02-16 17:29:11,813] ({pool-2-thread-54} 
NotebookServer.java[afterStatusChange]:1500) - Job 20170216-172703_35717830 is 
finished
 INFO [2017-02-16 17:29:11,905] ({pool-2-thread-54} 
SchedulerFactory.java[jobFinished]:137) - Job 
paragraph_1487237223597_-425146538 finished by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1298915037
 INFO [2017-02-16 17:29:18,480] ({pool-2-thread-36} Job.java[run]:180) - 
end jobRun Paragraph--
 INFO [2017-02-16 17:29:18,481] ({pool-2-thread-36} 
NotebookServer.java[afterStatusChange]:1500) - Job 20170216-155748_806534558 is 
finished
 INFO [2017-02-16 17:29:18,559] ({pool-2-thread-36} 
SchedulerFactory.java[jobFinished]:137) - Job 
paragraph_1487231868519_1985536076 finished by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1298915037
 INFO [2017-02-16 17:29:27,745] ({pool-2-thread-37} 
SchedulerFactory.java[jobStarted]:131) - Job paragraph_1487237351233_1749808870 
started by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session371072798
 INFO [2017-02-16 17:29:27,746] ({pool-2-thread-37} Paragraph.java[jobRun]:338) 
- run paragraph 20170216-172911_1707515274 using fkhive6 
org.apache.zeppelin.interpreter.LazyOpenInterpreter@6f5dc488
 INFO [2017-02-16 17:29:28,024] ({pool-2-thread-37} 
NotebookServer.java[afterStatusChange]:1500) - Job 20170216-172911_1707515274 
is finished
 INFO [2017-02-16 17:29:28,111] ({pool-2-thread-37} 
SchedulerFactory.java[jobFinished]:137) - Job 
paragraph_1487237351233_1749808870 finished by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session371072798
 INFO [2017-02-16 17:29:30,633] ({pool-2-thread-91} 
SchedulerFactory.java[jobStarted]:131) - Job paragraph_1487237223597_-425146538 
started by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1178960300
 INFO [2017-02-16 17:29:30,633] ({pool-2-thread-91} Paragraph.java[jobRun]:338) 
- run paragraph 20170216-172703_35717830 using fkhive4 
org.apache.zeppelin.interpreter.LazyOpenInterpreter@6e22f0a5
ERROR [2017-02-16 17:29:36,315] ({qtp1428414238-26784} 
NotebookServer.java[onMessage]:277) - Can't handle message
java.lang.NullPointerException
at 
org.apache.zeppelin.socket.NotebookServer.cancelParagraph(NotebookServer.java:1146)
at 
org.apache.zeppelin.socket.NotebookServer.onMessage(NotebookServer.java:215)
at 
org.apache.zeppelin.socket.NotebookSocket.onWebSocketText(NotebookSocket.java:57)
at 
org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
at 
org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
at 
org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage

Re: [DISCUSS] Scaling out CI capability

[Jongyoul Lee]

I think it's good idea. :-)

On Thu, Feb 16, 2017 at 7:54 PM, Jeff Zhang  wrote:

> Great, can't wait to try this.
>
>
>
> moon soo Lee 于2017年2月16日周四 下午6:35写道：
>
> > Hi Apache Zeppelin contributors!
> >
> > Recently, it's not very difficult to see pullrequest is waiting more than
> > 10 hours to get travis-ci build slot.
> >
> > It's because of all ASF project shares the same travis account and the
> > account's capability is limited. Although ASF assigned 5 concurrent build
> > capacity to Zeppelin, it's not dedicated slot, it's more like max
> > concurrent build limit, so when ASF travis is busy, Zeppelin pullrequest
> > should wait.
> >
> > But each contributor can get 5 concurrent build capacity for opensource
> > project. if we can leverage that, Zeppelin will no longer suffer from CI
> > build capacity.
> >
> > I created https://issues.apache.org/jira/browse/ZEPPELIN-2123 and it
> > includes proposed way, how Zeppelin can leverage individual contributors
> > travis account.
> > And created required script https://github.com/apache/zeppelin/pull/2026
> .
> >
> > Please take a look the proposal. Any feedback would be really
> appreciated!
> >
> > Thanks,
> > moon
> >
>



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

[GitHub] zeppelin issue #2026: [ZEPPELIN-2123] Travis build status check script

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2026
  
Looks 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 #2024: [ZEPPELIN-411] JDK8 support

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
In case that you encounter conflicts, you have to rebase your changes onto 
the base branch you start working on. AFAIK, ASF doesn't allow write permission 
through Github.


---
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 #2002: [ZEPPELIN-1928]: Get a rid of preinstalled external de...

[DmytroShkvyra]

Github user DmytroShkvyra commented on the issue:

https://github.com/apache/zeppelin/pull/2002
  
Incompatible with https://github.com/apache/zeppelin/pull/2016


---
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 #2002: [ZEPPELIN-1928]: Get a rid of preinstalled exte...

[DmytroShkvyra]

Github user DmytroShkvyra closed the pull request at:

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


---
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 #2024: [ZEPPELIN-411] JDK8 support

[DmytroShkvyra]

Github user DmytroShkvyra closed the pull request at:

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


---
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 #2024: [ZEPPELIN-411] JDK8 support

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
I'm not sure who think what now, I just let you know the history. If you 
really want to move JDK8, open discussion and reach a "consensus" with 
community first. I think moving to JDK8 doesn't have any technical hurdle but 
needs to do it with Apache way.


---
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-2123) Scale-out CI capacity by leveraging individual contributor's travis account

[Lee moon soo (JIRA)]

Lee moon soo created ZEPPELIN-2123:
--

 Summary: Scale-out CI capacity by leveraging individual 
contributor's travis account
 Key: ZEPPELIN-2123
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2123
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee moon soo
Assignee: Lee moon soo


h3. Motivation

Recently INFRA-13469 reduced simultaneous build capacity of Zeppelin project to 
5 from 11.

After that, although https://github.com/apache/zeppelin/pull/2003 reduced CI 
build time by 60%, it's not very difficult to see pullrequests are waiting more 
than 10 hours in the queue to be tested.

It's mainly because of Apache Zeppelin uses ASF's travis account and the same 
account serves all project in ASF. It's easy to guess that there will be tons 
of build requests from various projects in ASF.

By the way, individual contributor fork Apache Zeppelin repository on github to 
make a pullrequest. And it's not very difficult to setup travis for the fork.

If Apache Zeppelin project can leverage all individual contributors travis 
account to build the pullrequest, that'll give many advantages.

 - Individual contributor will have 5 simultaneous build slot on travis.
 - No other project shares the travis slot.
 - Individual contributor can control build - cancel, restart


h3. How it works

1. Individual contributor setup travis on Apache Zeppelin fork. (and turn on 
"Build pushes")
2. Contributor pushes the branch to forked repository
   -> Triggers Travis CI build
3. Contributor creates pullrequest to ApacheZeppelin repository
  -> Triggers Jenkins CI build
4. Jenkins CI build script checks individual contributors Travis CI build 
status.

Jenkins CI build script will not actually build the project but will just check 
contributors Travis CI build status. And Jekins CI build script will run on ASF 
infra (builds.apache.org)

h3. Things to do

Following tasks need to be done.

1. Create build CI script for Jenkins that checks contributor's travis CI
2. Setup Jenkins configuration on builds.apache.org
3. Ask INFRA to turn off pullrequest build on Travis-CI and add Jekins for 
pullrequest build
4. Add travis setup after fork in how to contribute guide.



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

[GitHub] zeppelin pull request #2026: [ZEPPELIN-2123] Travis build status check scrip...

[Leemoonsoo]

GitHub user Leemoonsoo opened a pull request:

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

[ZEPPELIN-2123] Travis build status check script

### What is this PR for?
This script is designed to check contributors travis CI build state when 
pullrequest is created.


### What type of PR is it?
Feature

### Todos
* [x] - check travis build status

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

### How should this be tested?

Run script with `python ./travis_check.py [Author] [Branch name] [Commit 
hash]`.
For example
```
moon$ python ./travis_check.py Leemoonsoo ZEPPELIN-2120 44b9403
[2017-02-16 18:55:43] Author: Leemoonsoo, branch: ZEPPELIN-2120, commit: 
44b9403
[2017-02-16 18:55:43] 
[2017-02-16 18:55:48] Get build status ...
https://travis-ci.org/Leemoonsoo/zeppelin/builds/202172366
[1] OK
[2] Running ...
[3] Running ...
[4] OK
[5] OK
[6] Running ...
[7] OK
[8] Error 1
[9] Running ...
1 job(s) failed, 4 job(s) running
```

### 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/Leemoonsoo/zeppelin ZEPPELIN-2123

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

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


commit 7de1c24f020510e9a09be45521134e72005ca61b
Author: Lee moon soo 
Date:   2017-02-16T10:20:09Z

Travis build status check script




---
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 #2023: [ZEPPELIN-2114]: adding reload endpoint + fixin...

[Remilito]

GitHub user Remilito reopened a pull request:

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

[ZEPPELIN-2114]: adding reload endpoint + fixing test

### What is this PR for?
Adding endpoint in NotebookRepoRestApi to trigger reload and broadcast of 
the note list.
Sending a GET request to /api/notebook-repositories/reload will trigger a 
reload of the note list, just like the reload button does on the homepage.
Q: If you think this endpoint belongs to another API (NotebookRestApi?), 
let me know.

### What type of PR is it?
Improvement

### Todos


### What is the Jira issue?


### How should this be tested?
0. add (or remove) a note in the notebook repository
1. curl -x GET http://HOST:PORT/api/notebook-repository/reload
2. verify that you the note list in Zeppelin's home page now contains (or 
does not contain anymore) the note.

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? NO
* Is there breaking changes for older versions? NO
* Does this needs documentation? NotebookRepoRestApi does not have 
documentation yet. Could add it in another PR if needed.


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

$ git pull https://github.com/Remilito/zeppelin ZEPPELIN-2114

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

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


commit e380fe4c75827e7f17c0d8e9a9909bf4de25d6f4
Author: Remilito 
Date:   2017-02-15T16:49:00Z

[ZEPPELIN-2114]: adding reload endpoint + fixing 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.
---

Re: [DISCUSS] Scaling out CI capability

[Jeff Zhang]

Great, can't wait to try this.



moon soo Lee 于2017年2月16日周四 下午6:35写道：

> Hi Apache Zeppelin contributors!
>
> Recently, it's not very difficult to see pullrequest is waiting more than
> 10 hours to get travis-ci build slot.
>
> It's because of all ASF project shares the same travis account and the
> account's capability is limited. Although ASF assigned 5 concurrent build
> capacity to Zeppelin, it's not dedicated slot, it's more like max
> concurrent build limit, so when ASF travis is busy, Zeppelin pullrequest
> should wait.
>
> But each contributor can get 5 concurrent build capacity for opensource
> project. if we can leverage that, Zeppelin will no longer suffer from CI
> build capacity.
>
> I created https://issues.apache.org/jira/browse/ZEPPELIN-2123 and it
> includes proposed way, how Zeppelin can leverage individual contributors
> travis account.
> And created required script https://github.com/apache/zeppelin/pull/2026.
>
> Please take a look the proposal. Any feedback would be really appreciated!
>
> Thanks,
> moon
>

[GitHub] zeppelin issue #2024: [ZEPPELIN-411] JDK8 support

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
And concerning your contribution, we discussed it before and concluded it's 
too early to move JDK8. If you think it's right time to move on, please start 
discussion again in dev@ and user@


---
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 #2023: [ZEPPELIN-2114]: adding reload endpoint + fixin...

[Remilito]

Github user Remilito closed the pull request at:

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


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

[DISCUSS] Scaling out CI capability

[moon soo Lee]

Hi Apache Zeppelin contributors!

Recently, it's not very difficult to see pullrequest is waiting more than
10 hours to get travis-ci build slot.

It's because of all ASF project shares the same travis account and the
account's capability is limited. Although ASF assigned 5 concurrent build
capacity to Zeppelin, it's not dedicated slot, it's more like max
concurrent build limit, so when ASF travis is busy, Zeppelin pullrequest
should wait.

But each contributor can get 5 concurrent build capacity for opensource
project. if we can leverage that, Zeppelin will no longer suffer from CI
build capacity.

I created https://issues.apache.org/jira/browse/ZEPPELIN-2123 and it
includes proposed way, how Zeppelin can leverage individual contributors
travis account.
And created required script https://github.com/apache/zeppelin/pull/2026.

Please take a look the proposal. Any feedback would be really appreciated!

Thanks,
moon

[GitHub] zeppelin issue #2024: [ZEPPELIN-411] JDK8 support

[DmytroShkvyra]

Github user DmytroShkvyra commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
@jongyoul Should I close ZEPPELIN-411 as "wont fix"?


---
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 #2024: [ZEPPELIN-411] JDK8 support

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
You don't have to do it because we eventually will move to further JDK 
version


---
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 #2024: [ZEPPELIN-411] JDK8 support

[DmytroShkvyra]

Github user DmytroShkvyra commented on the issue:

https://github.com/apache/zeppelin/pull/2024
  
@jongyoul May be make sense just create PR only for try moving to JDK8 and 
test this with Travis? Anyway nobody will not merge it to zeppelin without 
approve.


---
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-2124) Missing dependencies array in interpreter.json after upgrade from 0.6.2 to 0.7.0

[Frank Rosner (JIRA)]

Frank Rosner created ZEPPELIN-2124:
--

 Summary: Missing dependencies array in interpreter.json after 
upgrade from 0.6.2 to 0.7.0
 Key: ZEPPELIN-2124
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2124
 Project: Zeppelin
  Issue Type: Bug
  Components: conf
Affects Versions: 0.7.0
Reporter: Frank Rosner


h4. Problem

We upgraded our Zeppelin instance from 0.6.2 to 0.7.0 today and after that we 
were not able to add any new dependencies to the interpreters.

The JS console revealed that {{a.dependencies is undefined}}. This happens 
because the interpreter configuration ({{interpreter.json}} now has to contain 
a {{dependencies}} array, which was not the case in 0.6.2.

After adding {{dependencies: [],}} to {{interpreter.json}} it is working just 
fine.

h4. Solution

If the {{dependencies}} array is not present it should either assume that it is 
empty or fail fast. It should not throw invisible errors in JavaScript.



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

[jira] [Created] (ZEPPELIN-2125) Download helium.json when really needed

[Hoon Park (JIRA)]

Hoon Park created ZEPPELIN-2125:
---

 Summary: Download helium.json when really needed
 Key: ZEPPELIN-2125
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2125
 Project: Zeppelin
  Issue Type: Improvement
  Components: helium
Reporter: Hoon Park
 Fix For: 0.8.0


Currently, {{getAllPackageInfo}} function fetch {{helium.json}} every time. We 
can improve this by

- Downloading it's really necessary. For example, startup, refresh button is 
clicked.
- Otherwise, Let's use cache.



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

[GitHub] zeppelin issue #2015: [ZEPPELIN-2103] Unnecessary read to Helium registry

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2015
  
I will review this 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 pull request #1985: [ZEPPELIN-2075] Can't stop infinite `while` sta...

[astroshim]

GitHub user astroshim reopened a pull request:

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

[ZEPPELIN-2075] Can't stop infinite `while` statement in pyspark 
Interpreter.

### What is this PR for?
If following code runs with Pyspark Interpreter, there is no way to cancel 
except Zeppelin Server restart.
```
%spark.pyspark
import time

while True:
time.sleep(1)
print("running..")
```

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


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


### How should this be tested?
Run above code with Pyspark Interpreter and try to cancel.


### Screenshots (if appropriate)
- before
![pyspark 
before](https://cloud.githubusercontent.com/assets/3348133/22696141/615c1206-ed90-11e6-9bbb-339ecdec73fc.gif)


- after
![pyspark 
after](https://cloud.githubusercontent.com/assets/3348133/22696168/70899172-ed90-11e6-99e1-342eb4094b2c.gif)


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


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

$ git pull https://github.com/astroshim/zeppelin ZEPPELIN-2075

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

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


commit 6731e5628c5c139bd9f7189416a0312313cfda7a
Author: astroshim 
Date:   2017-02-07T14:47:45Z

add signal to cancel job

commit 65d8cc697179d1e12f18e95cc04e30a43608e7cb
Author: astroshim 
Date:   2017-02-07T14:54:23Z

init python pid variable

commit 678c183000ce194cfd17c8a6979ccedf6611a83f
Author: astroshim 
Date:   2017-02-08T04:23:58Z

remove signal handler

commit c0cac4ee0df9bf3140c3465da5a4679dca87f6c1
Author: astroshim 
Date:   2017-02-08T04:36:03Z

fix logging

commit f26eacf5041eb266d04c237df50be42fdd86f87b
Author: astroshim 
Date:   2017-02-12T03:30:22Z

add test-case for canceling.

commit b60d89a5ba4aae0fb983dcfea2bed1b03e1349b6
Author: astroshim 
Date:   2017-02-15T06:06:57Z

Merge branch 'master' into ZEPPELIN-2075

commit bc12eaaec6dcfe06911359ed5cae7f9d663d66e0
Author: astroshim 
Date:   2017-02-15T08:11:14Z

pass pid to java




---
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 #2027: [ZEPPELIN-791] Build infra: move all RAT to roo...

[DmytroShkvyra]

GitHub user DmytroShkvyra opened a pull request:

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

[ZEPPELIN-791] Build infra: move all RAT to root pom.xml

### What is this PR for?
Is is better have a single place where we manage project-wise RAT 
exclusions for a contributions under licenses different from Apache, then let 
maven sub-modules have them as we do now (makes things harder to track) 


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

### Todos
N/A

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

### How should this be tested?
mvn verify -DskipTests

### 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/DmytroShkvyra/zeppelin ZEPPELIN-791

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

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


commit 528c8a6121ad90e19f1dc7a18705f31e8c0e0d49
Author: DmytroShkvyra 
Date:   2017-02-16T18:14:31Z

[ZEPPELIN-791] Build infra: move all RAT to root pom.xml




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