date:20170223

[jira] [Created] (ZEPPELIN-2167) User with insufficient privileges can still restore files by renaming files in/out of Trash

2017-02-23 Thread Deepesh Khandelwal (JIRA)

Deepesh Khandelwal created ZEPPELIN-2167:


 Summary: User with insufficient privileges can still restore files 
by renaming files in/out of Trash
 Key: ZEPPELIN-2167
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2167
 Project: Zeppelin
  Issue Type: Bug
  Components: security
Reporter: Deepesh Khandelwal
Priority: Critical


Steps to reproduce:
# Create a notebook "test_nb" as bob.
# Delete the notebook
# Login as mary and try restoring "test_nb" from Trash folder. The system 
correctly complains of insufficient privileges.
# Open the "test_nb" notebook from Trash folder. The notebook opens with title 
"~Trash/test_nb".
# Edit the title and remove the prefix "~Trash".
If you now look at the list of notebooks there is no file "test_nb" in Trash.
Interestingly when you try and delete the recently moved file from Trash it 
complains that mary does not have privileges to delete it. Edit the title of 
that notebook to "~Trash/test_nb" and it goes back to Trash folder.




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

[GitHub] zeppelin issue #2058: [ZEPPELIN-2147] zeppelin should redirect to login page...

2017-02-23 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2058
  
Thank you @r-kamath  for reviewing this. Have handled your review 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 #2049: [ZEPPELIN-1586][MINOR] add new line char before...

2017-02-23 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread NohSeho

Github user NohSeho commented on the issue:

https://github.com/apache/zeppelin/pull/2060
  
@khalidhuseynov great! thanks alot :)


---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread NohSeho

GitHub user NohSeho reopened a pull request:

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

[ZEPPELIN-2094] Decrease npm install retry time

### What is this PR for?
Itâs too delayed for npm install when computer do not connected any 
networks.
Beacause when npm install, it has too long retry timeout.
This PR is to decrease retry timeout when npm install.


### What type of PR is it?
Improvement

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

### How should this be tested?
you must enable any one helium before test

Line 197 In zeppelin-zengine 
org.apache.zeppelin.helium.HeliumBundleFactory.java

First set with 
`String npmCommand = "install âloglevel=errorâ;`
and You donât connect any ethernet or wireless internet.
build & run

and set with
`String npmCommand = "install âfetch-retries=2 âfetch-retry-factor=1 
âfetch-retry-mintimeout=5000 âloglevel=errorâ;`
also donât connect any networks, build & run.

WHY
retries = 2
factor = 1
mintimeout = 5(sec)?

npm use [retry](https://github.com/tim-kos/node-retry) module to retry.
It refers [this 
article](http://dthain.blogspot.kr/2009/02/exponential-backoff-in-distributed.html)
 for retry algorithms.
It is a math which structured _Math.min(Math.round(random * minTimeout * 
Math.pow(factor, attempt)), maxTimeout)_.
In retry source code, between two retries. First retry doesn't care 
_Math.min()_, just _Math.round(random * minTimeout * Math.pow(factor, 
attempt))_)


Description | Before | After
--- | --- | ---
Condition | npm's default settingrandom = False = 1retry = 
2minTimeout = 10 (sec)maxTimeout = 60 (sec)factor = 10 | custom 
settingrandom = False = 1retry = 2minTimeout = 5 
(sec)maxTimeout = 60 (sec)factor = 1
First retry | Math.round(1 * 10 (sec) * 10^1)) | Math.round(1 * 5 (sec) * 
1^1))
First retry result (Approximately) | 100 (sec) | 5 (sec)
Second retry | Math.min(Math.round(1 * 10 (sec) * 10^2), 60 (sec)) | 
Math.min(Math.round(1 * 5 (sec) * 1^2), 60 (sec))
Second retry result (Approximately) | 60 (sec) | 5 (sec)
Total waiting time (Approximately) | 160 (sec) | 10 (sec)


You can check like this below Screenshots.

### Screenshots
Before | After
---|---
https://cloud.githubusercontent.com/assets/1144643/23267951/9deaec6e-fa2f-11e6-9171-5792f24de76d.png;>
 | https://cloud.githubusercontent.com/assets/1144643/23267954/a12c0c0a-fa2f-11e6-99cd-335deef607ac.png;>


### 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/NohSeho/zeppelin ZEPPELIN-2094

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

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


commit b7296ca0d60ba99d6c874831330a823ccea2f2b0
Author: NohSeho 
Date:   2017-02-23T15:59:57Z

[ZEPPELIN-2094] Decrease npm install retry time




---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread NohSeho

Github user NohSeho closed the pull request at:

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


---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread khalidhuseynov

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2060
  
@NohSeho closing and opening PR may help


---
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 #2055: [ZEPPELIN-1999] get interpreter property with replaced...

2017-02-23 Thread tinkoff-dwh

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2055
  
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 #2064: [ZEPPELIN-2164] Typo in Insufficient Privileges popup ...

2017-02-23 Thread r-kamath

Github user r-kamath commented on the issue:

https://github.com/apache/zeppelin/pull/2064
  
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 #2064: [ZEPPELIN-2164] Typo in Insufficient Privileges popup ...

2017-02-23 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2064
  
@Leemoonsoo  help review this.


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

[GitHub] zeppelin pull request #2064: [ZEPPELIN-2164] Typo in Insufficient Privileges...

2017-02-23 Thread prabhjyotsingh

GitHub user prabhjyotsingh opened a pull request:

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

[ZEPPELIN-2164] Typo in Insufficient Privileges popup of Zeppelin

