[GitHub] zeppelin issue #3007: zeppelin 0.8 version pyspark interpreter error when us...

2018-06-05 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/3007
  
What protobuf version do you use ? I think it is due to mismatch between 
protobuf and grpc 


---


[GitHub] zeppelin issue #3005: [ZEPPELIN-3528] Ordering by interpreter name in same i...

2018-06-05 Thread zjffdu
Github user zjffdu commented on the issue:

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


---


[GitHub] zeppelin pull request #3008: ZEPPELIN-3531. Don't look for py4j in NewSparkI...

2018-06-05 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

ZEPPELIN-3531. Don't look for py4j in NewSparkInterpreter

### What is this PR for?
Just remove setupConfForPySpark in NewSparkInterpreter as it is not 
necessary and will cause NPE when the node launch spark interpreter doesn't 
have spark installed in yarn cluster mode.


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

### Todos
* [ ] - Task

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

### How should this be tested?
* CI pass & Manually tested in a 3 node cluster


### Screenshots (if appropriate)

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


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

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

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

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


commit d3fa2d2e2808090032678b0baddb2281ce81f582
Author: Jeff Zhang 
Date:   2018-06-05T13:38:17Z

ZEPPELIN-3531. Don't look for py4j in NewSparkInterpreter




---


[jira] [Created] (ZEPPELIN-3531) Don't look for py4j in NewSparkInterpreter

2018-06-05 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-3531:


 Summary: Don't look for py4j in NewSparkInterpreter
 Key: ZEPPELIN-3531
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3531
 Project: Zeppelin
  Issue Type: Bug
Reporter: Jeff Zhang


py4j will be setup in SparkInterpreterLauncher, it is not necessary to do that 
in NewSparkInterpreter. It will cause NPE sometimes when the node launch spark 
interpreter doesn't have spark installed. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] zeppelin issue #2952: [Zeppelin-2572] multiple paragraphs actions

2018-06-05 Thread Tagar
Github user Tagar commented on the issue:

https://github.com/apache/zeppelin/pull/2952
  
We were using PR this in prod for a couple of weeks. Works great. 
Left one additional comment based on users feedback. 
"Select a paragraph" tooltip change to "Add this paragraph to selection" 
would be better,
as it selects that particular paragraph and based on tooltip users can see 
that it talks
about multi-paragraph selection.



---


[GitHub] zeppelin pull request #3007: change python project grpc version to 1.10.0

2018-06-05 Thread lizhenhuan
GitHub user lizhenhuan opened a pull request:

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

change python project grpc version to 1.10.0

### What is this PR for?
zeppelin 0.8 version pyspark interpreter error when using ipython


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



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

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

https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/interpreter/python.html#ipython-support
install ipython 
should also install protobuf


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

$ git pull https://github.com/lizhenhuan/zeppelin pyspark-grpc-version

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

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


commit fd00dd7fb99b7484dacb378a26cb672ae1e5120d
Author: lizhenhuan 
Date:   2018-06-05T13:34:39Z

change python project grpc version to 1.10.0




---


[jira] [Created] (ZEPPELIN-3530) pyspark interpreter error when using ipython

2018-06-05 Thread zhenhuanli708 (JIRA)
zhenhuanli708 created ZEPPELIN-3530:
---

 Summary: pyspark interpreter error when using ipython
 Key: ZEPPELIN-3530
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3530
 Project: Zeppelin
  Issue Type: Bug
  Components: pySpark
Affects Versions: 0.8.1
Reporter: zhenhuanli708
 Fix For: 0.8.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] zeppelin pull request #3006: Modify jobGroupId for checking user

2018-06-05 Thread woowahan-jaehoon
GitHub user woowahan-jaehoon opened a pull request:

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

Modify jobGroupId for checking user

### What is this PR for?
Need to check user in jobGroupId
because when some paragraph is running,
who run paragraph cannot be found in spark application web UI.

I replace `zeppelin-` to userId.
I think that 'zeppelin-' is needless because it is already known in spark 
application.

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

### Todos
* [x] - Modify Code

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

### How should this be tested?
* Check jobGroupId in Spark Application Web UI of Zeppelin Spark Interpreter

### 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/woowabros/zeppelin ZEPPELIN-3529

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

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


commit c467599e93001e7aab77bb6f93f71ec477f22b49
Author: Jaehoon Jeong 
Date:   2018-06-05T12:02:16Z

[ZEPPELIN-3529] Modify jobGroupId for checking user




---


[jira] [Created] (ZEPPELIN-3529) Need to check user in jobGroupId

