[GitHub] zeppelin issue #2407: [ZEPPELIN-1907] Shell Interpreter does not renew ticke...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2407
  
@felixcheung ping


---
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 #2426: Remove ticket after logout

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2426
  
@Leemoonsoo  can you help review this.
Jenkins 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 pull request #2414: [ZEPPELIN-2657] Add group search filter option ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2426: Remove ticket after logout

[prabhjyotsingh]

Github user prabhjyotsingh closed the pull request at:

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


---
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 #2426: Remove ticket after logout

[prabhjyotsingh]

GitHub user prabhjyotsingh reopened a pull request:

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

Remove ticket after logout

### What is this PR for?
IMO on logout of user Z-sever should also remove ticket.

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

### How should this be tested?
On logout and login, Z-sever should return a new ticket for the same user.

### Screenshots (if appropriate)
N/A

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


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

$ git pull https://github.com/prabhjyotsingh/zeppelin fix/removeTicket

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

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


commit 64ef34f5674293a03f0fafcf928395b56b41a98e
Author: Prabhjyot Singh 
Date:   2017-06-21T17:41:16Z

Remove ticket after logout




---
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 #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

GitHub user 1ambda reopened a pull request:

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

[ZEPPELIN-2670] fix: DON'T reset all helium config when saving display order

### What is this PR for?

Reordering vis package using the `save` button resets all helium 
configuration.