### What is this PR for?
When trying to delete a note of another user Zeppelin correctly throws a 
popup for insufficient privileges but has a small typo "removenote" (no space 
between remove note). Similar issue exist for renaming notebook "renamenote".

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

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

### How should this be tested?
Refer before/after screen shot

### Screenshots (if appropriate)
Before:
https://cloud.githubusercontent.com/assets/674497/23292690/66b808fa-fa87-11e6-9bde-4f9fbbb1cb67.png;>


After:
https://cloud.githubusercontent.com/assets/674497/23292691/66c0e9c0-fa87-11e6-9abc-16dc7b52ce3c.png;>



### 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/prabhjyotsingh/zeppelin ZEPPELIN-2164

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

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


commit c4c8222f83114655956d160f684858b5c6e21fe3
Author: Prabhjyot Singh 
Date:   2017-02-24T06:17:24Z

ZEPPELIN-2164: Typo in Insufficient Privileges popup of Zeppelin




---
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-2166) HeliumBundleFactory can't resolve es6+ syntax

2017-02-23 Thread Hoon Park (JIRA)

Hoon Park created ZEPPELIN-2166:
---

 Summary: HeliumBundleFactory can't resolve es6+ syntax
 Key: ZEPPELIN-2166
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2166
 Project: Zeppelin
  Issue Type: Improvement
  Components: front-end, helium
Affects Versions: 0.7.0
Reporter: Hoon Park
 Fix For: 0.7.1, 0.8.0


Currently, we don't use any preset. This cause error messages like

- when helium package includes es6+ syntax.

{code}
SyntaxError: Unexpected token import
at helium.service.js:36
at angular.js:10973
at processQueue (angular.js:15552)
at angular.js:15568
at Scope.$eval (angular.js:16820)
at Scope.$digest (angular.js:16636)
at Scope.$apply (angular.js:16928)
at done (angular.js:11266)
at completeRequest (angular.js:11464)
at XMLHttpRequest.requestLoaded (angular.js:11405)
{code}



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

[GitHub] zeppelin issue #2063: ZEPPELIN-2148: On creation of Bar graph zeppelin UI sh...

2017-02-23 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2063
  
Thank you for reviewing @r-kamath.  I've handled 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.
---

[jira] [Created] (ZEPPELIN-2165) Loading Scatter chart on Safari causes the browser to hang

2017-02-23 Thread Deepesh Khandelwal (JIRA)

Deepesh Khandelwal created ZEPPELIN-2165:


 Summary: Loading Scatter chart on Safari causes the browser to hang
 Key: ZEPPELIN-2165
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2165
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Reporter: Deepesh Khandelwal


When one clicks on various chart types for a table in Zeppelin, observed that 
Safari hangs when clicking in/out from the Scatter chart type. The browser 
basically becomes unusable at that point.

The problem is only seen on Safari and not in Chrome. Restarting the browser is 
the only recourse after this.



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

[GitHub] zeppelin issue #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread NohSeho

Github user NohSeho commented on the issue:

https://github.com/apache/zeppelin/pull/2060
  
I successfully restart build but it does not change.
How can I do this?

https://travis-ci.org/NohSeho/zeppelin/builds/204825105


---
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 #2063: ZEPPELIN-2148: On creation of Bar graph zeppelin UI sh...

2017-02-23 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2063
  
@1ambda  @Leemoonsoo  Help review this. This fixes the problem, but with a 
dirty hack.


---
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 #2063: ZEPPELIN-2148: On creation of Bar graph zeppeli...

2017-02-23 Thread prabhjyotsingh

GitHub user prabhjyotsingh opened a pull request:

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

ZEPPELIN-2148: On creation of Bar graph zeppelin UI shows it as mini graph

### What is this PR for?
On creation of Bar graph zeppelin UI shows it as mini graph, and is easily 
reproducible on safari.

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


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

### How should this be tested?
Check screen shot.

### Screenshots (if appropriate)
Before:

