[GitHub] zeppelin pull request #1814: [ZEPPELIN-1869] changed the API response to gen...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1912: [HOTFIX][ZEPPELIN-1980] - Test and update CI for matpl...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1912
  
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 #1915: ZEPPELIN-1985 Remove user from pig tutorial note

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1915
  
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 #1911: [ZEPPELIN-1972] Preserve context classloader

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1911
  
Thanks @DrIgor for fix and explanation of the issue!

When RemoteInterpreterServer creates Interpreter, it [wraps interpreter 
instance with 
LazyOpenInterpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/remote/RemoteInterpreterServer.java#L187).
 If we wrap interpreter instance with 
[ClassLoaderInterpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/ClassloaderInterpreter.java)
 as well, like [zeppelin do when creating interpreter 
locally](https://github.com/apache/zeppelin/blob/ae1cb0527bc223b25761e1370618929e228183f8/zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterFactory.java#L1123),
 then every interpreter will benefit by ClassloaderInterpreter. 
ClassloaderInterpreter restores classloader after methods call.

@DrIgor @jongyoul Shell we try make RemoteInterpreterServer wrap 
interpreter with ClassloaderInterpreter? what do you think?


---
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 #1905: [ZEPPELIN-1974] Remove extension from webpack c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1910: ZEPPELIN-1977. spark 2.1 uses a more recent com...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1915: ZEPPELIN-1985 Remove user from pig tutorial note

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1915
  
@AhyoungRyu Please help review


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

[GitHub] zeppelin pull request #1915: ZEPPELIN-1985 Remove user from pig tutorial not...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1985 Remove user from pig tutorial note

### What is this PR for?
Should remove the user from pig tutorial note, otherwise it can not be seen 
in anonymous mode.


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

### Todos
* [ ] - Task

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

### How should this be tested?
Tested it in anonymous mode

### Screenshots (if appropriate)
 

![image](https://cloud.githubusercontent.com/assets/164491/22135013/5f34ad78-df06-11e6-9043-fffce363bb9e.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/zjffdu/zeppelin ZEPPELIN-1985

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

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


commit c92b8f3ac8e9df357b1b01aff397b53fd9a9804a
Author: Jeff Zhang 
Date:   2017-01-18T07:10:07Z

ZEPPELIN-1985. Remove user from pig tutorial note




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

[jira] [Created] (ZEPPELIN-1985) Remove user from pig tutorial note

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1985:


 Summary: Remove user from pig tutorial note
 Key: ZEPPELIN-1985
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1985
 Project: Zeppelin
  Issue Type: Bug
Reporter: Jeff Zhang
Priority: Minor


Should remove the user from pig tutorial note, otherwise it can not be seen in 
anonymous mode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZEPPELIN-1984) Zeppelin Server doesn't catch all exception when launching a new interpreter process

[Ruslan Dautkhanov (JIRA)]

Ruslan Dautkhanov created ZEPPELIN-1984:
---

 Summary: Zeppelin Server doesn't catch all exception when 
launching a new interpreter process
 Key: ZEPPELIN-1984
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1984
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-interpreter, zeppelin-server
Affects Versions: 0.7.0
 Environment: Zeppelin server from a month old master snapshot
Reporter: Ruslan Dautkhanov


We saw below exception stack when Zeppelin server tries to start a new 
interpreter process, for example, Spark interpreter. It was really hard to 
debug and the only way to capture real root cause, was to add 
{code}
LOG="/tmp/interpreter.sh-$$.log"
date >> $LOG
set -x
exec >> $LOG
exec 2>&1
{code} to $zeppelinhome/bin/interpreter.sh file
so all stdout and stderr from the interpreter.sh would go to that file.
So it showed real problem 
{noformat}
Exception in thread "main" org.apache.spark.SparkException: Keytab file: 
/home//.kt does not exist
at 
org.apache.spark.deploy.SparkSubmit$.prepareSubmitEnvironment(SparkSubmit.scala:555)
at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:158)
...
{noformat}
while all other Zeppelin logs and note output was showing misleading 
"Connection refused" - see below stack

{noformat}
ERROR [2017-01-18 16:54:38,533] ({pool-2-thread-2} 
NotebookServer.java[afterStatusChange]:1645) - Error
org.apache.zeppelin.interpreter.InterpreterException: 
org.apache.zeppelin.interpreter.InterpreterException: 
org.apache.thrift.transport.TTransportException: java.net.ConnectException: 
Connection refused
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:232)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:400)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:105)
at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:316)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:329)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
...
{noformat}

The issue might be that after interpreter.sh is started and exits right away - 
https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/remote/RemoteInterpreterManagedProcess.java#L121
 
