[jira] [Created] (ZEPPELIN-2174) Spark UI link for spark interpreter falsely notify that spark app not running even when app is running

2017-02-24 Thread Yesha Vora (JIRA)
Yesha Vora created ZEPPELIN-2174:


 Summary: Spark UI link for spark interpreter falsely notify that 
spark app not running even when app is running
 Key: ZEPPELIN-2174
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2174
 Project: Zeppelin
  Issue Type: Bug
Reporter: Yesha Vora


Scenario:
* Running few notebooks with spark and spark2 interpreter.
* Zeppelin started 2 applications ( application_1487349092366_0025 and 
application_1487349092366_0026)
* Go to interpreter setting page.
* Click on spark_ui button.
when this button was clicked , it redirected to 
http://xxx:8088/proxy/redirect/application_1487349092366_0025/.

After some time, when I clicked again on same link, It complained that "No 
Spark application running" even though application_1487349092366_0025 and 
application_1487349092366_0026 were running.



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


[jira] [Created] (ZEPPELIN-2173) Zeppelin UI: Duplicate user names populated in the Note permission box

2017-02-24 Thread Namit Maheshwari (JIRA)
Namit Maheshwari created ZEPPELIN-2173:
--

 Summary: Zeppelin UI: Duplicate user names populated in the Note 
permission box
 Key: ZEPPELIN-2173
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2173
 Project: Zeppelin
  Issue Type: Bug
Reporter: Namit Maheshwari


Steps:
Steps:
1. Try to edit note permissions by a user who is not the owner
2. Click Save button
3. It shows the correct message
{code}
Insufficient privileges to change permissions.

Allowed owners: [hrt_qa]

User belongs to: [hrt_1]
{code}

4. Click Cancel button
5. See duplicate user names populated in the Note Permissions boxes





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


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

2017-02-24 Thread 1ambda
Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2060
  
Thanks for improvement! I will review and comment soon.


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


[jira] [Created] (ZEPPELIN-2171) Connection refused

2017-02-24 Thread Matthew Mc Colgan (JIRA)
Matthew Mc Colgan created ZEPPELIN-2171:
---

 Summary: Connection refused 
 Key: ZEPPELIN-2171
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2171
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.7.0
Reporter: Matthew Mc Colgan


My apologies, in advance, if this seems trivial. I'm a student trying to run 
zeppelin for a project. First time posting so not sure if done correctly. 

I'm trying to run Zeppelin on my local machine on windows 10. Master is set to 
local[*], I've altered the zeppelin-env.sh file and the zeppelin-site.xml files 
to export my JAVA_HOME, SPARK_HOME and also changed the port to 8090. The error 
i receive is:
java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at 
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.thrift.transport.TSocket.open(TSocket.java:182)
at 
org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:51)
at 
org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:37)
at 
org.apache.commons.pool2.BasePooledObjectFactory.makeObject(BasePooledObjectFactory.java:60)
at 
org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:861)
at 
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
at 
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.getClient(RemoteInterpreterProcess.java:90)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:209)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:375)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:105)
at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:365)
at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:329)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)  

The logs do not save into the log file but get printed in the command prompt. 
The logs are: 

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd C:\zeppelin-0.7.0-bin-all\bin

C:\zeppelin-0.7.0-bin-all\bin>zeppelin.cmd
Java HotSpot(TM) 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:/C:/zeppelin-0.7.0-bin-all/lib/interpreter/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/C:/zeppelin-0.7.0-bin-all/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]
 INFO [2017-02-24 13:35:49,259] ({main} ZeppelinConfiguration.java[create]:101) 
- Load configuration from file:/C:/zeppelin-0.7.0-bin-all/conf/zeppelin-site.xml
 INFO [2017-02-24 13:35:49,349] ({main} ZeppelinConfiguration.java[create]:109) 
- Server Host: 0.0.0.0
 INFO [2017-02-24 13:35:49,349] ({main} ZeppelinConfiguration.java[create]:111) 
- Server Port: 8090
 INFO [2017-02-24 13:35:49,349] ({main} ZeppelinConfiguration.java[create]:115) 
- Context Path: /
 INFO [2017-02-24 13:35:49,354] ({main} ZeppelinConfiguration.java[create]:116) 
- Zeppelin Version: 0.7.0
 INFO [2017-02-24 13:35:49,386] ({main} Log.java[initialized]:186) - Logging 

[jira] [Created] (ZEPPELIN-2170) Zeppelin does not show all WARN messages thrown by spark-shell

2017-02-24 Thread Yesha Vora (JIRA)
Yesha Vora created ZEPPELIN-2170:


 Summary: Zeppelin does not show all WARN messages thrown by 
