[GitHub] zeppelin issue #2526: [ZEPPELIN-2848] Added new type of user to only run not...

2017-08-26 Thread gfalcone
Github user gfalcone commented on the issue:

https://github.com/apache/zeppelin/pull/2526
  
@1ambda @zjffdu @felixcheung do you still need clarifications or 
modifications from me? 


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
GitHub user zjffdu reopened a pull request:

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

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

### What is this PR for?
This is the first step for implement IPython Interpreter in Zeppelin.  I 
just use the jupyter_client to create and manage the ipython kernel. We don't 
need to care about python compilation and execution, all the things are 
delegated to ipython kernel. Ideally all the features of ipython should be 
available in Zeppelin as well.  

For now, user can use %python.ipython for IPython Interpreter. And if 
ipython is available, the default python interpreter will use ipython. But user 
can still set `zeppelin.python.useIPython` as false to enforce to use the old 
implementation of python interpreter. 

Main features:
* IPython interpreter support
** All the ipython features are available, including visualization, ipython 
magics. 
* ZeppelinContext support
* Streaming output support
* Support Ipython in PySpark

Regarding the visualization, ideally all the visualization libraries work 
in jupyter should also work here.
In unit test, I only verify the following 3 popular visualization library. 
could add more later.
* matplotlib
* bokeh
* ggplot

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

### Todos
* [ ] - Task

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

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

### Screenshots (if appropriate)
Verify bokeh in IPython Interpreter