2018-06-05 Thread Jaehoon Jeong (JIRA)
Jaehoon Jeong created ZEPPELIN-3529:
---

 Summary: Need to check user in jobGroupId
 Key: ZEPPELIN-3529
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3529
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Jaehoon Jeong


Need to check user in jobGroupId
because when some paragraph is running,
who run paragraph cannot be found in spark application web UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] zeppelin pull request #3005: [ZEPPELIN-3528] Ordering by interpreter name in...

2018-06-05 Thread woowahan-jaehoon
GitHub user woowahan-jaehoon opened a pull request:

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

[ZEPPELIN-3528] Ordering by interpreter name in same interpreter group

### What is this PR for?
In 'Create new note' diagram, 'Default Interpreter' is ordered by only 
interpreter groups.

But interpreter is not ordered in same interpreter group.
(It seems to ordered by hashcode of 'InterpreterSetting')

When there are many interpreter in same group and this group is first,
user cannot predict what interpreter is showed first.

So I think that interpreter need to be ordered by name.


### What type of PR is it?
Improvement

### Todos
* [v] - Modify Code

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

### How should this be tested?
* Click 'create new note'

### 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/woowabros/zeppelin ZEPPELIN-3528

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

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


commit 5f74d3a8011ec0b31885938651fe42d50d51e464
Author: Jaehoon Jeong 
Date:   2018-06-05T11:39:55Z

[ZEPPELIN-3528] Ordering by interpreter name in same interpreter group




---


[jira] [Created] (ZEPPELIN-3528) Need ordering interpreter name in same group

2018-06-05 Thread Jaehoon Jeong (JIRA)
Jaehoon Jeong created ZEPPELIN-3528:
---

 Summary: Need ordering interpreter name in same group
 Key: ZEPPELIN-3528
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3528
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Jaehoon Jeong


In 'Create new note' diagram, 'Default Interpreter' is ordered by only 
interpreter groups.

But interpreter is not ordered in same interpreter group.
(It seems to ordered by hashcode of 'InterpreterSetting')

When there are many interpreter in same group and this group is first,
user cannot predict what interpreter is showed first.

So I think that interpreter need to be ordered by name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


RE: zeppelin start is failing on zeppelin v0.8.0-rc2

2018-06-05 Thread Panchappanavar, Naveenakumar Gurushantap (Nokia - IN/Bangalore)
Hi Zhang,

We took the source code from the given link and built the same.

Its working properly, zeppelin server is able to start without any issues.

Thanks again for all your help and sharing the information.

Regards
Naveen

-Original Message-
From: Jeff Zhang [mailto:zjf...@gmail.com] 
Sent: Thursday, May 17, 2018 7:14 PM
To: dev@zeppelin.apache.org
Subject: Re: zeppelin start is failing on zeppelin v0.8.0-rc2

This is because there's no .git folder in this tar file. You can use the
rc2 source code in
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc2/


Panchappanavar, Naveenakumar Gurushantap (Nokia - IN/Bangalore) <
naveenakumar_gurushantap.panchappana...@nokia.com>于2018年5月17日周四 下午8:47写道:

> The mvn command used to build the source code is
>
> mvn clean install -DskipTests -Drat.skip=true -Pspark-2.2 -Phadoop2
> -Pscala-2.11
>
> we will try with without profiles and get back.
>
> Regards
> Naveen
>
>
> From: Panchappanavar, Naveenakumar Gurushantap (Nokia - IN/Bangalore)
> Sent: Thursday, May 17, 2018 6:13 PM
> To: dev@zeppelin.apache.org
> Subject: zeppelin start is failing on zeppelin v0.8.0-rc2
>
> Hi All,
>
> We have cloned the source code
> https://github.com/apache/zeppelin/archive/v0.8.0-rc2.tar.gz from this 
> uri built the source code after generating zeppelin tar ball.
>
> When we are issuing the command to start zeppelin server 
> bin/zeppelin.sh start
>
> We are getting the following exception while starting the zeppelin 
> server itself.
>
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/opt/zeppelin0.8/zeppelin-0.8.0/lib/interpreter/slf4j-log4j1
> 2-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/opt/zeppelin0.8/zeppelin-0.8.0/lib/slf4j-log4j12-1.7.10.jar
> !/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at
> org.apache.zeppelin.conf.ZeppelinConfiguration.create(ZeppelinConfiguration.java:136)
>   at
> org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:169
> ) Caused by: java.lang.NullPointerException
>   at
> java.util.Properties$LineReader.readLine(Properties.java:434)
>   at java.util.Properties.load0(Properties.java:353)
>   at java.util.Properties.load(Properties.java:341)
>   at org.apache.zeppelin.util.Util.(Util.java:41)
>   ... 2 more
>
>
> We set the spark home in zeppelin-env.sh as well.
>
> Regards
> Naveen
>
>


