[GitHub] zeppelin issue #1810: [MINOR] Fix navbar layout misalignment

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/1810
  
Tested and it works very well.
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 #1804: [ZEPPELIN-1578] notes list in customizing zeppelin hom...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1804
  
@soralee There is a conflict file now. Could you resolve 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 #1811: [MINOR] Fix paragraph id misalignment in dropdown menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1811
  
Thanks for your contribution. I added clipboard in #1750 but, can't 
reproduce the text overflow like you attached screenshot. I tested latest 
master in Chrome / Firefox / Safari. 
 - Chrome 
https://cloud.githubusercontent.com/assets/10060731/21538539/77726244-cde1-11e6-80b3-120f91e4a329.png;>

 - Firefox 
https://cloud.githubusercontent.com/assets/10060731/21538550/94c11aa2-cde1-11e6-86f0-a74dfcc6b803.png;>

 - Safari 
https://cloud.githubusercontent.com/assets/10060731/21538555/a2e2a772-cde1-11e6-887b-e6b7f8fcba9c.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 #1810: [MINOR] Fix navbar layout misalignment

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1810
  
Tested and LGTM.
Thanks @cuspymd for the fix.

Merge to master if there're no further 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.
---

[jira] [Created] (ZEPPELIN-1871) Spark Interpreter died unexpectedlly

[Neil Dong (JIRA)]

Neil Dong created ZEPPELIN-1871:
---

 Summary: Spark Interpreter died unexpectedlly
 Key: ZEPPELIN-1871
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1871
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters, zeppelin-server
Affects Versions: 0.6.2
Reporter: Neil Dong
Priority: Minor




About the "spark interpreter group",  When multiple notebook use 
timed-scheduling  sharing one spark interpreter instance  , because of the 
interpreter use REPL to process the notebook ,and REPL only   allow one task in 
the same time . 
 So the code looks like this :
```
public InterpreterResult interpret(String[] lines, InterpreterContext context) {
synchronized (this) {
  z.setGui(context.getGui());
  sc.setJobGroup(getJobGroup(context), "Zeppelin", false);
  InterpreterResult r = interpretInput(lines, context);
  sc.clearJobGroup();
  return r;
}
  }
```


Then the blocked processing will effect each other , eventually lead the 
interpreter jvm died in somehow without any suspicious output in the 
interpreter log.
Meanwhile the zeppelin server is constantly checking the status of the 
interpreter by calling `RemoteInterpreterService#getStatus().` Because the 
interpreter is already died , the zeppelin server always found  :
```
ERROR [2016-12-26 15:39:00,715] ({pool-1-thread-84} 
RemoteScheduler.java[getStatus]:255) - Can't get status information
org.apache.zeppelin.interpreter.InterpreterException: 
org.apache.thrift.transport.TTransportException: java.net.ConnectException: 
Connection refused
at 
org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:53)
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:189)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobStatusPoller.getStatus(RemoteScheduler.java:253)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:341)
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)
Caused by: org.apache.thrift.transport.TTransportException: 
java.net.ConnectException: Connection refused
at org.apache.thrift.transport.TSocket.open(TSocket.java:187)
at 
org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:51)
... 15 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
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.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.thrift.transport.TSocket.open(TSocket.java:182)
... 16 more
ERROR [2016-12-26 15:39:00,715] ({pool-1-thread-84} 
NotebookServer.java[afterStatusChange]:1145) - 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.interpret(RemoteInterpreter.java:250)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94)
at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:279)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:328)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

[GitHub] zeppelin pull request #1816: [MINOR] Fix broken CSS for plain text paragraph...

[AhyoungRyu]

GitHub user AhyoungRyu opened a pull request:

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

[MINOR] Fix broken CSS for plain text paragraph result

### What is this PR for?
After #1711 merged, plain text paragraph result CSS is broken now. 
Originally the text result like below (it's `0.6.2`). The font was `Monaco` 
applied by `.paragraph .text` class. 

![result1](https://cloud.githubusercontent.com/assets/10060731/21538417/421bdb76-cde0-11e6-901e-8fd79c0cb69a.png)
https://cloud.githubusercontent.com/assets/10060731/21538419/44d4f0e6-cde0-11e6-9707-227ee4b95446.png;>


But now  bootstrap default font `Helvetica` is used. 

![result2](https://cloud.githubusercontent.com/assets/10060731/21538421/47f72794-cde0-11e6-877c-4b43ae4f217f.png)
https://cloud.githubusercontent.com/assets/10060731/21538424/49824ec2-cde0-11e6-8a07-c893eb31a12e.png;>

So I bring it back by adding new class `.plainTextContainer`.

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

### What is the Jira issue?
No Iira issue for this 

### How should this be tested?
 1. See the current text paragraph result (e.g. Zeppelin tutorial: Spark)
 2. Apply this patch and start dev mode under `zeppelin-web` \w `npm run 
