[GitHub] zeppelin pull request #1546: [ Hotfix ] Incorrect (per user) setup ui for "c...

[cloverhearts]

GitHub user cloverhearts opened a pull request:

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

[ Hotfix ] Incorrect (per user) setup ui for "create new interpreter 
component"

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


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

### Todos
- [x] fix to text margin top
- [x] implement to (per note / per user) setup feature of create new 
insterpreter 

### How should this be tested?
1. on click interpreter menu.
2. on click interpreter menu.
3. check per user and per note setting. (`per user` setting must be shiro 
is activated)
4. save and check to result.

### Screenshots (if appropriate)
 - Create new Interpreter  - before

![pernotebefore](https://cloud.githubusercontent.com/assets/10525473/19588103/6d1236a4-979e-11e6-972b-bb6d35f83ac5.png)

 - Create new Interpreter  - after
![new create 
interpreter](https://cloud.githubusercontent.com/assets/10525473/19588118/87ad23ca-979e-11e6-9a2b-4ec8be27c74f.png)

 - fix margin for interpreter settings  - before

![pernotebefore](https://cloud.githubusercontent.com/assets/10525473/19588140/a8b701ee-979e-11e6-804b-4e39c063281d.png)

 - fix margin for interpreter settings  - after

![margin](https://cloud.githubusercontent.com/assets/10525473/19588145/b13ca8f0-979e-11e6-9a02-186b92a0dad1.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/cloverhearts/zeppelin 
hotfix-inerpreterRunningModeUIFix

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

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


commit ebf1d811c7e6b34cf5af85ef5a2a2f6d1b9b2910
Author: CloverHearts 
Date:   2016-10-21T05:40:01Z

hotfix - change setup ui for interpreter setting components




---
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 #1545: ZEPPELIN-1571. Support pig udf interpreter

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1571. Support pig udf interpreter

### What is this PR for?
Support a new interpreter `%pig.udf` for Pig Interpreter group. User can 
write pig udf in this interpreter, and will compile/build this udf to jar which 
would be registered in pig automatically. 


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

### Todos
* [ ] - Task

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

### How should this be tested?
Unit test is added

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

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

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


commit 9ebabbb8b09ca8e52623e48b4616bc01e0be5e3a
Author: Jeff Zhang 
Date:   2016-10-20T14:30:54Z

ZEPPELIN-1571. Support pig udf interpreter




---
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-1571) Support pig udf interpreter

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1571:


 Summary: Support pig udf interpreter
 Key: ZEPPELIN-1571
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1571
 Project: Zeppelin
  Issue Type: New Feature
  Components: Interpreters
Affects Versions: 0.6.2
Reporter: Jeff Zhang
Assignee: Jeff Zhang
 Fix For: 0.7.0






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

[GitHub] zeppelin issue #1517: [MINOR] ui improvement

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1517
  
@baekhoseok Tested and it looks good! You chose second option :)
https://cloud.githubusercontent.com/assets/10060731/19586063/9f5f8646-978c-11e6-814c-623fb8d5a063.png;>
This is the current status that I build locally.

But one wired thing is I can't build with `./grunt build` in this branch. 
(no problem in master now)
https://cloud.githubusercontent.com/assets/10060731/19586076/cfddc396-978c-11e6-9b02-0bae29b1d2b1.png;>

IDK what the exact cause is, I fixed this with rebasing. 
So could you rebase with below steps?

```
$ git checkout master
```

if you didn't set upstream yet (or you can skip this step)

```
$ git remote add upstream https://github.com/apache/zeppelin
```

rebase from master
```
$ git fetch upstream
$ git pull upstream master
$ git checkout minor_ui_fix
$ git rebase master
$ git push origin -f minor_ui_fix
```



---
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 #1544: spelling error

[khalidhuseynov]

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/1544
  
Thanks for the contribution! could you modify PR description template with 
little info and address the 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 issue #1471: Closes [ZEPPELIN-1505] Add Scio interpreter

[ravwojdyla]

Github user ravwojdyla commented on the issue:

https://github.com/apache/zeppelin/pull/1471
  
@felixcheung after going through the `BeamInterpreter`, I don't see 
immediate technical advantage of sharing the group, current implementation of 
`BeamInterpreter`, is actually pure Java interpreter, they would not share any 
configuration. That said from strictly logical point of view it makes sense for 
them to be in the same group - given they share the same model.

What kind of changes are needed to put scio in the same group as beam? And 
what is gonna be the impact on users?


---
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 #1471: Closes [ZEPPELIN-1505] Add Scio interpreter

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1471
  
I think that's strictly cosmetic - you can see the Spark/R interpreter on 
how multiple interpreter classes are going to the same group.

I think this helps discoverability and longer term transition when Scio 
becomes part of Beam.


---
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 #1471: Closes [ZEPPELIN-1505] Add Scio interpreter

[ravwojdyla]

Github user ravwojdyla commented on the issue:

https://github.com/apache/zeppelin/pull/1471
  
@felixcheung I see, thanks for help, is 95dd9bb enough?


---
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 #1462: ZEPPELIN-1477. Add Integration Test for LivyInterprete...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1462
  
As mentioned in the PR description, for now you need to export SPARK_HOME 
and LIVY_HOME. I plan to merge with travis in the following 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 issue #1462: ZEPPELIN-1477. Add Integration Test for LivyInterprete...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1462
  
I just tried it on my local; so basically it skips all the test cases.

```
WARN [2016-10-20 18:17:05,017] ({main} 
LivyIntegrationTest.java[checkPreCondition]:66) - livy integration is skipped 
because LIVY_HOME is not set
 WARN [2016-10-20 18:17:05,018] ({main} 
LivyIntegrationTest.java[checkPreCondition]:66) - livy integration is skipped 
because LIVY_HOME is not set
 WARN [2016-10-20 18:17:05,019] ({main} 
LivyIntegrationTest.java[checkPreCondition]:66) - livy integration is skipped 
because LIVY_HOME is not set
 WARN [2016-10-20 18:17:05,008] ({main} 
LivyIntegrationTest.java[checkPreCondition]:66) - livy integration is skipped 
because LIVY_HOME is not set
```

Any plan for this to merge with travis ?


---
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 #1544: spelling error

[hunylee]

GitHub user hunylee opened a pull request:

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

spelling error

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


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

### Todos
* [ ] - Task

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

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

### Screenshots (if appropriate)

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

spelling error

responce => response

seprated => seperated

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

$ git pull https://github.com/hunylee/zeppelin patch-1

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

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


commit 049043551bef722bb54c56e391fbcaf644c5179b
Author: terrylee 
Date:   2016-10-20T13:44:54Z

spelling error

spelling error

responce => response

seprated => seperated




---
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 #1462: ZEPPELIN-1477. Add Integration Test for LivyInterprete...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1462
  
Otherwise yes, 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 #1540: [WIP][ZEPPELIN-1566] Make paragraph editable with doub...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1540
  
How about making editOnDblClick false by default?


---
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 #1522: [ ZEPPELIN-1461 ] Doesn't display "description" value ...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1522
  
I think this PR tries to make less change for the dealing with that 
problem. Actually the most right way changes a lot including backend. it also 
can break backward compatibility.


---
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 #1467: [ZEPPELIN-1488] JDBC Interpreter throws error while th...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1467
  
LGTM. Merging there's no more discussion.


---
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 #1542: [MINOR][DOC] Fix typo (re-open PR #1541 with rebase)

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1542
  
Thanks for the fixing typo


---
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 #1543: Add missing TOC(Table of Contents) in install_w...

[oganizang]

GitHub user oganizang opened a pull request:

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

Add missing TOC(Table of Contents) in 
install_with_flink_and_spark_cluster.md

### What is this PR for?
Add missing TOC(Table of Contents) in 
install_with_flink_and_spark_cluster.md

### What type of PR is it?
Documentation

### What is the Jira issue?
no Jira issue for this 



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

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

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

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


commit 832410a944152fc5ec47322a172ee034f3ce1b6d
Author: oganizang 
Date:   2016-10-20T13:02:33Z

First open source commit




---
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 #1542: [MINOR][DOC] Fix typo (re-open PR #1541 with re...

[laesunk]

GitHub user laesunk opened a pull request:

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

[MINOR][DOC] Fix typo (re-open PR #1541 with rebase)

### What is this PR for?
Fix minor typos in docs

### What type of PR is it?
Documentation

### 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/laesunk/zeppelin fix_typo

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

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


commit 01ce71bc73dbc59817dafb7940e304d2fbc47b41
Author: k 
Date:   2016-10-20T11:46:43Z

fix likly

commit 190ac05b83912aa13d2be00f1a8169bfca863d0f
Author: k 
Date:   2016-10-20T11:56:17Z

fix words




---
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 #1541: [MINOR][DOC] Fix typo

[laesunk]

Github user laesunk closed the pull request at:

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


---
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 #1541: [MINOR][DOC] Fix typo

[laesunk]

GitHub user laesunk opened a pull request:

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

[MINOR][DOC] Fix typo

### What is this PR for?
Fix minor typos in docs

### What type of PR is it?
Documentation

### 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/laesunk/zeppelin fixtypo

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

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


commit 46f4e4ac337c805e7c5320b1ba769630b4a9f45a
Author: k 
Date:   2016-10-20T11:46:43Z

fix likly

commit bf5f3df027f13e50030cf1f3439ed93e123c0291
Author: k 
Date:   2016-10-20T11:56:17Z

fix words




---
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 #1520: [ZEPPELIN-1061] Select default interpreter while creat...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1520
  
@kavinkumarks Backend codes looks good to me. @corneadoug Could you please 
look into 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.
---

[GitHub] zeppelin issue #1447: [ZEPPELIN-1293] Re-create Livy session if it's lost

[gss2002]

Github user gss2002 commented on the issue:

https://github.com/apache/zeppelin/pull/1447
  
@spektom / @zjffdu @purechoc there is definitely an additional condition. 
Not sure if it's because the ConcurrentHashMaps are not being used correctly. 
But the exception doesn't get caught completely or correctly at times with the 
fix proposed here..


ERROR [2016-10-19 14:19:57,638] ({pool-2-thread-11} 
LivyHelper.java[executeHTTP]:378) - Error with 404 StatusCode: "Session '9' not 
found."
ERROR [2016-10-19 14:19:57,638] ({pool-2-thread-11} 
LivyHelper.java[interpretInput]:229) - error in interpretInput
org.apache.zeppelin.livy.LivyHelper$LivyNoSessionException: Session not 
found, Livy server would have restarted, or lost session.
at 
org.apache.zeppelin.livy.LivyHelper.executeCommand(LivyHelper.java:312)
at org.apache.zeppelin.livy.LivyHelper.interpret(LivyHelper.java:241)
at 
org.apache.zeppelin.livy.LivyHelper.interpretInput(LivyHelper.java:189)
at 
org.apache.zeppelin.livy.LivySparkInterpreter.interpret(LivySparkInterpreter.java:106)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:390)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
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)
 INFO [2016-10-19 14:19:57,639] ({pool-2-thread-11} 
SchedulerFactory.java[jobFinished]:137) - Job remoteInterpretJob_1476901197622 
finished by scheduler org.apache.zeppelin.livy.LivySparkInterpreter37814848
 INFO [2016-10-19 14:19:57,819] ({pool-2-thread-34} 
SchedulerFactory.java[jobStarted]:131) - Job remoteInterpretJob_1476901197819 
started by scheduler org.apache.zeppelin.livy.LivySparkInterpreter37814848
ERROR [2016-10-19 14:19:57,835] ({pool-2-thread-34} 
LivyHelper.java[executeHTTP]:378) - Error with 404 StatusCode: "Session '9' not 
found."
ERROR [2016-10-19 14:19:57,835] ({pool-2-thread-34} 
LivyHelper.java[interpretInput]:229) - error in interpretInput
org.apache.zeppelin.livy.LivyHelper$LivyNoSessionException: Session not 
found, Livy server would have restarted, or lost session.
at 
org.apache.zeppelin.livy.LivyHelper.executeCommand(LivyHelper.java:312)
at org.apache.zeppelin.livy.LivyHelper.interpret(LivyHelper.java:241)
at 
org.apache.zeppelin.livy.LivyHelper.interpretInput(LivyHelper.java:189)
at 
org.apache.zeppelin.livy.LivySparkInterpreter.interpret(LivySparkInterpreter.java:106)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:390)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
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)
 INFO [2016-10-19 14:19:57,836] ({pool-2-thread-34} 
SchedulerFactory.java[jobFinished]:137) - Job remoteInterpretJob_1476901197819 
finished by scheduler org.apache.zeppelin.livy.LivySparkInterpreter37814848