[GitHub] zeppelin pull request #2996: ZEPPELIN-3521 Dynamic note form overlaps with p...

2018-06-05 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] zeppelin issue #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or pass...

2018-06-05 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/3003
  
@mebelousov sure I've added a doc.


---


[GitHub] zeppelin issue #3004: [ZEPPELIN-2913] Support for both user and role for Aut...

2018-06-05 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/3004
  
@zjffdu @VipinRathor  can you help review this PR


---


[GitHub] zeppelin pull request #3004: [ZEPPELIN-2913] Support for both user and role ...

2018-06-05 Thread prabhjyotsingh
GitHub user prabhjyotsingh opened a pull request:

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

[ZEPPELIN-2913] Support for both user and role for AuthorizationFilter

### What is this PR for?
Currently, Zeppelin only supports roles for AuthorizationFilter, but there 
can be a condition as described in 
https://issues.apache.org/jira/browse/ZEPPELIN-2913 where Zeppelin's user does 
not belong to a group/role, and the administrator wants to have control using 
user only.

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

### Todos
* [ ] - Add documentation

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

### How should this be tested?
add the following in shiro.ini:
```
[main]
...
anyofroles = org.apache.zeppelin.utils.AnyOfRolesUserAuthorizationFilter

[urls]
...
/api/interpreter/** = authc, anyofroles[admin, user1]
/api/configurations/** = authc, roles[admin]
/api/credential/** = authc, roles[admin]
```
With the above config both user (user1) and users the belong to role admin 
will have access to interpreter setting page.


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

$ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-2913

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

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


commit 53c0c034a3e76467929091442a8a9c8b3c9839cf
Author: Prabhjyot Singh 
Date:   2018-06-05T08:14:33Z

[ZEPPELIN-2913] support for both user and role

Change-Id: I5a83e5701d22ac40b37cc8c3d4c9414ef007b99c




---


[GitHub] zeppelin issue #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or pass...

2018-06-05 Thread mebelousov
Github user mebelousov commented on the issue:

https://github.com/apache/zeppelin/pull/3003
  
@prabhjyotsingh I think it's good to document only one way for 
authentification. What do you think about it?


---


[GitHub] zeppelin issue #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or pass...

2018-06-05 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/3003
  
Agreed we should definitely do something like zeppelin-plugins for 
authentication components as well in Zeppelin-0.9


---


[GitHub] zeppelin issue #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or pass...

2018-06-05 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/3003
  
LGTM, one suggestion is that I think it is time for us to do refactoring 
for the authentication component, we should put it in one component and provide 
interface to be used by other components. Instead of putting logic in zeppelin 
server like this PR. 


---


[GitHub] zeppelin issue #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or pass...

2018-06-05 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/3003
  
@Leemoonsoo @felixcheung @zjffdu  can you help review this.


---


[GitHub] zeppelin pull request #3003: [ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP ...

2018-06-05 Thread prabhjyotsingh
GitHub user prabhjyotsingh opened a pull request:

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

[ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or password based) should be 
mutually exclusive

### What is this PR for?
Problem:
When any external authentication (like LDAP/AD) is enabled for Zeppelin, 
the default password-based authentication could still be configured in addition 
to that. This makes space for backdoor in Zeppelin where the user can still get 
in using the local username/password.

Proposed Solution:
Zeppelin shouldn't allow specifying [users] section in shiro.ini when it is 
configured to authenticate with LDAP/AD.


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

### Todos
* [ ] - Add documentation 

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

### How should this be tested?
If both [users] and [main] for example activeDirectoryRealm section enabled 
in shiro, Zeppelin server should not start.


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

$ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-3526

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

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


commit 529ab3e0e4297f413a0095e4dd19e7e11ce32493
Author: Prabhjyot Singh 
Date:   2018-06-05T06:31:25Z

ZEPPELIN-3526: Zeppelin auth mechanisms (LDAP or password based) should be 
mutually exclusive

Change-Id: I9e0602c41462997c14a2dbb7378489ffab3ca0b4




---


[jira] [Created] (ZEPPELIN-3527) Upgrade log4j to log4j2

2018-06-05 Thread Thomas Decaux (JIRA)
Thomas Decaux created ZEPPELIN-3527:
---

 Summary: Upgrade log4j to log4j2
 Key: ZEPPELIN-3527
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3527
 Project: Zeppelin
  Issue Type: Wish
  Components: Core
Reporter: Thomas Decaux


According 
[https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces]
 , log4j is more than deprecated now.

According [https://blogs.apache.org/logging/entry/moving_on_to_log4j_2,] log4j 
has some issues with Java 9.

Should we move to log4j2 ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)