Originally, reported in 
[ZEPPELIN-2656](https://issues.apache.org/jira/browse/ZEPPELIN-2656) but 
created a new issue track that problem only.

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

### Todos

DONE

### What is the Jira issue?

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

### How should this be tested?

1. Enable 2 vis packages
2. Change display order
3. Refresh (**necessary**) the page
4. Change display order again

### Screenshots (if appropriate)

 before


![2670_before](https://user-images.githubusercontent.com/4968473/27380768-702d2dd0-56bb-11e7-8565-00b08550b343.gif)


 after



![2670_after](https://user-images.githubusercontent.com/4968473/27380773-74704058-56bb-11e7-95b7-035eb9cd8116.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/1ambda/zeppelin 
ZEPPELIN-2670/saving-helium-vis-order-should-not-reset

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

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


commit 8edfdf75380df098558b4fcd9a3da5fd93a2ea53
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:14Z

style: move getVisualizationPackageOrder func

commit bb66c2bc4703a7e26f95be1a2e33e2d5cbc00cb7
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:36Z

style: Rename setVisualizationPackageOrder

commit d1aea4e85721beae1ddbcc2d0b5b14450850a955
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:15:14Z

style: reindent saveBundleOrder

commit 13bb650842b530a4f3801ae210d7eb916caf4730
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:45:16Z

fix: DON'T build when set orders

commit 7159a965c1b19f211f4c935408fc1f25051f4feb
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:05:38Z

fix: Fetch bundleOrder after getAllPackages

commit 86d960c1ec3c4b32d1eea42f6b2ead5e5d5289b5
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:15:57Z

fix: DON'T call unncessary init()

commit 04e046e898f5029e203e96968fbf5168afb65931
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T10:45:06Z

fix: DON'T reset when getting display order




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

[GitHub] zeppelin pull request #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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 #2411: [ZEPPELIN-2650] fix: DON'T set uppercase automa...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2371: [ZEPPELIN-2596] Improving documentation page

[khalidhuseynov]

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2371
  
@1ambda could you plz resolved conflicts here?


---
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 #2391: [ZEPPELIN-2501] Better Job Navigation Experienc...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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 #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

GitHub user 1ambda reopened a pull request:

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

[ZEPPELIN-2670] fix: DON'T reset all helium config when saving display order

### What is this PR for?

Reordering vis package using the `save` button resets all helium 
configuration.

Originally, reported in 
[ZEPPELIN-2656](https://issues.apache.org/jira/browse/ZEPPELIN-2656) but 
created a new issue track that problem only.

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

### Todos

DONE

### What is the Jira issue?

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

### How should this be tested?

1. Enable 2 vis packages
2. Change display order
3. Refresh (**necessary**) the page
4. Change display order again

### Screenshots (if appropriate)

 before


![2670_before](https://user-images.githubusercontent.com/4968473/27380768-702d2dd0-56bb-11e7-8565-00b08550b343.gif)


 after



![2670_after](https://user-images.githubusercontent.com/4968473/27380773-74704058-56bb-11e7-95b7-035eb9cd8116.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/1ambda/zeppelin 
ZEPPELIN-2670/saving-helium-vis-order-should-not-reset

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

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


commit 8edfdf75380df098558b4fcd9a3da5fd93a2ea53
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:14Z

style: move getVisualizationPackageOrder func

commit bb66c2bc4703a7e26f95be1a2e33e2d5cbc00cb7
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:36Z

style: Rename setVisualizationPackageOrder

commit d1aea4e85721beae1ddbcc2d0b5b14450850a955
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:15:14Z

style: reindent saveBundleOrder

commit 13bb650842b530a4f3801ae210d7eb916caf4730
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:45:16Z

fix: DON'T build when set orders

commit 7159a965c1b19f211f4c935408fc1f25051f4feb
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:05:38Z

fix: Fetch bundleOrder after getAllPackages

commit 86d960c1ec3c4b32d1eea42f6b2ead5e5d5289b5
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:15:57Z

fix: DON'T call unncessary init()

commit 04e046e898f5029e203e96968fbf5168afb65931
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T10:45:06Z

fix: DON'T reset when getting display order




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

[GitHub] zeppelin issue #2425: [ZEPPELIN-2673] - Helium skip node install

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2425
  
Does Zeppelin already check whether node + npm + yarn is installed or not?


---
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 #2419: [ZEPPELIN-2666] docs: Add docker usage to download pag...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2419
  
@Leemoonsoo I faced that issue few times. So I think we need to open and 
resolve it. Otherwise, people don't know what zeppelin doesn't up in their 
browser.


---
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 #2428: [ZEPPELIN-1470] limiting results from jdbc

[herval]

GitHub user herval opened a pull request:

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

[ZEPPELIN-1470] limiting results from jdbc

### What is this PR for?

One thing we tracked down is that if you issue a large query on a very 
large table, it will simply try to load all results (and then cap them on 
Zeppelin's side), which seems suboptimal (and will freeze the server). Setting 
this on the JDBC level seems to solve the problem.

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

### Todos
* [ ] - Task

### How should this be tested?

- Create or use a table with a very large number of rows. In our tests, I 
simply created a:

```
createdb zeppelin_test

psql zeppelin_test

create table too_many_rows(n int)
```

And added 5m rows to it.

Making a paragraph like this will hang without this:
```
%zeppelin_test

select * from too_many_rows
```

### 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/herval/zeppelin hfreire/limit-row-count

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

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


commit f574f84706e4b345b62bebd456964928c4b787e8
Author: Herval Freire 
Date:   2017-06-21T23:54:29Z

limiting results from jdbc




---
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 #2427: Rinterpreter

[test2016new]

GitHub user test2016new opened a pull request:

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

Rinterpreter

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

### Todos
* [ ] - Task

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/elbamos/Zeppelin-With-R rinterpreter

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

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






---
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 #2397: [ZEPPELIN-2592] Ensure open stream is closed

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2397
  
LGTM and merge to master if no further 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.
---

[GitHub] zeppelin pull request #2398: [ZEPPELIN-2622] Add Zeppelin Git info REST API

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2413: [ZEPPELIN-2654] add roles to permissions of interprete...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2413
  
LGTM and merge to master if 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 pull request #2421: [ZEPPELIN-2663] Helium vizualisations do not ap...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

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

Merge to master as a Hotfix as it fixes broken feature.


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

New committer: Park Hoon

[moon soo Lee]

The Project Management Committee (PMC) for Apache Zeppelin has invited Park
Hoon (1ambda) to become a committer and we are pleased to announce that has
accepted.

Please join us to welcome.

The Apache Zeppelin PMC

[GitHub] zeppelin pull request #2426: Remove ticket after logout

[prabhjyotsingh]

GitHub user prabhjyotsingh opened a pull request:

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

Remove ticket after logout

### What is this PR for?
IMO on logout of user Z-sever should also remove ticket.

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

### How should this be tested?
On logout and login, Z-sever should return a new ticket for the same user.

### Screenshots (if appropriate)
N/A

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


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

$ git pull https://github.com/prabhjyotsingh/zeppelin fix/removeTicket

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

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


commit 64ef34f5674293a03f0fafcf928395b56b41a98e
Author: Prabhjyot Singh 
Date:   2017-06-21T17:41:16Z

Remove ticket after logout




---
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: Contributing to Apache Zeppelin

[Felix Cheung]

Hi welcome!

Please feel free to open JIRA and add a comment that you are working on it - 
there is no need to wait to have the JIRA assigned to you to start.



_
From: Marco Tagliabue 
>
Sent: Wednesday, June 21, 2017 9:36 AM
Subject: Contributing to Apache Zeppelin
To: >


Dear community,

I’m Marco Tagliabue, software engineer at Radicalbit. Currently we are using 
Zeppelin inside our company and for this reason I would like to contribute to 
the project, fixing some issues that we have seen in Flink Interpreter. I’m 
writing here for asking permissions to independently assign issues to myself in 
ASF Jira.

Thank you in advance for your time.

Best Regards,

Marco Tagliabue

Contributing to Apache Zeppelin

[Marco Tagliabue]

Dear community, 

I’m Marco Tagliabue, software engineer at Radicalbit. Currently we are using 
Zeppelin inside our company and for this reason I would like to contribute to 
the project, fixing some issues that we have seen in Flink Interpreter. I’m 
writing here for asking permissions to independently assign issues to myself in 
ASF Jira.

Thank you in advance for your time.

Best Regards,

Marco Tagliabue

[GitHub] zeppelin pull request #2425: [ZEPPELIN-2673] - Helium skip node install

[necosta]

GitHub user necosta opened a pull request:

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

[ZEPPELIN-2673] - Helium skip node install

### What is this PR for?
Skip altogether the install of NPM. Node and YarnPkg when the packages have 
been successfully downloaded into the node installer dir (default 
../local-repo/helium-bundles/node/)

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

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

### How should this be tested?
Open Zeppelin > Helium > Enable Plugin > Check NPM/Node install > Stop 
Zeppelin > Start Zeppelin > Enable Plugin > Check skip of NPM/Node install

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


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

$ git pull https://github.com/nokia/zeppelin helium_skip_node_install

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

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


commit b24f4ff026c0213b11e5501be5391451839461d2
Author: Nelson Costa 
Date:   2017-06-21T15:00:02Z

Skip Helium Node and NPM re-install after Zeppelin re-start

commit 05459aaa9584e222a14262930068b3c98e8c1dcc
Author: Nelson Costa 
Date:   2017-06-21T16:15:30Z

ESPOOBL-1625: Refactor check mode




---
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-2674) Update Apache Ignite version up to 1.9 in Ignite Interpreter

[Andrey Gura (JIRA)]

Andrey Gura created ZEPPELIN-2674:
-

 Summary: Update Apache Ignite version up to 1.9 in Ignite 
Interpreter
 Key: ZEPPELIN-2674
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2674
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.7.2
Reporter: Andrey Gura
Assignee: Andrey Gura


Need to update Apache Ignite version up to 1.9 in Ignite Interpreter.



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

[GitHub] zeppelin pull request #2423: [ZEPPELIN-2672] Fix interpreter repos url toolt...

[necosta]

GitHub user necosta reopened a pull request:

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

[ZEPPELIN-2672] Fix interpreter repos url tooltip

### What is this PR for?
Fixing regression on showing interpreter repos tooltip

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

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

### How should this be tested?
Zeppelin > Interpreter > Repository > (Mouse over) central/local/other

### Screenshots 
After this fix:

![image](https://user-images.githubusercontent.com/26248959/27374071-6be20736-5662-11e7-9f30-7514fe342821.png)


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


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

$ git pull https://github.com/nokia/zeppelin zeppelin2672

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

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


commit c2fa47afb01ed9a7cab9b88fb637455b8eed2259
Author: Nelson Costa 
Date:   2017-06-20T18:49:48Z

[ZEPPELIN-2672] Fix interpreter repos url tooltip

commit 2d6514f4a5e89248657403167fae38d4cbfe179f
Author: Nelson Costa 
Date:   2017-06-21T14:34:58Z

[ZEPPELIN-2672] Also fixed column selector




---
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 #2423: [ZEPPELIN-2672] Fix interpreter repos url toolt...

[necosta]

Github user necosta closed the pull request at:

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


---
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-2673) Helium - Improve Node and NPM install check

[Nelson Costa (JIRA)]

Nelson Costa created ZEPPELIN-2673:
--

 Summary: Helium - Improve Node and NPM install check
 Key: ZEPPELIN-2673
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2673
 Project: Zeppelin
  Issue Type: Bug
  Components: helium
Reporter: Nelson Costa
Assignee: Nelson Costa
 Fix For: 0.8.0


Hi! I noticed that every time we start Zeppelin, when we enable a Helium 
plugin, we are re-installing Node, NPM and YarnPkg. This is unnecessary.



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

[GitHub] zeppelin issue #2422: [WIP] [ZEPPELIN-2627] Interpreter refactor

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2422
  
Wow ~ It changes pretty big including some code styles. Before reviewing 
it, How about reverting code style? It's not related to feature itself, then we 
can fix the style with minor pr. And can you describe what is the purpose of 
this PR? Which logic do you want to refactor? this kind of description will be 
help to review it. I glanced at it few minutes, and it seems to relocate some 
classes and introduce remoteFunction concept. Can you explain them more?


---
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 #2268: [ZEPPELIN-2403] interpreter property widgets

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2268
  
Ready to 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 #2413: [ZEPPELIN-2654] add roles to permissions of interprete...

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2413
  
Ready to 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 #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2421
  
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 pull request #2421: [ZEPPELIN-2663] Helium vizualisations do not ap...

[conker84]

GitHub user conker84 reopened a pull request:

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

[ZEPPELIN-2663] Helium vizualisations do not appear in the list of builtInt 
visualizations in paragraph

### What is this PR for?
Within the helium only default build in visualizations are in the list of 
possible visualizations


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

### Todos
* [x] - Correct the bug

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

### How should this be tested?
* git clone zeppelin
* mvn clean package
* run, open browser
* go to helium
* enable few additional visualizations
* create new note and add paragraph: print("%table text\tme\n")

### Screenshots (if appropriate)
No

### 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/conker84/zeppelin master

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

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


commit 5d8e50e365dfce949f08f5334e683e82475e9029
Author: conker84 
Date:   2017-06-19T21:02:17Z

Bugfix

commit 02c4efb9dce945635ececb13fabcf60945448276
Author: conker84 
Date:   2017-06-19T21:14:07Z

Commit to trigger travis

commit 1a846ff3eca51a5cb98e5619a85496d3868e0f04
Author: conker84 
Date:   2017-06-20T08:47:40Z

Removed whitespace




---
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 #2421: [ZEPPELIN-2663] Helium vizualisations do not ap...

[conker84]

Github user conker84 closed the pull request at:

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


---
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 #2420: [ZEPPELIN-2628] Serialization issue with RuntimeTypeAd...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2420
  
It seems that we have a backward compatibility problem.


---
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 #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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 #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

GitHub user 1ambda reopened a pull request:

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

[ZEPPELIN-2670] fix: DON'T reset all helium config when saving display order

### What is this PR for?

Reordering vis package using the `save` button resets all helium 
configuration.

Originally, reported in 
[ZEPPELIN-2656](https://issues.apache.org/jira/browse/ZEPPELIN-2656) but 
created a new issue track that problem only.

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

### Todos

DONE

### What is the Jira issue?

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

### How should this be tested?

1. Enable 2 vis packages
2. Change display order
3. Refresh (**necessary**) the page
4. Change display order again

### Screenshots (if appropriate)

 before


![2670_before](https://user-images.githubusercontent.com/4968473/27380768-702d2dd0-56bb-11e7-8565-00b08550b343.gif)


 after



![2670_after](https://user-images.githubusercontent.com/4968473/27380773-74704058-56bb-11e7-95b7-035eb9cd8116.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/1ambda/zeppelin 
ZEPPELIN-2670/saving-helium-vis-order-should-not-reset

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

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


commit 8edfdf75380df098558b4fcd9a3da5fd93a2ea53
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:14Z

style: move getVisualizationPackageOrder func

commit bb66c2bc4703a7e26f95be1a2e33e2d5cbc00cb7
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:36Z

style: Rename setVisualizationPackageOrder

commit d1aea4e85721beae1ddbcc2d0b5b14450850a955
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:15:14Z

style: reindent saveBundleOrder

commit 13bb650842b530a4f3801ae210d7eb916caf4730
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:45:16Z

fix: DON'T build when set orders

commit 7159a965c1b19f211f4c935408fc1f25051f4feb
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:05:38Z

fix: Fetch bundleOrder after getAllPackages

commit 86d960c1ec3c4b32d1eea42f6b2ead5e5d5289b5
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:15:57Z

fix: DON'T call unncessary init()

commit 04e046e898f5029e203e96968fbf5168afb65931
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T10:45:06Z

fix: DON'T reset when getting display order




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

[GitHub] zeppelin pull request #2424: [ZEPPELIN-2670] fix: DON'T reset all helium con...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2670] fix: DON'T reset all helium config when saving display order

### What is this PR for?

Reordering vis package using the `save` button resets all helium 
configuration.

Originally, reported in 
[ZEPPELIN-2656](https://issues.apache.org/jira/browse/ZEPPELIN-2656) but 
created a new issue track that problem only.

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

### Todos

DONE

### What is the Jira issue?

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

### How should this be tested?

1. Enable 2 vis packages
2. Change display order
3. Refresh (**necessary**) the page
4. Change display order again

### Screenshots (if appropriate)

 before


![2670_before](https://user-images.githubusercontent.com/4968473/27380768-702d2dd0-56bb-11e7-8565-00b08550b343.gif)


 after



![2670_after](https://user-images.githubusercontent.com/4968473/27380773-74704058-56bb-11e7-95b7-035eb9cd8116.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/1ambda/zeppelin 
ZEPPELIN-2670/saving-helium-vis-order-should-not-reset

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

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


commit 8edfdf75380df098558b4fcd9a3da5fd93a2ea53
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:14Z

style: move getVisualizationPackageOrder func

commit bb66c2bc4703a7e26f95be1a2e33e2d5cbc00cb7
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T06:31:36Z

style: Rename setVisualizationPackageOrder

commit d1aea4e85721beae1ddbcc2d0b5b14450850a955
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:15:14Z

style: reindent saveBundleOrder

commit 13bb650842b530a4f3801ae210d7eb916caf4730
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T07:45:16Z

fix: DON'T build when set orders

commit 7159a965c1b19f211f4c935408fc1f25051f4feb
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:05:38Z

fix: Fetch bundleOrder after getAllPackages

commit 86d960c1ec3c4b32d1eea42f6b2ead5e5d5289b5
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T08:15:57Z

fix: DON'T call unncessary init()

commit 04e046e898f5029e203e96968fbf5168afb65931
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-21T10:45:06Z

fix: DON'T reset when getting display order




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

[GitHub] zeppelin issue #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2421
  
@conker84 Could you close and reopen this issue? to trigger the jenkins 
(not travis CI) 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 #2423: [ZEPPELIN-2672] Fix interpreter repos url toolt...

[necosta]

GitHub user necosta reopened a pull request:

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

[ZEPPELIN-2672] Fix interpreter repos url tooltip

### What is this PR for?
Fixing regression on showing interpreter repos tooltip

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

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

### How should this be tested?
Zeppelin > Interpreter > Repository > (Mouse over) central/local/other

### Screenshots 
After this fix:

![image](https://user-images.githubusercontent.com/26248959/27374071-6be20736-5662-11e7-9f30-7514fe342821.png)


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


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

$ git pull https://github.com/nokia/zeppelin zeppelin2672

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

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


commit c2fa47afb01ed9a7cab9b88fb637455b8eed2259
Author: Nelson Costa 
Date:   2017-06-20T18:49:48Z

[ZEPPELIN-2672] Fix interpreter repos url tooltip




---
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 #2423: [ZEPPELIN-2672] Fix interpreter repos url toolt...

[necosta]

Github user necosta closed the pull request at:

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


---
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 #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[conker84]

Github user conker84 commented on the issue:

https://github.com/apache/zeppelin/pull/2421
  
@1ambda the CI it's finally 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 #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[conker84]

Github user conker84 commented on the issue:

https://github.com/apache/zeppelin/pull/2421
  
@1ambda the fork is up to date, i just restarted the job once time again, 
let's see
Thanks for the support!
Andrea


---
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 #2420: [ZEPPELIN-2628] Serialization issue with RuntimeTypeAd...

[necosta]

Github user necosta commented on the issue:

https://github.com/apache/zeppelin/pull/2420
  
Yes, @1ambda, 
The issue is on notebooks that contain "z.input("
On commit 7b585c7399f29, z.input was renamed to z.textbox, but loading old 
notebooks into 0.8 was not handled. 
The bug is on Note.java, addCloneParagraph, where we import forms without 
checking.
We are working on a fix that will be made available in a new pull request

FYI: @andreaTP 



---
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 #2423: [ZEPPELIN-2672] Fix interpreter repos url toolt...

[necosta]

GitHub user necosta opened a pull request:

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

[ZEPPELIN-2672] Fix interpreter repos url tooltip

### What is this PR for?
Fixing regression on showing interpreter repos tooltip

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

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

### How should this be tested?
Zeppelin > Interpreter > Repository > (Mouse over) central/local/other

### Screenshots 
After this fix:

![image](https://user-images.githubusercontent.com/26248959/27374071-6be20736-5662-11e7-9f30-7514fe342821.png)


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


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

$ git pull https://github.com/nokia/zeppelin zeppelin2672

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

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


commit c2fa47afb01ed9a7cab9b88fb637455b8eed2259
Author: Nelson Costa 
Date:   2017-06-20T18:49:48Z

[ZEPPELIN-2672] Fix interpreter repos url tooltip




---
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 #2422: [WIP] [ZEPPELIN-2627] Interpreter refactor

[zjffdu]

GitHub user zjffdu opened a pull request:

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

[WIP] [ZEPPELIN-2627] Interpreter refactor

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

### Todos
* [ ] - Task

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/zjffdu/zeppelin interpreter_refactor

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

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


commit 8ee3f45dffa7feff4b95f0ac0cdf6ac3fc69f61b
Author: Jeff Zhang 
Date:   2017-05-23T07:52:15Z

save

commit 2ca2188cd157ec509b5b982ffeaaae2d3f954d07
Author: Jeff Zhang 
Date:   2017-06-18T05:52:26Z

fix Job race




---
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-2672) Show tooltip on interpreter repositories section

[Nelson Costa (JIRA)]

Nelson Costa created ZEPPELIN-2672:
--

 Summary: Show tooltip on interpreter repositories section
 Key: ZEPPELIN-2672
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2672
 Project: Zeppelin
  Issue Type: Bug
Reporter: Nelson Costa
Assignee: Nelson Costa
Priority: Minor
 Fix For: 0.8.0


Hi, in previous versions (0.6 and 0.7), we had a tooltip showing us the repo 
url assigned to interpreter repos (central, local, any other)
In 0.8 it no longer shows and this should be fixed.
Note that, given the "central" repo url comes from 
ZEPPELIN_INTERPRETER_DEP_MVNREPO it is important to see in the UI it's value




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

[GitHub] zeppelin issue #2421: [ZEPPELIN-2663] Helium vizualisations do not appear in...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2421
  
1. I checked manually `testSparkInterpreterDependencyLoading` in this 
branch. It works.
2. Helium icons now appear. 

@conker84 Could you please rebase?


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