---
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-1570) note default owner is not set when create a note

[liupengcheng (JIRA)]

liupengcheng created ZEPPELIN-1570:
--

 Summary: note default owner is not set when create a note
 Key: ZEPPELIN-1570
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1570
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-server
Affects Versions: 0.6.1
Reporter: liupengcheng


when a new note is created, no default owner is set, but it should be the login 
username. However, what now the condition is when userA created a note, then 
userB can see this note and also change it's permission.



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

[GitHub] zeppelin pull request #1454: [ZEPPELIN-1483] Zeppelin home page list noteboo...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1447: [ZEPPELIN-1293] Re-create Livy session if it's lost

[gss2002]

Github user gss2002 commented on the issue:

https://github.com/apache/zeppelin/pull/1447
  
@spektom  just tested against my build by catching the exception and 
rethrowing.. It definitely solves the issue.

} catch (LivyNoSessionException e) {
throw e;
} catch (Exception e) {
  LOGGER.error("error in interpretInput", e);
  return new InterpreterResult(Code.ERROR, e.getMessage());
}
  }

  public InterpreterResult interpret(String stringLines,

The code base I'm using is here with you patch and a few of @zjffdu patches 
and one of mine for NestedRuntimeException for 404's with KerberosTemplate: 
https://github.com/gss2002/zeppelin/blob/GSS_PROD_BUILD/livy/src/main/java/org/apache/zeppelin/livy/LivyHelper.java


---
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 #1462: ZEPPELIN-1477. Add Integration Test for LivyInterprete...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1462
  
@felixcheung @prabhjyotsingh I have published livy jars to OSSRH, and now I 
removed the livy jars. 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 #1265: [ZEPPELIN-1210] Run interpreter per user

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1449: [MINOR] Change Markdown class name from MarkdownInterp...

[kavinkumarks]

Github user kavinkumarks commented on the issue:

https://github.com/apache/zeppelin/pull/1449
  
Thanks @Leemoonsoo !

- Kavin


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