spark-shell
 Key: ZEPPELIN-2170
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2170
 Project: Zeppelin
  Issue Type: Bug
Reporter: Yesha Vora


Scenario:
* Create a CSV file from bug data. 
* Upload this file to HDFS
* Use spark2 interpreter to read the csv file and convert it to dataframe.

Steps to reproduce:
{code}
para1:
%sh
hdfs dfs -rmr -skipTrash  /tmp/jira
hdfs dfs -mkdir /tmp/jira
hdfs dfs -put /tmp/jira/jira.com-2.csv  /tmp/jira
hdfs dfs -ls /tmp/jira

para2:
%spark2
import org.apache.spark.sql.SQLContext

val sqlContext = new SQLContext(sc)
val df = sqlContext.read
.format("csv")
.option("header", "true") // Use first line of all files as header
.option("inferSchema", "true") // Automatically infer data types
.load("/tmp/jira/jira.com-2.csv")

df.show(){code}

While converting csv file data to dataframe , spark-shell throws below WARN 
message. 
{code}
scala> val df = sqlContext.read.format("csv").option("header", 
"true").option("inferSchema", "true").load("/tmp/jira/jira.com-2.csv")
17/02/17 00:09:12 WARN DataSource: Error while looking for metadata directory.
df: org.apache.spark.sql.DataFrame = [Summary: string, Issue key: string ... 24 
more fields]{code}

*"WARN DataSource: Error while looking for metadata directory."*  message is 
not shown in output of zeppelin notebook. This warn message is a key to debug 
the notebook failure. 
Since zeppelin does not print this message , It becomes hard for an user to 
debug issue from zeppelin. 

Tried with sc.setLogLevel("DEBUG")  as well. But this message wasn't printed.



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


[GitHub] zeppelin issue #2066: [ZEPPELIN-1725] replace cleanDirectory with forceDelet...

2017-02-24 Thread r-kamath
Github user r-kamath commented on the issue:

https://github.com/apache/zeppelin/pull/2066
  
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 #2065: [ZEPPELIN-2168] Fix typo on Elasticsearch inter...

2017-02-24 Thread juanpaulo
GitHub user juanpaulo opened a pull request:

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

[ZEPPELIN-2168] Fix typo on Elasticsearch interpreter help

### What is this PR for?
Fix typo on Elasticsearch interpreter help

### What type of PR is it?
Documentation

### Todos
* Fix typo (ndex to index)

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

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

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

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

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


commit 0c58c986b08178384babb2c526c761f2564d83f4
Author: Juan Paulo Gutierrez 
Date:   2017-02-24T09:48:22Z

fixed typo on 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.
---


[jira] [Created] (ZEPPELIN-2168) Fix typo on Elasticsearch interpreter help

2017-02-24 Thread Juan Paulo Gutierrez (JIRA)
Juan Paulo Gutierrez created ZEPPELIN-2168:
--

 Summary: Fix typo on Elasticsearch interpreter help
 Key: ZEPPELIN-2168
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2168
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Reporter: Juan Paulo Gutierrez
Priority: Minor


Current:
{noformat}
Elasticsearch interpreter:
General format:  ///  
...
  - index /ndex/type/id 
. the id can be omitted, elasticsearch will generate one
{noformat}

Should be:
{noformat}
Elasticsearch interpreter:
General format:  ///  
...
  - index /index/type/id 
. the id can be omitted, elasticsearch will generate one
{noformat}



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


[GitHub] zeppelin issue #2064: [ZEPPELIN-2164] Typo in Insufficient Privileges popup ...

2017-02-24 Thread khalidhuseynov
Github user khalidhuseynov 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 pull request #2032: [ZEPPELIN-791] Build infra: move all RAT to roo...

2017-02-24 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


commit c23cdf514b3ba1e4ef3748b64f991a8bbcb384d6
Author: DmytroShkvyra 
Date:   2017-02-23T10:50:41Z

[ZEPPELIN-791] fix conflict

commit a5fa056df9a305b42716f01b05f8b4ae6db50a63
Author: DmytroShkvyra 
Date:   2017-02-24T09:25:32Z

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

2017-02-24 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 issue #2004: [MINOR] add pig wiki page to pig doc

2017-02-24 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2004
  
Thanks @felixcheung for review, comments are addressed and a minor update 
on 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.
---


[GitHub] zeppelin pull request #1794: [WIP][MINOR][ZEPPELIN-804] Remove static method...

2017-02-24 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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-24 Thread felixcheung
Github user felixcheung commented on the issue:

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


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