![image](https://user-images.githubusercontent.com/164491/27999716-756d749e-6552-11e7-90bb-4c6b08f4ab5c.png)

Verify matplotlib

![image](https://user-images.githubusercontent.com/164491/28046960-e881b28e-6619-11e7-9e1f-7f4662f842f3.png)

Verify ZeppelinContext


![image](https://user-images.githubusercontent.com/164491/28119378-4212620c-6747-11e7-89d5-3b5e609593ce.png)

Verify Streaming

![streaming](https://user-images.githubusercontent.com/164491/28950974-8f92fe1e-78fa-11e7-841f-3174da198bb7.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/zjffdu/zeppelin ZEPPELIN-2753

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

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


commit b0b5c95a6802c595177c187e8363c08c7e464a54
Author: Jeff Zhang 
Date:   2017-07-02T07:51:14Z

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

commit e869f31d07650685907eb00b0ce2d2c15869232d
Author: Jeff Zhang 
Date:   2017-08-26T03:59:43Z

address 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 pull request #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
Github user zjffdu closed the pull request at:

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


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
Github user zjffdu closed the pull request at:

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


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
GitHub user zjffdu reopened a pull request:

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

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

### What is this PR for?
This is the first step for implement IPython Interpreter in Zeppelin.  I 
just use the jupyter_client to create and manage the ipython kernel. We don't 
need to care about python compilation and execution, all the things are 
delegated to ipython kernel. Ideally all the features of ipython should be 
available in Zeppelin as well.  

For now, user can use %python.ipython for IPython Interpreter. And if 
ipython is available, the default python interpreter will use ipython. But user 
can still set `zeppelin.python.useIPython` as false to enforce to use the old 
implementation of python interpreter. 

Main features:
* IPython interpreter support
** All the ipython features are available, including visualization, ipython 
magics. 
* ZeppelinContext support
* Streaming output support
* Support Ipython in PySpark

Regarding the visualization, ideally all the visualization libraries work 
in jupyter should also work here.
In unit test, I only verify the following 3 popular visualization library. 
could add more later.
* matplotlib
* bokeh
* ggplot

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

### Todos
* [ ] - Task

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

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

### Screenshots (if appropriate)
Verify bokeh in IPython Interpreter

![image](https://user-images.githubusercontent.com/164491/27999716-756d749e-6552-11e7-90bb-4c6b08f4ab5c.png)

Verify matplotlib

![image](https://user-images.githubusercontent.com/164491/28046960-e881b28e-6619-11e7-9e1f-7f4662f842f3.png)

Verify ZeppelinContext


![image](https://user-images.githubusercontent.com/164491/28119378-4212620c-6747-11e7-89d5-3b5e609593ce.png)

Verify Streaming

![streaming](https://user-images.githubusercontent.com/164491/28950974-8f92fe1e-78fa-11e7-841f-3174da198bb7.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/zjffdu/zeppelin ZEPPELIN-2753

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

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


commit b0b5c95a6802c595177c187e8363c08c7e464a54
Author: Jeff Zhang 
Date:   2017-07-02T07:51:14Z

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

commit e869f31d07650685907eb00b0ce2d2c15869232d
Author: Jeff Zhang 
Date:   2017-08-26T03:59:43Z

address 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-2883) Host must be manually added to /etc/hosts, or else Zeppelin won't load

2017-08-26 Thread Ken Williams (JIRA)
Ken Williams created ZEPPELIN-2883:
--

 Summary: Host must be manually added to /etc/hosts, or else 
Zeppelin won't load
 Key: ZEPPELIN-2883
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2883
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.7.2
 Environment: Mac OS X
Reporter: Ken Williams


I downloaded a fresh {{zeppelin-0.7.2-bin-all}} and started it with 
{{./bin/zeppelin-daemon.sh start}}.  Visiting http://localhost:8080, I get the 
stack trace shown below.

If I add {{127.0.0.1   Nerb.local}} to my {{/etc/hosts}} file, I can load 
Zeppelin properly.

I don't think the process should care what the hostname of the client is.

{code}
HTTP ERROR 500

Problem accessing /. Reason:

Server Error
Caused by:

java.net.UnknownHostException: Nerb.local: Nerb.local: nodename nor servname 
provided, or not known
at java.net.InetAddress.getLocalHost(InetAddress.java:1475)
at 
org.apache.zeppelin.utils.SecurityUtils.isValidOrigin(SecurityUtils.java:72)
at org.apache.zeppelin.server.CorsFilter.doFilter(CorsFilter.java:55)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:499)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.UnknownHostException: Nerb.local: nodename nor servname 
provided, or not known
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)
at 
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1295)
at java.net.InetAddress.getLocalHost(InetAddress.java:1471)
... 21 more
Caused by:

java.net.UnknownHostException: Nerb.local: nodename nor servname provided, or 
not known
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)
at 
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1295)
at java.net.InetAddress.getLocalHost(InetAddress.java:1471)
at 
org.apache.zeppelin.utils.SecurityUtils.isValidOrigin(SecurityUtils.java:72)
at org.apache.zeppelin.server.CorsFilter.doFilter(CorsFilter.java:55)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
   

[GitHub] zeppelin pull request #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
Github user zjffdu closed the pull request at:

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


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
GitHub user zjffdu reopened a pull request:

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

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

### What is this PR for?
This is the first step for implement IPython Interpreter in Zeppelin.  I 
just use the jupyter_client to create and manage the ipython kernel. We don't 
need to care about python compilation and execution, all the things are 
delegated to ipython kernel. Ideally all the features of ipython should be 
available in Zeppelin as well.  

For now, user can use %python.ipython for IPython Interpreter. And if 
ipython is available, the default python interpreter will use ipython. But user 
can still set `zeppelin.python.useIPython` as false to enforce to use the old 
implementation of python interpreter. 

Main features:
* IPython interpreter support
** All the ipython features are available, including visualization, ipython 
magics. 
* ZeppelinContext support
* Streaming output support
* Support Ipython in PySpark

Regarding the visualization, ideally all the visualization libraries work 
in jupyter should also work here.
In unit test, I only verify the following 3 popular visualization library. 
could add more later.
* matplotlib
* bokeh
* ggplot

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

### Todos
* [ ] - Task

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

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

### Screenshots (if appropriate)
Verify bokeh in IPython Interpreter

![image](https://user-images.githubusercontent.com/164491/27999716-756d749e-6552-11e7-90bb-4c6b08f4ab5c.png)

Verify matplotlib

![image](https://user-images.githubusercontent.com/164491/28046960-e881b28e-6619-11e7-9e1f-7f4662f842f3.png)

Verify ZeppelinContext


![image](https://user-images.githubusercontent.com/164491/28119378-4212620c-6747-11e7-89d5-3b5e609593ce.png)

Verify Streaming

![streaming](https://user-images.githubusercontent.com/164491/28950974-8f92fe1e-78fa-11e7-841f-3174da198bb7.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/zjffdu/zeppelin ZEPPELIN-2753

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

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


commit b0b5c95a6802c595177c187e8363c08c7e464a54
Author: Jeff Zhang 
Date:   2017-07-02T07:51:14Z

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

commit e869f31d07650685907eb00b0ce2d2c15869232d
Author: Jeff Zhang 
Date:   2017-08-26T03:59:43Z

address 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 pull request #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
Github user zjffdu closed the pull request at:

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


---
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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...

2017-08-26 Thread zjffdu
GitHub user zjffdu reopened a pull request:

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

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

### What is this PR for?
This is the first step for implement IPython Interpreter in Zeppelin.  I 
just use the jupyter_client to create and manage the ipython kernel. We don't 
need to care about python compilation and execution, all the things are 
delegated to ipython kernel. Ideally all the features of ipython should be 
available in Zeppelin as well.  

For now, user can use %python.ipython for IPython Interpreter. And if 
ipython is available, the default python interpreter will use ipython. But user 
can still set `zeppelin.python.useIPython` as false to enforce to use the old 
implementation of python interpreter. 

Main features:
* IPython interpreter support
** All the ipython features are available, including visualization, ipython 
magics. 
* ZeppelinContext support
* Streaming output support
* Support Ipython in PySpark

Regarding the visualization, ideally all the visualization libraries work 
in jupyter should also work here.
In unit test, I only verify the following 3 popular visualization library. 
could add more later.
* matplotlib
* bokeh
* ggplot

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

### Todos
* [ ] - Task

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

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

### Screenshots (if appropriate)
Verify bokeh in IPython Interpreter

![image](https://user-images.githubusercontent.com/164491/27999716-756d749e-6552-11e7-90bb-4c6b08f4ab5c.png)

Verify matplotlib

![image](https://user-images.githubusercontent.com/164491/28046960-e881b28e-6619-11e7-9e1f-7f4662f842f3.png)

Verify ZeppelinContext


![image](https://user-images.githubusercontent.com/164491/28119378-4212620c-6747-11e7-89d5-3b5e609593ce.png)

Verify Streaming

![streaming](https://user-images.githubusercontent.com/164491/28950974-8f92fe1e-78fa-11e7-841f-3174da198bb7.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/zjffdu/zeppelin ZEPPELIN-2753

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

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


commit b0b5c95a6802c595177c187e8363c08c7e464a54
Author: Jeff Zhang 
Date:   2017-07-02T07:51:14Z

[ZEPPELIN-2753] Basic Implementation of IPython Interpreter

commit e869f31d07650685907eb00b0ce2d2c15869232d
Author: Jeff Zhang 
Date:   2017-08-26T03:59:43Z

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