![zeppelin-2148-before](https://cloud.githubusercontent.com/assets/674497/23291765/b1469780-fa80-11e6-9a13-3ecb6ca275ba.gif)


After:

![zeppelin-2148-after](https://cloud.githubusercontent.com/assets/674497/23291751/9aa39122-fa80-11e6-962e-482e12c4bca5.gif)



### 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 ZEPPELIN-2148

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

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


commit 38a1198b5a26d4f43962a5d2c730c34dc76f5d28
Author: Prabhjyot Singh 
Date:   2017-02-24T05:25:26Z

ZEPPELIN-2148: On creation of Bar graph zeppelin UI shows it as mini graph




---
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-2164) Typo in Insufficient Privileges popup of Zeppelin

2017-02-23 Thread Deepesh Khandelwal (JIRA)

Deepesh Khandelwal created ZEPPELIN-2164:


 Summary: Typo in Insufficient Privileges popup of Zeppelin
 Key: ZEPPELIN-2164
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2164
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Reporter: Deepesh Khandelwal
Priority: Minor


When trying to delete a note of another user Zeppelin correctly throws a popup 
for insufficient privileges but has a small typo "removenote" (no space between 
remove note). Similar issue exist for renaming notebook "renamenote".



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

[GitHub] zeppelin issue #2053: [ZEPPELIN-1964] Layout info is lost after refresh

2017-02-23 Thread AhyoungRyu

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2053
  
Tested and it works well as expected. 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 #2037: [ZEPPELIN-2109][2110] Sortable Helium pkgs & Introduce...

2017-02-23 Thread AhyoungRyu

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2037
  
Ready for review 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 #2037: [ZEPPELIN-2109][2110] Sortable Helium pkgs & In...

2017-02-23 Thread AhyoungRyu

Github user AhyoungRyu closed the pull request at:

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


---
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 #2037: [ZEPPELIN-2109][2110] Sortable Helium pkgs & In...

2017-02-23 Thread AhyoungRyu

GitHub user AhyoungRyu reopened a pull request:

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

[ZEPPELIN-2109][2110] Sortable Helium pkgs & Introduce "INTERPRETER" type

### What is this PR for?

* Make Helium pkgs sortable
For now, we have 3 types of Helium packages: `VISUALIZATION`, `SPELL` and 
`APPLICATION`.
`VISUALIZATION` and `SPELL` type of pkgs can be published [NPM 
registry](https://www.npmjs.com/). Likewise, `APPLICATION` type pkg can be 
registered in [Maven central repository](http://search.maven.org/). 
But all available Helium packages are not sorted and shown in random order 
in Helium menu.
To do this, I put "NPM Packages" & "Maven Artifacts" button at top-right 
corner of Helium menu. 

* Introduce "INTERPRETER" type
As a first step of [ZEPPELIN-1993: Install interpreter from Helium 
menu](https://issues.apache.org/jira/browse/ZEPPELIN-1993), I added 
`INTERPRETER` type as a new Helium pkg type. Like 
[ZEPPELIN-1973](https://issues.apache.org/jira/browse/ZEPPELIN-1973) did, we 
can retrieve Maven artifact(which has `zeppelin-interpreter` as its dependency) 
info and save it to Helium online registry as well. 
For more detailed explanation, please see 
[ZEPPELIN-1993](https://issues.apache.org/jira/browse/ZEPPELIN-1993) and 
[ZEPPELIN-2110](https://issues.apache.org/jira/browse/ZEPPELIN-2110)'s 
description.

### What type of PR is it?
Improvement

### Todos
* [ ] - address feedback

### What is the Jira issue?
* [ZEPPELIN-2109](https://issues.apache.org/jira/browse/ZEPPELIN-2109) : 
Make Helium packages sortable in Helium menu
* [ZEPPELIN-2110](https://issues.apache.org/jira/browse/ZEPPELIN-2110) : 
List community & 3rd party interpreter registered at Maven central repo in 
Helium menu 

### How should this be tested?
To see how `INTERPRETER` type can be shown in Helium menu,

1. Replace temporarily 
[ZeppelinConfiguration.java#L46](https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L46)
 with [this 
url](https://raw.githubusercontent.com/AhyoungRyu/spark-notebook-example/master/helium-test.json)

2. Build \w below command and restart
```
 $ mvn clean package -DskipTests -pl 'zeppelin-zengine, zeppelin-server, 
zeppelin-interpreter'
```

3. Start web dev server under `ZEPPELIN_HOME/zeppelin-web` and browse 
`localhost:9000`
```
$ yarn run dev:helium
```

4. Go to Helium menu
### Screenshots (if appropriate)
 - How's it look?

![record](https://cloud.githubusercontent.com/assets/10060731/23219279/02fc234e-f962-11e6-86a9-30e7dc0953aa.gif)

 - Package selection by types (`VISUALIZATION`, `SPELL`, `INTERPRETER` and 
`APPLICATION`)
https://cloud.githubusercontent.com/assets/10060731/23219377/3c020fb4-f962-11e6-849c-6da193414d87.png;>


 - Disabled "Enable" button until 
[ZEPPELIN-1993](https://issues.apache.org/jira/browse/ZEPPELIN-1993) is resolved
https://cloud.githubusercontent.com/assets/10060731/23104412/c95dccb2-f710-11e6-9602-4159c7182e64.png;>


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



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

$ git pull https://github.com/AhyoungRyu/zeppelin ZEPPELIN-2109

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

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


commit 6de9169988dae72b084566fef7e401949d5287a4
Author: AhyoungRyu 
Date:   2017-02-19T16:46:05Z

Add img files

commit f1c7bac81e15f8dd577e1e96de698567e004b1f0
Author: AhyoungRyu 
Date:   2017-02-19T16:47:17Z

Add 'INTERPRETER', 'APPLICATION' as helium pkg types

commit 4a6eace7a9a0356b21d93743105cbd3690a65d9e
Author: AhyoungRyu 
Date:   2017-02-19T16:51:00Z

Enable Helium pkg type sortable

commit b74c599178edc28c240ceb3ba9ac7f01b3d2faf1
Author: AhyoungRyu 
Date:   2017-02-19T17:12:16Z

Remove console.log

commit 86e1eda3ef7d1b79d2544864fd568ce22701c697
Author: AhyoungRyu 
Date:   2017-02-19T17:43:54Z

Remove unnecassary words

commit 6d7f4fab5be6dc4b568f238f9403872309386be0
Author: AhyoungRyu 
Date:   2017-02-22T15:37:39Z

Make packages sortable by type not repository

commit c68efd211bd1741c7d2efd1552d41e9164904694
Author: AhyoungRyu 
Date:   2017-02-22T15:45:27Z

Remove unused img files

commit 899e8fa8eba08a293821470a00c582145c64ea36
Author: AhyoungRyu 
Date:

[jira] [Created] (ZEPPELIN-2163) Incorrect doc link in Zeppelin UI

2017-02-23 Thread Yesha Vora (JIRA)

Yesha Vora created ZEPPELIN-2163:


 Summary: Incorrect doc link in Zeppelin UI
 Key: ZEPPELIN-2163
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2163
 Project: Zeppelin
  Issue Type: Bug
Reporter: Yesha Vora


Steps followed:
* Log in to cluster as Ananomous user
* Open a notebook
* Click on Note permission icon on right hand side
It will pop up a message box with "Only authenticated user can set the 
permission.".
* Click on "?" sign after the message. This link redirects to 
"https://zeppelin.apache.org/docs/0.7.0.xx/security/notebook_authorization.html;
This page is not valid.

Zeppelin Documentation link on Home page is also broken. 



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

[GitHub] zeppelin pull request #2004: [MINOR] add pig wiki page to pig doc

2017-02-23 Thread zjffdu

GitHub user zjffdu reopened a pull request:

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

[MINOR] add pig wiki page to pig doc

### What is this PR for?
Add pig wiki page pig doc


### What type of PR is it?
[Documentation |]

### Todos
* [ ] - Task

### What is the Jira issue?
No jira created

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

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

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


commit b8542de569f91d37071ff9db1bc98d66078993cf
Author: Jeff Zhang 
Date:   2017-02-10T08:23:13Z

[MINOR] add pig wiki page to pig doc

commit c6cb5ffa5bcac9b49478efb44f29e99c1782ab58
Author: Jeff Zhang 
Date:   2017-02-24T02:05:09Z

update pig tutorial




---
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] Behaviour of Interpreter when it is restarted

2017-02-23 Thread Jagat Singh

We are implementing the exact same use case today , Trying out central
shared zeppelin 0.7 instance in our organisation.

As member of admin team we have locked down the interpreter page and
published set of settings which we have been configured in the backend.

If Interpreter settings are per user basis then only we will give the
ability to end user to change what he needs , and behaviour you mentioned
about restart affecting only that user job seems a good idea.

One of the issue we are facing is lifecycle of interpreters , zombie
Zeppelin processes which are left on the node where Zeppelin is installed
and on cluster.  How does restart of interpreter by end users and people
from admin team affect those processes ?

Another issue to take care is which of the change will need Zeppelin server
to be restarted as a whole ?

I can write detailed note on issues we are having with running Zeppelin in
enterprise if you are ready to take some feedback in future backlog.

On 22 February 2017 at 19:17, Prabhjyot Singh 
wrote:

> This is WRT the PR that I've created https://github.com/
> apache/zeppelin/pull/2034.
>
> The issue that I want to discuss over here is how should an Interpreter
> behave when it is;
>  - restarted from notebook
>  - restarted from Interpreter setting page
>  - edited from Interpreter setting page
>  - deleted from Interpreter setting page
>
>
> Assuming Zeppelin is being used in Enterprise world, where not all user
> may have access to Zeppelin's Interpreter setting page, say only restricted
> user say "admin-group" have access to this page. Now when a restart, edit
> or delete action is performed from Interpreter setting page; any of this
> operation should terminate all the processes of that particular
> Interpreter. On the other hand if it is restarted from the notebook page by
> any User, then only process of that logged-in User should get affected.
>
> How do you guys think of it?
>
> --
>
> Warm Regards,
>
> Prabhjyot Singh
>

[GitHub] zeppelin issue #2000: [gh-pages] update contribution/webapplication.html

2017-02-23 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

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


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

[GitHub] zeppelin pull request #2004: [MINOR] add pig wiki page to pig doc

2017-02-23 Thread zjffdu

Github user zjffdu closed the pull request at:

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


---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2060
  
Thanks for the contribution.

Please take a look 'Continuous Integration" section 
http://zeppelin.apache.org/contribution/contributions.html#continuous-integration
 .

Once you have setup, make sure you turned on "Build Pushes"


![image](https://cloud.githubusercontent.com/assets/1540981/23286781/2a2f6680-fa7d-11e6-9766-cc34745274f0.png)

Once everything is done, if you push a new commit in this PR then build 
status will be displayed correctly.


---
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-2162) Make travis_check.py print instructions of setting up CI.

2017-02-23 Thread Lee moon soo (JIRA)

Lee moon soo created ZEPPELIN-2162:
--

 Summary: Make travis_check.py print instructions of setting up CI.
 Key: ZEPPELIN-2162
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2162
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee moon soo
Priority: Minor


When contributor didn't set travis-ci, {{travis_check.py}} fails. Although 
contribution guide has some instruction setting up CI, it will be more helpful 
{{travis_check.py}} script prints why it fails and where contributor should go 
to setup the CI.



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

[GitHub] zeppelin issue #1982: [ZEPPELIN-2069] Helium Package Configuration

2017-02-23 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1982
  
Shell we also remove `"version": "local"` from 

zeppelin-examples/zeppelin-example-spell-echo/zeppelin-example-spell-echo.json

zeppelin-examples/zeppelin-example-spell-flowchart/zeppelin-example-spell-flowchart.json

zeppelin-examples/zeppelin-example-spell-markdown/zeppelin-example-spell-markdown.json

zeppelin-examples/zeppelin-example-spell-translator/zeppelin-example-spell-translator.json
?

Otherthan that, 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 #2062: ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

2017-02-23 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2062
  
Thanks @weand for improvmenet.
Have you turn on "Build Pushes" in travis-ci settings?


![image](https://cloud.githubusercontent.com/assets/1540981/23285281/804a474c-fa73-11e6-8f60-8611abbe3326.png)



---
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 #2062: ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

2017-02-23 Thread weand

Github user weand commented on the issue:

https://github.com/apache/zeppelin/pull/2062
  
any idea why the build has failed? I don't get the error.


---
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 #2062: ZEPPELIN-2161 Nested Group Support in LdapRealm...

2017-02-23 Thread weand

GitHub user weand opened a pull request:

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

ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

### What is this PR for?
A common use case in LDAP/AD setup is the hierarchical structuring of
groups - a.k.a. adding groups to other groups. Such nesting groups can
help reduce the number of roles that need to be managed.

Current zeppelin realm implementations doesn't have support for looking
up memberships throughout nested group structures.

E.g. consider the following nested group scenario:
```
acme_employees
 \__department_a
 \__sub_department_x
```
User 'bob' is in Group 'sub_department_x'.
Notebook 'note1' has a Reader Role assignment for 'department_a' or
'acme_employees'.
Then access must be granted for 'bob' on 'note1'.

In AD enviroments this scenarios can be efficiently implemented using
the so called LDAP_MATCHING_RULE_IN_CHAIN operator
'1.2.840.113556.1.4.1941'.

This PR introduces a property 'groupSearchEnableMatchingRuleInChain' to
org.apache.zeppelin.realm.LdapRealm which defaults to false. If enabled,
all roles of potential nested group hierarchies will be resolved using
the LDAP_MATCHING_RULE_IN_CHAIN operator.

### What type of PR is it?
Improvement

### Todos
-

### What is the Jira issue?
[ZEPPELIN-2161]

### How should this be tested?
Set groupSearchEnableMatchingRuleInChain = true for the ldap realm.

### Screenshots (if appropriate)

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

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

$ git pull https://github.com/weand/zeppelin ZEPPELIN-2161

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

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






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

2017-02-23 Thread DmytroShkvyra

Github user DmytroShkvyra closed the pull request at:

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


---
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 #2061: ZEPPELIN-2161 Nested Group Support in LdapRealm...

2017-02-23 Thread weand

Github user weand closed the pull request at:

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


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

2017-02-23 Thread DmytroShkvyra

GitHub user DmytroShkvyra reopened a pull request:

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

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

What is this PR for?

It 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/2032.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 #2032






---
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 #2061: ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

2017-02-23 Thread weand

Github user weand commented on the issue:

https://github.com/apache/zeppelin/pull/2061
  
any idea why the build has failed?


---
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 #2061: ZEPPELIN-2161 Nested Group Support in LdapRealm...

2017-02-23 Thread weand

GitHub user weand opened a pull request:

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

ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

### What is this PR for?
A common use case in LDAP/AD setup is the hierarchical structuring of
groups - a.k.a. adding groups to other groups. Such nesting groups can
help reduce the number of roles that need to be managed.

Current zeppelin realm implementations doesn't have support for looking
up memberships throughout nested group structures.

E.g. consider the following nested group scenario:
```
acme_employees
 \__department_a
 \__sub_department_x
```
User 'bob' is in Group 'sub_department_x'.
Notebook 'note1' has a Reader Role assignment for 'department_a' or
'acme_employees'.
Then access must be granted for 'bob' on 'note1'.

In AD enviroments this scenarios can be efficiently implemented using
the so called LDAP_MATCHING_RULE_IN_CHAIN operator
'1.2.840.113556.1.4.1941'.

This PR introduces a property 'groupSearchEnableMatchingRuleInChain' to
org.apache.zeppelin.realm.LdapRealm which defaults to false. If enabled,
all roles of potential nested group hierarchies will be resolved using
the LDAP_MATCHING_RULE_IN_CHAIN operator.

### What type of PR is it?
Improvement

### Todos
-

### What is the Jira issue?
[ZEPPELIN-2161]

### How should this be tested?
Set groupSearchEnableMatchingRuleInChain = true for the ldap realm.

### Screenshots (if appropriate)

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

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

$ git pull https://github.com/weand/zeppelin master

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

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


commit f312f1134d40c7f9a28a1235c952bd85393bbb76
Author: Andreas Weise 
Date:   2017-02-23T21:55:06Z

ZEPPELIN-2161 Nested Group Support in LdapRealm for AD

### What is this PR for?
A common use case in LDAP/AD setup is the hierarchical structuring of
groups - a.k.a. adding groups to other groups. Such nesting groups can
help reduce the number of roles that need to be managed.
Current zeppelin realm implementations doesn't have support for looking
up memberships throughout nested group structures.
E.g. consider the following nested group scenario:
acme_employees
 \__department_a
 \__sub_department_x
User 'bob' is in Group 'sub_department_x'.
Notebook 'note1' has a Reader Role assignment for 'department_a' or
'acme_employees'.
Then access must be granted for 'bob' on 'note1'.
In AD enviroments this scenarios can be efficiently implemented using
the so called LDAP_MATCHING_RULE_IN_CHAIN operator
'1.2.840.113556.1.4.1941'.

This PR introduces a property 'groupSearchEnableMatchingRuleInChain' to
org.apache.zeppelin.realm.LdapRealm which defaults to false. If enabled,
all roles of potential nested group hierarchies will be resolved using
the LDAP_MATCHING_RULE_IN_CHAIN operator.

### What type of PR is it?
Improvement

### Todos
-

### What is the Jira issue?
[ZEPPELIN-2161]

### How should this be tested?
Set groupSearchEnableMatchingRuleInChain = true for the ldap realm.

### Screenshots (if appropriate)

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




---
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-2161) Nested Group Support in LdapRealm for AD using LDAP_MATCHING_RULE_IN_CHAIN Operator

2017-02-23 Thread Andreas Weise (JIRA)

Andreas Weise created ZEPPELIN-2161:
---

 Summary: Nested Group Support in LdapRealm for AD using 
LDAP_MATCHING_RULE_IN_CHAIN Operator
 Key: ZEPPELIN-2161
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2161
 Project: Zeppelin
  Issue Type: Improvement
  Components: zeppelin-server
Affects Versions: 0.7.0
Reporter: Andreas Weise


A common use case in LDAP/AD setup is the hierarchical structuring of groups - 
a.k.a. adding groups to other groups. Such nesting groups can help reduce the 
number of roles that need to be managed.

Current zeppelin realm implementations doesn't have support for looking up 
memberships throughout nested group structures.

E.g. consider the following nested group scenario:
{noformat}
acme_employees
 \__department_a
 \__sub_department_x
{noformat}
User 'bob' is in Group 'sub_department_x'.

Notebook 'note1' has a Reader Role assignment for 'department_a' or 
'acme_employees'.

Then access must be granted for 'bob' on 'note1'.

In AD enviroments this scenarios can be efficiently implemented using the so 
called LDAP_MATCHING_RULE_IN_CHAIN operator '1.2.840.113556.1.4.1941'.



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

[GitHub] zeppelin issue #2032: [ZEPPELIN-791] Build infra: move all RAT to root pom.x...

2017-02-23 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2032
  
Sorry, it is hard that way. You could try again by closing and re-opening 
this PR...


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

[GitHub] zeppelin pull request #2050: ZEPPELIN-2137 Changed "show line chart with foc...

2017-02-23 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #2058: [ZEPPELIN-2147] zeppelin should redirect to login page...

2017-02-23 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/2058
  
Thank you @khalidhuseynov  for taking a look at this. CI is green now.


---
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 #2060: [ZEPPELIN-2094] Decrease npm install retry time

2017-02-23 Thread NohSeho

GitHub user NohSeho opened a pull request:

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

[ZEPPELIN-2094] Decrease npm install retry time

### What is this PR for?
Itâs too delayed for npm install when computer do not connected any 
networks.
Beacause when npm install, it has too long retry timeout.
This PR is to decrease retry timeout when npm install.


### What type of PR is it?
Improvement

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

### How should this be tested?
Line 197 In zeppelin-zengine 
org.apache.zeppelin.helium.HeliumBundleFactory.java

First set with 
`String npmCommand = "install âloglevel=errorâ;`
and You donât connect any ethernet or wireless internet.
build & run

and set with
`String npmCommand = "install âfetch-retries=2 âfetch-retry-factor=1 
âfetch-retry-mintimeout=5000 âloglevel=errorâ;`
also donât connect any networks, build & run.

WHY
retries = 2
factor = 1
mintimeout = 5(sec)?

npm use [retry](https://github.com/tim-kos/node-retry) module to retry.
It refers [this 
article](http://dthain.blogspot.kr/2009/02/exponential-backoff-in-distributed.html)
 for retry algorithms.
It is a math which structured _Math.min(Math.round(random * minTimeout * 
Math.pow(factor, attempt)), maxTimeout)_.

So before, zeppelin use npm's default setting
random = False = 1
retry = 2
minTimeout = 10(sec)
maxTimeout = 60(sec)
factor = 10

First retry
_Math.min(1 * 10(sec) * Math.pow(10, 1), 60(sec))_
then, _Math.min(10(sec) * 10^1, 60(sec))_ -> _Math.min(100(sec), 60(sec))_ 
= _100sec_ wating for first retry

and Second
_Math.min(1 * 10(sec) * Math.pow(10, 2), 60(sec))_
then, _Math.min(10(sec) * 10^2, 60(sec))_ -> _Math.min(10(sec) * 100, 
60(sec))_ -> _Math.min(1000(sec), 60(sec))_ = _60sec_ wating for second retry

approximately 160sec, 2min 40sec wating for two times retries.

But it's too long to run server when no networks.

So decrease like that you see above.

First retry
_Math.min(1 * 5(sec) * Math.pow(1, 1), 60(sec))_
then, _Math.min(5(sec) * 1^1, 60(sec))_ -> _Math.min(5(sec), 60(sec)_ = 
_5sec_ wating for first retry

and Second
_Math.min(1 * 5(sec) * Math.pow(1, 2), 60(sec))_
then, _Math.min(5(sec) * 1^2, 60(sec))_ -> _Math.min(5(sec), 60(sec)_ = 
_5sec_ wating for second retry

approximately 10sec waiting for two times retries.

You can check like this below Screenshots.

### Screenshots
https://cloud.githubusercontent.com/assets/1144643/23267951/9deaec6e-fa2f-11e6-9171-5792f24de76d.png;>
https://cloud.githubusercontent.com/assets/1144643/23267954/a12c0c0a-fa2f-11e6-99cd-335deef607ac.png;>


### 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/NohSeho/zeppelin ZEPPELIN-2094

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

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


commit b3fe1886df3d8d64c4aced5672d0f98bb5ad4241
Author: NohSeho 
Date:   2017-02-23T15:59:57Z

[ZEPPELIN-2094] Decrease npm install retry time




---
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-2160) PySpark: Matplotlib Integration extremely slow

2017-02-23 Thread Bernhard Walter (JIRA)

Bernhard Walter created ZEPPELIN-2160:
-

 Summary: PySpark: Matplotlib Integration extremely slow
 Key: ZEPPELIN-2160
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2160
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end, GUI
Affects Versions: 0.7.0
Reporter: Bernhard Walter


*Issue:*
I tested matplotlib integration in Pyspark. As a baseline, the following 3 
examples took at 1 - 2 seconds in Jupyter on the same machine.

{code}
%pyspark

import matplotlib.pyplot as plt
plt.plot([1,2,3,4])
plt.ylabel('some numbers')
z.show(plt)
{code}

==> 1 sec

{code}
%pyspark

import numpy as np
import matplotlib.pyplot as plt

# Fixing random state for reproducibility
np.random.seed(19680801)

mu, sigma = 100, 15
x = mu + sigma * np.random.randn(1)

# the histogram of the data
n, bins, patches = plt.hist(x, 50, normed=1, facecolor='g', alpha=0.75)

plt.xlabel('Smarts')
plt.ylabel('Probability')
plt.title('Histogram of IQ')
plt.text(60, .025, r'$\mu=100,\ \sigma=15$')
plt.axis([40, 160, 0, 0.03])
plt.grid(True)
plt.show()
{code}

==> 11 sec

{code}
%pyspark
from ggplot import *

ggplot(diamonds, aes(x='price', fill='cut')) +\
geom_density(alpha=0.25) +\
facet_wrap("clarity")
{code}

==> 138 sec

*Environment:*
Downloaded 
http://apache.mirror.digionline.de/zeppelin/zeppelin-0.7.0/zeppelin-0.7.0-bin-netinst.tgz
 and installed spark, python, sh, md and angular interpreter
Started via bin/zeppelin.sh



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

[jira] [Created] (ZEPPELIN-2158) PySpark: Error trace appears when assigning a value to variable "z"

2017-02-23 Thread Bernhard Walter (JIRA)

Bernhard Walter created ZEPPELIN-2158:
-

 Summary: PySpark: Error trace appears when assigning a value to 
variable "z"
 Key: ZEPPELIN-2158
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2158
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end, GUI
Affects Versions: 0.7.0
Reporter: Bernhard Walter


*Issue:*

Variable "z" seems to be bound to the ZeppelinContext
Now "z" can be assigned with any value, e.g.

{code}
%pyspark
z=[]
{code}

This leads to 
{code}
Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 344, in 
exec(code)
  File "", line 3, in 
AttributeError: 'list' object has no attribute '_displayhook'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 346, in 
raise Exception(traceback.format_exc())
Exception: Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 344, in 
exec(code)
  File "", line 3, in 
AttributeError: 'list' object has no attribute '_displayhook'
{code}

in every cell that is executed later on.

Since z is a very common variable in math and statistics science, it should not 
be used for ZeppelinContext.
Propsal (use double underscore like in python for private stuff):
{code}
__z
{code}
or better
{code}
__zeppelinContext
{code}

*Environment:*

Downloaded 
http://apache.mirror.digionline.de/zeppelin/zeppelin-0.7.0/zeppelin-0.7.0-bin-netinst.tgz
 and installed spark, python, sh, md and angular interpreter

Started via bin/zeppelin.sh




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

[jira] [Created] (ZEPPELIN-2159) PySpark: Error trace appears when assigning a value to variable "z"

2017-02-23 Thread Bernhard Walter (JIRA)

Bernhard Walter created ZEPPELIN-2159:
-

 Summary: PySpark: Error trace appears when assigning a value to 
variable "z"
 Key: ZEPPELIN-2159
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2159
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end, GUI
Affects Versions: 0.7.0
Reporter: Bernhard Walter


*Issue:*

Variable "z" seems to be bound to the ZeppelinContext
Now "z" can be assigned with any value, e.g.

{code}
%pyspark
z=[]
{code}

This leads to 
{code}
Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 344, in 
exec(code)
  File "", line 3, in 
AttributeError: 'list' object has no attribute '_displayhook'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 346, in 
raise Exception(traceback.format_exc())
Exception: Traceback (most recent call last):
  File 
"/var/folders/sf/prpc_v7d1vbdjz61kshfh9x0gp/T/zeppelin_pyspark-6677949145168225238.py",
 line 344, in 
exec(code)
  File "", line 3, in 
AttributeError: 'list' object has no attribute '_displayhook'
{code}

in every cell that is executed later on.

Since z is a very common variable in math and statistics science, it should not 
be used for ZeppelinContext.
Propsal (use double underscore like in python for private stuff):
{code}
__z
{code}
or better
{code}
__zeppelinContext
{code}

*Environment:*

Downloaded 
http://apache.mirror.digionline.de/zeppelin/zeppelin-0.7.0/zeppelin-0.7.0-bin-netinst.tgz
 and installed spark, python, sh, md and angular interpreter

Started via bin/zeppelin.sh




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

[GitHub] zeppelin issue #2042: [ZEPPELIN-1588]: bumping nvd3 to 1.8.5

2017-02-23 Thread AhyoungRyu

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2042
  
@Remilito I see. Thanks for explanation. It's okay, wasn't strong opinion. 
Looks good as is :)


---
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-2157) Helium should bundle only requires zeppelin-related packages in node_modules

2017-02-23 Thread Hoon Park (JIRA)

Hoon Park created ZEPPELIN-2157:
---

 Summary: Helium should bundle only requires zeppelin-related 
packages in node_modules
 Key: ZEPPELIN-2157
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2157
 Project: Zeppelin
  Issue Type: Bug
  Components: helium
Affects Versions: 0.7.1, 0.8.0
Reporter: Hoon Park
 Fix For: 0.7.1, 0.8.0


Helium should bundle only requires zeppelin-related packages in node_modules.

Currently, we are babelifying all packages in node_modules. This will increase 
total bundle time significantly.

{code}
// zengine/src/main/resources/helium/webpack.config.json

module: {
loaders: [{
test: /\.js$/,
//exclude: /node_modules/,
loader: 'babel-loader'
}]
}
{code}



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

[GitHub] zeppelin issue #2032: [ZEPPELIN-791] Build infra: move all RAT to root pom.x...

2017-02-23 Thread DmytroShkvyra

Github user DmytroShkvyra commented on the issue:

https://github.com/apache/zeppelin/pull/2032
  
Failed tests: 
  NotebookTest.testPublicPrivateNewNote:1173 expected:<2C9[FXZKX8]> but 
was:<2C9[4VAUTF]>
  NotebookTest.testAuthorizationRoles:759 expected: but was:
@jongyoul , @felixcheung  Thanks for review! I have resolved conflict but 
third party tests have been failed. It's pity that so simple PR couldn't be 
merged to master. Fix of these tests out of scope PR.


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

[jira] [Created] (ZEPPELIN-2156) Paragraph with PySpark streaming - running job cannot be canceled

2017-02-23 Thread Piotr Nestorow (JIRA)

Piotr Nestorow created ZEPPELIN-2156:


 Summary: Paragraph with PySpark streaming - running job cannot be 
canceled
 Key: ZEPPELIN-2156
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2156
 Project: Zeppelin
  Issue Type: Bug
  Components: pySpark
Affects Versions: 0.7.0
 Environment: Linux Ubuntu
Reporter: Piotr Nestorow


In a  'spark.pyspark' paragraph a StreamingContext to a Kafka stream is 
created. 

The paragraph is started and while the job is running the spark context 
produces correct output from the code.

The problem is the job cannot be stopped in the Zeppelin web interface.

Installed Kafka version: kafka_2.11-0.8.2.2
Spark Kafka jar: spark-streaming-kafka-0-8_2.11-2.1.0.jar
Zeppelin: zeppelin-0.7.0-bin-all

Tried:
1. Paragraph Cancel ( || button ) has no effect.

2. Zeppelin Job view Stop All has no effect

3. Another paragraph with 
%spark.pyspark
ssc.stop(stopSparkContext=false, stopGracefully=true)

is started by stays in 'Pending'

4. Restarting the 'spark' interpreter stops the job


The example logic:

%spark.pyspark
import sys
import json

from pyspark import SparkContext
from pyspark.streaming import StreamingContext(II())
from pyspark.streaming.kafka import KafkaUtils

zkQuorum, topic, interval = ('localhost:2181', 'airport', 60)

ssc = StreamingContext(sc, interval)

kvs = KafkaUtils.createStream(ssc, zkQuorum, "spark-streaming-consumer", 
{topic: 1})

parsed = kvs.map(lambda (k, v): json.loads(v))
summed = parsed.\
filter(lambda event: 'kind' in event and 
event['kind']=='gate').\
map(lambda event: ('count_all', 
int(event['value']['passengers']))).\
reduceByKey(lambda x,y: x + y).\
map(lambda x: {'sum': x[0], "passengers": x[1]})
summed.pprint()

ssc.start()
ssc.awaitTermination()



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

[GitHub] zeppelin issue #2058: [ZEPPELIN-2147] zeppelin should redirect to login page...

2017-02-23 Thread khalidhuseynov

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2058
  
changes look good, may need to check the CI though


---
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 #2042: [ZEPPELIN-1588]: bumping nvd3 to 1.8.5

2017-02-23 Thread Remilito

Github user Remilito commented on the issue:

https://github.com/apache/zeppelin/pull/2042
  
@AhyoungRyu : I have just checked, those "axis-boxes" seemed to have 
disappeared from nvd3 after 1.7.1. However the new tooltip provides both x and 
y values. WDYT?


---
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 #2059: [ZEPPELIN-2139] Interpreters based on scala_2.1...

2017-02-23 Thread minahlee

GitHub user minahlee opened a pull request:

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

[ZEPPELIN-2139] Interpreters based on scala_2.11 aren't installed correctly

### What is this PR for?
pom variables such as `${scala.version}` are not replaced to value when you 
do mvn install.
This causes leaf poms to look for this value in parent pom, which is always 
`2.10.5` and bring scala library dependency conflict. For example, 
zeppelin-flink_2.11 will have scala 2.10.5 as dependency.
This PR fixes this problem by using maven flatten plugin.

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

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

### How should this be tested?
```
$ ./dev/change_scala_version.sh 2.11
$ mvn clean install -pl 
'zeppelin-server,zeppelin-zengine,zeppelin-interpreter,flink' -am -DskipRat 
-DskipTests -Pscala-2.11
```
Open 
`~/.m2/repository/org/apache/zeppelin/zeppelin-flink_2.11/0.8.0-SNAPSHOT/zeppelin-flink_2.11-0.8.0-SNAPSHOT.pom`
 file and see if scala related libraries dependency version is set to 2.11.7

### 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/minahlee/zeppelin ZEPPELIN-2139

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

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


commit 301a555b23472b8a9abf8c34c33b05c1190c3b49
Author: Mina Lee 
Date:   2017-02-23T05:59:52Z

Fix indentation and add default properties to be used in flattened-pom

commit 0acdec0189ac8f1b18e66cd22000c1fdaafde905
Author: Mina Lee 
Date:   2017-02-23T07:32:41Z

Use maven flatten plugin to make pom.xml variables to be replaced by value

commit 38bad9b5134f34d825d080266d2135b13ecdc978
Author: Mina Lee 
Date:   2017-02-23T09:21:35Z

Change  property in parent pom file




---
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 #2058: [ZEPPELIN-2147] zeppelin should redirect to log...

2017-02-23 Thread prabhjyotsingh

GitHub user prabhjyotsingh opened a pull request:

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

[ZEPPELIN-2147] zeppelin should redirect to login page after browser 
session expires

### What is this PR for?
Zeppelin should redirect to login page after browser session expires

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

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

### How should this be tested?
 - Open any Zeppelin's notebook on a browser
 - Restart zeppelin server
 - now as soon as next web-socket message or API request is sent to server 
that returns either "ticket is invalid" or 405. This should get redirected to 
login page.
 - On successful login it should take user back to the page from where he 
was coming from.

### Screenshots (if appropriate)

![zeppelin-2147](https://cloud.githubusercontent.com/assets/674497/23250873/ec27b6e6-f9d0-11e6-8e6f-75e97f2449b1.gif)



### 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 ZEPPELIN-2147

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

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


commit 6486383c0816f033feb0803b3de98f94db6739ab
Author: Prabhjyot Singh 
Date:   2017-02-23T08:13:18Z

in case of session lost or logout, show login window




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

54 matches

Mail list logo