dev` -> browse `http://localhost:9000`
 3. Compare the text paragraph result 

### 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/AhyoungRyu/zeppelin fix/brokenCSS

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

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


commit de10ec1eefe5e0a8fd0ecb239c28dcd3c8f58347
Author: AhyoungRyu 
Date:   2016-12-29T06:40:13Z

Fix broken CSS for plain text paragraph result




---
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 #1815: [ZEPPELIN-1722] Modernize visualization/transfo...

[Leemoonsoo]

GitHub user Leemoonsoo opened a pull request:

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

[ZEPPELIN-1722] Modernize visualization/transformation using ES6 class and 
module syntax

### What is this PR for?
Modernize visualization/transformation using ES6 class and module syntax.
And remove global variable 'zeppelin'

### What type of PR is it?
Refactoring

### Todos
* [x] - Use ES6 class and module syntax

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

### 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/Leemoonsoo/zeppelin ZEPPELIN-1722

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

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


commit 59d1a6ddaee1bb64bd43e98014a10cf003bafdff
Author: Lee moon soo 
Date:   2016-12-29T06:47:57Z

use class and import/export syntax for transformations(tabledata) and 
visualizations




---
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 #1814: [ZEPPELIN-1869] changed the API response to gen...

[cloverhearts]

GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1869] changed the API response to generate to 200.

### 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?
Documentation | change

### Todos
- [x] replace to doc
- [x] change response 201 -> 200

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


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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-STATUS-CHANGE-API

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

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


commit 754309ed4c68e408e48a95d53a460d80fc2935f9
Author: cloverhearts 
Date:   2016-12-29T06:42:07Z

Apply to api success status code 200




---
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-1869) apply success respon to 200 for Zeppelin Restapi response

[CloverHearts (JIRA)]

CloverHearts created ZEPPELIN-1869:
--

 Summary: apply success respon to 200 for Zeppelin Restapi response
 Key: ZEPPELIN-1869
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1869
 Project: Zeppelin
  Issue Type: Wish
Reporter: CloverHearts
Assignee: CloverHearts


Zeppelin had many api.
But, for some api, the response is passed to 201.
This hampers the regularity of the API's success.



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

[GitHub] zeppelin issue #1808: [ZEPPELIN-1843] Error on invoking the REST API to run ...

[kavinkumarks]

Github user kavinkumarks commented on the issue:

https://github.com/apache/zeppelin/pull/1808
  
The travis build is green.


---
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 #1813: [ZEPPELIN-1868]fix to not shows up the login bu...

[astroshim]

GitHub user astroshim opened a pull request:

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

[ZEPPELIN-1868]fix to not shows up the login button on Anonymous mode.

### What is this PR for?
This PR fixs to not shows up the login button on Anonymous mode.


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


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


### How should this be tested?
1. Give permission on note.
2. Turn off the shiro.
3. Delete note that you made on 1.
4. Then you can see the `login button` like as screen shot.

### Screenshots (if appropriate)

![image](https://cloud.githubusercontent.com/assets/3348133/21537257/89d15862-cd43-11e6-8129-0e25348537ae.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/astroshim/zeppelin feat/skipLogin

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

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


commit ba7218872f75a8341ae2dd24d32b6544c40f35c1
Author: astroshim 
Date:   2016-12-29T05:12:43Z

fix to not shows up the login button on Anonymous mode.




---
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-1868) Why login button shows up even if turned off the shiro?

[Shim HyungSung (JIRA)]