this does not get captured anywhere. The only sign you'll see on Zeppelin side 
is "Connection refused" as Zeppelin wouldn't be able to connect to a new 
interpreter process. We saw different root causes (above error from 
spark-submit that keytab file doesn't exist is just one of them), and every 
time we had to add tracing into interpreter.sh to capture real problem.

We think there are two possible ways to improve that:
1) capture fact that interpreter.sh bails out (and don't try to connect in 
https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/remote/RemoteInterpreterManagedProcess.java#L132
 as it'll produce expected "Connection refused")
2) if one point 1) isn't possible for some reason (although I don't why that 
would be) - at least capture errors produced by interpreter.sh so error stack 
in Zeppelin log files and paragraph output that kicked off interpreter start 
would have some meaningful information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zeppelin issue #1913: [ZEPPELIN-1979] fix 'File size limit Exceeded' when im...

[Tagar]

Github user Tagar commented on the issue:

https://github.com/apache/zeppelin/pull/1913
  
Thank you @khalidhuseynov 


---
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 #1914: [ZEPPELIN-1983] Feedback about success/failure ...

[beriaanirudh]

GitHub user beriaanirudh opened a pull request:

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

[ZEPPELIN-1983] Feedback about success/failure when interpreter is re…

### What is this PR for?
When a interpreter is restarted, there is no feedback to user whether the 
action is received/honoured by zeppelin. This might also lead them to click 
restart multiple times, before they realize it has taken affect.
Also fixed a null bug.

### What type of PR is it?
[Improvement + Bug fix]

### Todos
* None

### What is the Jira issue?
ZEPPELIN-1983

### How should this be tested?
Restart a interpreter to test the positive case. The message should 
disappers on its own after sometime if not closed. A simple way to test the 
negative case is to stop the server and then try restarting.

### Screenshots (if appropriate)
 Positive case
![positive 
case](https://cloud.githubusercontent.com/assets/4542030/22111327/fa675304-de84-11e6-9323-da49f2f70902.png)

 Negative case
![negative 
case](https://cloud.githubusercontent.com/assets/4542030/22111326/fa31bd84-de84-11e6-8a2e-07aaf0179275.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/beriaanirudh/zeppelin ZEPPELIN-1983

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

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


commit 761b986ef649fcd00a02e938d108b50c21118c42
Author: Beria 
Date:   2016-05-06T04:32:02Z

[ZEPPELIN-1983] Feedback about success/failure when interpreter is restarted




---
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: R interpreter

[Jeff Zhang]

That is SparkR, R interpreter is in the r folder under the root of zeppelin.



Igor Drozdov 于2017年1月19日周四 下午8:06写道：

> Hello!
>
> I'm working on https://issues.apache.org/jira/browse/ZEPPELIN-921 and I
> have some doubts about R Interpreter.
>
> Currently, R interpreter jar is in the same directory as Spark
> interpreter. InterpreterFactory searches for interpreters in spark dir,
> successfully loads interpreter-setting.json for spark and stops scanning
> this folder. So R interpreter is never loaded!
>
> Could anyone confirm that R interpreter does not work for now? Or it is my
> local misconfiguration?
>
> Thank you,
> Igor Drozdov
>

R interpreter

[Igor Drozdov]

Hello!

I'm working on https://issues.apache.org/jira/browse/ZEPPELIN-921 and I have 
some doubts about R Interpreter.

Currently, R interpreter jar is in the same directory as Spark interpreter. 
InterpreterFactory searches for interpreters in spark dir, successfully loads 
interpreter-setting.json for spark and stops scanning this folder. So R 
interpreter is never loaded!

Could anyone confirm that R interpreter does not work for now? Or it is my 
local misconfiguration?

Thank you,
Igor Drozdov

[jira] [Created] (ZEPPELIN-1983) Feedback on success/failure of interpreter restart

[Anirudh Beria (JIRA)]

Anirudh Beria created ZEPPELIN-1983:
---

 Summary: Feedback on success/failure of interpreter restart
 Key: ZEPPELIN-1983
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1983
 Project: Zeppelin
  Issue Type: Bug
Reporter: Anirudh Beria
Assignee: Anirudh Beria


When a interpreter is restarted, there is no feedback to user whether the 
action is received/honoured by zeppelin. This might also lead them to click 
restart multiple times, before they realize it has taken affect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zeppelin issue #1911: [ZEPPELIN-1972] Preserve context classloader

[DrIgor]

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/1911
  
@jongyoul I checked SparkInterpreter, it has the same issue with context 
class loader


---
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-1982) When using the "Select * ..." statement doesn't show the response In %sql interpreter

[Chin TzuLin (JIRA)]

Chin TzuLin created ZEPPELIN-1982:
-

 Summary: When using the "Select * ..." statement doesn't  show the 
response In %sql interpreter
 Key: ZEPPELIN-1982
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1982
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Chin TzuLin



When I execute the sample which is from tutorial.
"Select * ..." statement doesn't  show the response

!http://i.imgur.com/hCfvhWY.png!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)