Shim HyungSung created ZEPPELIN-1868:


 Summary: Why login button shows up even if turned off the shiro?
 Key: ZEPPELIN-1868
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1868
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Affects Versions: 0.7.0
Reporter: Shim HyungSung
Assignee: Shim HyungSung


It doesn't need login button when turned off the shiro.



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

[GitHub] zeppelin issue #1587: [ZEPPELIN-1609] using pyspark(python3) with livy inter...

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1587
  
LGTM
merging if no more 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 #1773: [DOCS] Add doc about zeppelin.notebook.public

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1792: Change gitignore for font files

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1587: [ZEPPELIN-1609] using pyspark(python3) with livy inter...

[purechoc]

Github user purechoc commented on the issue:

https://github.com/apache/zeppelin/pull/1587
  
thank to address.

update code completed


---
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 #1729: [ZEPPELIN-1758] support livy pyspark Interpreter's mag...

[purechoc]

Github user purechoc commented on the issue:

https://github.com/apache/zeppelin/pull/1729
  
@felixcheung  @Leemoonsoo 
could you mind merge of 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 #1812: [ZEPPELIN-1850] Use yarn instead of npm to redu...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-1850] Use yarn instead of npm to reduce build time

### What is this PR for?

This PR is about using [yarn](https://yarnpkg.com/) which is ultra fast 
than npm.

As you can see, we can reduce almost 50 sec

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

### Todos
* [x] - Setup `pom.xml` to download, use yarn
* [x] - Update `README.md`

### What is the Jira issue?

[ZEPPELIN-1850](https://issues.apache.org/jira/browse/ZEPPELIN-1850)

### How should this be tested?

- Run this command to compare build time in master and pr branch

`rm -rf zeppelin-web/bower_components zeppelin-web/node 
zeppelin-web/node_modules; mvn clean package -pl 'zeppelin-web' -DskipTests`

- If you want to compare `npm install` and `yarn install` only, 

First remove this line in package.json `"postinstall": "bower install 
--silent && grunt googlefonts",`
And then, execute `npm install` and `yarn install` respectively 

### Screenshots (if appropriate)

```
## before
[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 02:49 min
[INFO] Finished at: 2016-12-29T01:28:34+09:00
[INFO] Final Memory: 37M/1239M
[INFO] 

mvn clean package -pl 'zeppelin-web' -DskipTests  138.69s user 46.12s 
system 107% cpu 2:51.21 total

## after
[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 02:02 min
[INFO] Finished at: 2016-12-29T01:34:02+09:00
[INFO] Final Memory: 49M/1259M
[INFO] 

mvn clean package -pl 'zeppelin-web' -DskipTests  102.03s user 43.56s 
system 117% cpu 2:03.78 total
```

Also, I tested `npm install` and `yarn install` only

```
## before
npm install  36.05s user 11.38s system 114% cpu 41.540 total

## after
yarn  12.90s user 11.42s system 163% cpu 14.884 total
```

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


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

$ git pull https://github.com/1ambda/zeppelin ZEPPELIN-1850/use-yarn

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

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


commit 8502890c70338e8e7541c8dc9a2ca8c968ddecb5
Author: 1ambda <1am...@gmail.com>
Date:   2016-12-28T16:36:42Z

feat: Use yarn instead of npm

commit da8f0021e1b5150f44926afbd2c4e3cb3452e17f
Author: 1ambda <1am...@gmail.com>
Date:   2016-12-28T16:42:28Z

docs: Update README.md




---
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 #1811: [MINOR] Fix paragraph id misalignment in dropdo...

[cuspymd]

GitHub user cuspymd opened a pull request:

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

[MINOR] Fix paragraph id misalignment in dropdown menu

### What is this PR for?
Fix paragraph id misalignment in dropdown menu at Chrome/Firefox browser.


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

### Todos

### What is the Jira issue?
N/A

### How should this be tested?
Open the dropdown menu of a paragraph at Chrome/Firefox browser.

### Screenshots (if appropriate)
* before

![before](https://cloud.githubusercontent.com/assets/8870299/21526341/cbc8d57e-cd66-11e6-8379-d95914139310.png)
*after

![after](https://cloud.githubusercontent.com/assets/8870299/21526378/095d732c-cd67-11e6-87b7-fb4b1e509a30.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/cuspymd/zeppelin fix-dropdown-menu

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

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


commit 0eb047c9e765f8bb0545b23e8e6db8c855285058
Author: Myoungdo Park 
Date:   2016-12-26T15:42:43Z

Fix paragraph id misalignment in dropdown menu




---
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 #1810: [MINOR] Fix navbar layout misalignment

[cuspymd]

GitHub user cuspymd opened a pull request:

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

[MINOR] Fix navbar layout misalignment

### What is this PR for?
Fix navbar layout misalignment when browser width is narrow.


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

### Todos

### What is the Jira issue?
NA

### How should this be tested?
Change the width of browser(chrome/firefox/IE)

### Screenshots (if appropriate)
* before

![before](https://cloud.githubusercontent.com/assets/8870299/21526139/5161c418-cd65-11e6-9a00-b07437413882.gif)
* after

![after](https://cloud.githubusercontent.com/assets/8870299/21526154/71470d42-cd65-11e6-8706-13f93e08445d.gif)

### 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/cuspymd/zeppelin fix-navbar

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

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


commit ce756960c0aa7f00410aad5f034e4519bf6f7ff4
Author: Myoungdo Park 
Date:   2016-12-26T14:44:49Z

Fix navbar layout misalignment

commit d67be872dd77e74bbeb09af3dcb88979dd03a6ff
Author: Myoungdo Park 
Date:   2016-12-28T15:35:24Z

Merge branch 'ori-master' into fix-navbar




---
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 #1736: [ZEPPELIN-1757] Menu of paragraph includes keyboard sh...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1736
  
@soralee you're right. I checked again and it looks good to me.
Thanks for the improvement and merge if there're no further 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 issue #1561: [Zeppelin 914]- Apply new mechanism to IgniteInterpret...

[meenakshisekar]

Github user meenakshisekar commented on the issue:

https://github.com/apache/zeppelin/pull/1561
  
Ok sure please go ahead


On Wed, Dec 28, 2016 at 3:29 PM, DrIgor  wrote:

> Hello!
>
> I would like to help with ZEPPELIN-804
>  subtasks and make it
> possible to complete refactoring
>
> If you don't mind I will rebase this PR and take a look at #1077
> 
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



-- 
Thanks & Regards,
Meenakshi.



---
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 #1796: [WIP] ZEPPELIN-1852. Use multiple InterpreterResult fo...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1796
  
Rest 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 #1809: ZEPPELIN-1866. No meaningful exception for pig interpr...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1809
  
@felixcheung Please help review. CI failure is not relevant.
```
AngularElem
- should provide onclick method *** FAILED ***
  The code passed to eventually never returned normally. Attempted 1 times 
over 185.23286 milliseconds. Last failure message: 0 was not equal to 1. 
(AbstractAngularElemTest.scala:64)
AngularElem
```


---
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 #1796: [WIP] ZEPPELIN-1852. Use multiple InterpreterResult fo...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1796
  
Thanks @prabhjyotsingh , because I think it make more sense to name it as 
`zeppelin.livy.session.create_timeout`, doc is updated. 


---
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 #1796: [WIP] ZEPPELIN-1852. Use multiple InterpreterResult fo...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1796
  
Any specific reason you want to change `livy.create.session.timeout` ? You 
may want to update this 
https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/interpreter/livy.html doc as 
well.

👍  for adding test case.


---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API to run ...

[kavinkumarks]

Github user kavinkumarks commented on the issue:

https://github.com/apache/zeppelin/pull/1808
  
Reopening to trigger the CI build.


---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

Github user kavinkumarks closed the pull request at:

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


---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

GitHub user kavinkumarks reopened a pull request:

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

[ZEPPELIN-1843] Error on invoking the REST API to run paragraph 
synchronously


### What is this PR for?
This fixes the validation check of paragraph's note id to match with the 
Note instance id.

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

### Todos
NA

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

### How should this be tested?
The run para synchronous REST API should be successful.

### 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/kavinkumarks/zeppelin 
zeppelin-1843-run-para-sync-api-error

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

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


commit b5f29270ead7a065d440b8fbf2db590805d9
Author: Kavin 
Date:   2016-12-28T07:39:19Z

Throw IAE only when the note id of the instance and paragraph's note id
doesn't match.




---
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 #1796: [WIP] ZEPPELIN-1852. Use multiple InterpreterResult fo...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1796
  
@Leemoonsoo 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 issue #1808: [ZEPPELIN-1843] Error on invoking the REST API to run ...

[kavinkumarks]

Github user kavinkumarks commented on the issue:

https://github.com/apache/zeppelin/pull/1808
  
Reopening to trigger the CI build.


---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

GitHub user kavinkumarks reopened a pull request:

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

[ZEPPELIN-1843] Error on invoking the REST API to run paragraph 
synchronously


### What is this PR for?
This fixes the validation check of paragraph's note id to match with the 
Note instance id.

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

### Todos
NA

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

### How should this be tested?
The run para synchronous REST API should be successful.

### 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/kavinkumarks/zeppelin 
zeppelin-1843-run-para-sync-api-error

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

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


commit b5f29270ead7a065d440b8fbf2db590805d9
Author: Kavin 
Date:   2016-12-28T07:39:19Z

Throw IAE only when the note id of the instance and paragraph's note id
doesn't match.




---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

Github user kavinkumarks closed the pull request at:

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


---
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 #1561: [Zeppelin 914]- Apply new mechanism to IgniteInterpret...

[DrIgor]

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/1561
  
Hello!

I would like to help with 
[ZEPPELIN-804](https://issues.apache.org/jira/browse/ZEPPELIN-804) subtasks and 
make it possible to complete refactoring

If you don't mind I will rebase this PR and take a look at #1077


---
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 #1600: Using HDFS to backup and restore notebook

[aspen01]

Github user aspen01 commented on the issue:

https://github.com/apache/zeppelin/pull/1600
  
 I committed this branch on latest master and force-push 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-1867) Update document for pig interpreter and add one sample note

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1867:


 Summary: Update document for pig interpreter and add one sample 
note
 Key: ZEPPELIN-1867
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1867
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
 Fix For: 0.7.0






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

[GitHub] zeppelin pull request #1809: ZEPPELIN-1866. No meaningful exception for pig ...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1866. No meaningful exception for pig interpreter under tez engine


### What is this PR for?
This PR is to fix the bug that there's no meaningful exception when using 
tez engine. 


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

### Todos
* [ ] - Task

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

### How should this be tested?
Unit test is added and also manually test it. 

### Screenshots (if appropriate)

![image](https://cloud.githubusercontent.com/assets/164491/21519099/9eb518d6-cd25-11e6-8bd9-38161173cb64.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-1866

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

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


commit e8bd9f23afa779d5ffcde8a374e22c5b749dc31d
Author: Jeff Zhang 
Date:   2016-12-28T09:44:47Z

ZEPPELIN-1866. No meaningful exception for pig interpreter under tez engine




---
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-1866) No meaningful exception for pig interpreter under tez engine

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1866:


 Summary: No meaningful exception for pig interpreter under tez 
engine
 Key: ZEPPELIN-1866
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1866
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
 Fix For: 0.7.0






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

[GitHub] zeppelin pull request #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

GitHub user kavinkumarks reopened a pull request:

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

[ZEPPELIN-1843] Error on invoking the REST API to run paragraph 
synchronously


### What is this PR for?
This fixes the validation check of paragraph's note id to match with the 
Note instance id.

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

### Todos
NA

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

### How should this be tested?
The run para synchronous REST API should be successful.

### 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/kavinkumarks/zeppelin 
zeppelin-1843-run-para-sync-api-error

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

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


commit b5f29270ead7a065d440b8fbf2db590805d9
Author: Kavin 
Date:   2016-12-28T07:39:19Z

Throw IAE only when the note id of the instance and paragraph's note id
doesn't match.




---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API ...

[kavinkumarks]

Github user kavinkumarks closed the pull request at:

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


---
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 #1808: [ZEPPELIN-1843] Error on invoking the REST API to run ...

[kavinkumarks]

Github user kavinkumarks commented on the issue:

https://github.com/apache/zeppelin/pull/1808
  
Reopening to trigger the CI build.


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