[GitHub] Leemoonsoo commented on issue #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo commented on issue #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303#issuecomment-461571102 Ah branch-0.8 already has https://github.com/apache/zeppelin/commit/1b6b269d2c2ca4fb648a695d962a3c820807dad3. This PR is merged to master only. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] asfgit closed pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
asfgit closed pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Leemoonsoo commented on issue #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo commented on issue #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303#issuecomment-461568824 Thanks @felixcheung for the review. Merging to master and branch-0.8 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Leemoonsoo opened a new pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo opened a new pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303 ### What is this PR for? Configure IPython interpreter in Docker image by installing necessary dependencies. ### What type of PR is it? Improvement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-3989 ### How should this be tested? Build docker image and see if %python interpreter works with Ipython kernel. ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Leemoonsoo closed pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo closed pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: ipython
Hi Can ipython server run inside its own docker container? How does ipython server run in Zeppelin container? Does it run inside the Zeppelin container? Thanks
[GitHub] Leemoonsoo commented on a change in pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo commented on a change in pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303#discussion_r253588410 ## File path: scripts/docker/zeppelin/bin/Dockerfile ## @@ -63,12 +63,11 @@ RUN echo "$LOG_TAG Install python related packages" && \ apt-get install -y gfortran && \ # numerical/algebra packages apt-get install -y libblas-dev libatlas-dev liblapack-dev && \ -# font, image for matplotlib +# font, image apt-get install -y libpng-dev libfreetype6-dev libxft-dev && \ # for tkinter apt-get install -y python-tk libxml2-dev libxslt-dev zlib1g-dev && \ -pip install numpy && \ -pip install matplotlib +pip install numpy==1.12.1 pandas==0.21.1 matplotlib==2.1.1 pandasql==0.7.3 ipython==5.4.1 jupyter_client==5.1.0 ipykernel==4.7.0 bokeh==0.12.10 ggplot==0.11.5 grpcio==1.8.2 bkzep==0.4.0 Review comment: This library list came from https://github.com/apache/zeppelin/blob/master/testing/install_external_dependencies.sh#L48-L49 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Leemoonsoo opened a new pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image
Leemoonsoo opened a new pull request #3303: [ZEPPELIN-3989] Configure IPython Interpreter in Docker image URL: https://github.com/apache/zeppelin/pull/3303 ### What is this PR for? Configure IPython interpreter in Docker image by installing necessary dependencies. ### What type of PR is it? Improvement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-3989 ### How should this be tested? Build docker image and see if %python interpreter works with Ipython kernel. ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (ZEPPELIN-3989) Configure IPython Interpreter in Docker image
Lee moon soo created ZEPPELIN-3989: -- Summary: Configure IPython Interpreter in Docker image Key: ZEPPELIN-3989 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3989 Project: Zeppelin Issue Type: Task Affects Versions: 0.8.0 Reporter: Lee moon soo Assignee: Lee moon soo Fix For: 0.8.1 It'll be nice if Zeppelin docker image installs necessary libraries to enable IPython Interpreter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] yx91490 closed pull request #3265: [ZEPPELIN-3910] IPython delete temp file and close stream
yx91490 closed pull request #3265: [ZEPPELIN-3910] IPython delete temp file and close stream URL: https://github.com/apache/zeppelin/pull/3265 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] felixcheung commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream
felixcheung commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream URL: https://github.com/apache/zeppelin/pull/3265#issuecomment-455901052 you can rewrite log and force push - or it might be easier to open a new PR This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] yx91490 edited a comment on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream
yx91490 edited a comment on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream URL: https://github.com/apache/zeppelin/pull/3265#issuecomment-455831861 > @yx91490 This PR is mixed with other commits. sorry, It's hard to revert, should I close this and make a new pr? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] yx91490 commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream
yx91490 commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream URL: https://github.com/apache/zeppelin/pull/3265#issuecomment-455831861 > @yx91490 This PR is mixed with other commits. sorry, I try to revert it This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] zjffdu commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream
zjffdu commented on issue #3265: [ZEPPELIN-3910] IPython delete temp file and close stream URL: https://github.com/apache/zeppelin/pull/3265#issuecomment-455780920 @yx91490 This PR is mixed with other commits. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (ZEPPELIN-3951) Enable IPython in Docker
Jeff Zhang created ZEPPELIN-3951: Summary: Enable IPython in Docker Key: ZEPPELIN-3951 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3951 Project: Zeppelin Issue Type: Bug Reporter: Jeff Zhang IPythonInterpreter require some additional libraries installed, it is not available in zeppelin docker, this ticket is trying to enable it via installing the necessary libraries in zeppelin docker -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zeppelin issue #3265: [ZEPPELIN-3910] IPython delete temp file and close str...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3265 LGTM ---
[GitHub] zeppelin issue #3265: [ZEPPELIN-3910] IPython delete temp file and close str...
Github user yx91490 commented on the issue: https://github.com/apache/zeppelin/pull/3265 > can you check failed tests https://travis-ci.org/yx91490/zeppelin/builds/468316435 I rebuild it and all test passed. ---
[GitHub] zeppelin issue #3265: [ZEPPELIN-3910] IPython delete temp file and close str...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3265 can you check failed tests https://travis-ci.org/yx91490/zeppelin/builds/468316435 ---
[GitHub] zeppelin pull request #3084: [zeppelin-3639] Add Ipython interpreter prerequ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/3084 ---
[GitHub] zeppelin issue #3084: [zeppelin-3639] Add Ipython interpreter prerequisite c...
Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/3084 that makes sense. thanks @khalidhuseynov ---
[GitHub] zeppelin issue #3084: [zeppelin-3639] Add Ipython interpreter prerequisite c...
Github user khalidhuseynov commented on the issue: https://github.com/apache/zeppelin/pull/3084 @Tagar thanks for suggestion, but I think it's better not to include this check for tornado in this function since it's not really pre-requisite check. if we add it, then we need to keep track it, and restore back when the issue with tornado is fixed. ---
[GitHub] zeppelin issue #3084: [zeppelin-3639] Add Ipython interpreter prerequisite c...
Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/3084 Would be nice to check freeze output for tornado version. tornado 5.x is broken for Zeppelin. https://issues.apache.org/jira/browse/ZEPPELIN-3505 ---
[GitHub] zeppelin issue #3084: [zeppelin-3639] Add Ipython interpreter prerequisite c...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3084 LGTM ---
[GitHub] zeppelin pull request #3084: [zeppelin-3639] Add Ipython interpreter prerequ...
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/3084 [zeppelin-3639] Add Ipython interpreter prerequisite check for protobuf ### What is this PR for? This is to protobuf prerequisite check when starting ipython kernel. This is required since from grpcio 1.12.0 it's independent from protobuf ### What type of PR is it? [ Improvement ] ### Todos * [x] - add protobuf prerequisite check * [x] - add to ipython docs ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-3639 ### How should this be tested? 1. remove grpcio and protobuf 2. install latest grpcio and try to run ipython interpreter - should fail 3. then install protobuf and try again - should work ### Screenshots (if appropriate) ### 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/khalidhuseynov/zeppelin fix/ZEPPELIN-3639 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3084.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 #3084 commit 58c06898b7d78790f153dfea9912acf1d837a5c8 Author: Khalid Huseynov Date: 2018-07-19T06:47:53Z add protobuf prerequsite check commit 066e061d25d0066102818eb57a97840cece77ad5 Author: Khalid Huseynov Date: 2018-07-19T07:03:58Z fix ipython documentation ---
[jira] [Created] (ZEPPELIN-3639) Add Ipython interpreter prerequisite check for protobuf
Khalid Huseynov created ZEPPELIN-3639: - Summary: Add Ipython interpreter prerequisite check for protobuf Key: ZEPPELIN-3639 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3639 Project: Zeppelin Issue Type: Improvement Components: Interpreters, python-interpreter Affects Versions: 0.8.0, 0.9.0 Reporter: Khalid Huseynov after grpcio 1.12 release [https://github.com/grpc/grpc/releases/tag/v1.12.0] it doesn't depend on protobuf, however we need protobuf to communicate with ipython kernel. thus we need to add prerequisite check for protobuf when starting ipython kernel -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3588) Can't run ipython interpreter from docker container
Thomas Han created ZEPPELIN-3588:
Summary: Can't run ipython interpreter from docker container
Key: ZEPPELIN-3588
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3588
Project: Zeppelin
Issue Type: Bug
Components: Interpreters
Affects Versions: 0.8.0
Reporter: Thomas Han
Startup the docker container
{{docker run -p 8080:8080 --rm --name zeppelin apache/zeppelin:0.8.0}}
Inside the container execute (refer to [this
page|https://www.zepl.com/viewer/notebooks/bm90ZTovL3pqZmZkdS84YjZmZTAzYmE4ZDc0ODg1OTQ0YWM5MDcwYjYyNzQ0Mi9ub3RlLmpzb24])
{{pip install jupyter }}{{grpcio}}{{}}
Execute
{{%python.ipython}}
{{import sys}}
{{sys?}}
If you look at the logs the ipython kernel can't be instantiated.
{quote}WARN [2018-07-06 05:33:00,389] (\{Exec Default Executor}
IPythonInterpreter.java[onProcessFailed]:394) - Exception happens in Python
Process
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit
value: 1)
at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at
org.apache.commons.exec.DefaultExecutor.access$200(DefaultExecutor.java:48)
at org.apache.commons.exec.DefaultExecutor$1.run(DefaultExecutor.java:200)
at java.lang.Thread.run(Thread.java:748)
{quote}
Followed by
{quote}INFO [2018-07-06 06:12:36,904] (\{pool-2-thread-2}
IPythonInterpreter.java[launchIPythonKernel]:293) - Wait for IPython Kernel to
be started
INFO [2018-07-06 06:12:37,005] (\{pool-2-thread-2}
IPythonInterpreter.java[launchIPythonKernel]:293) - Wait for IPython Kernel to
be started
...
{quote}
And finally times out
{quote}java.lang.RuntimeException: Fail to open IPythonInterpreter
at
org.apache.zeppelin.python.IPythonInterpreter.open(IPythonInterpreter.java:157)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:617)
at org.apache.zeppelin.scheduler.Job.run(Job.java:188)
at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:140)
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:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Fail to launch IPython Kernel in 60 seconds
at
org.apache.zeppelin.python.IPythonInterpreter.launchIPythonKernel(IPythonInterpreter.java:297)
at
org.apache.zeppelin.python.IPythonInterpreter.open(IPythonInterpreter.java:154)
... 11 more
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3530) pyspark interpreter error when using ipython
zhenhuanli708 created ZEPPELIN-3530: --- Summary: pyspark interpreter error when using ipython Key: ZEPPELIN-3530 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3530 Project: Zeppelin Issue Type: Bug Components: pySpark Affects Versions: 0.8.1 Reporter: zhenhuanli708 Fix For: 0.8.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3505) IPython interpreter: ERROR:tornado.general:Uncaught exception in ZMQStream callback
Ruslan Dautkhanov created ZEPPELIN-3505:
---
Summary: IPython interpreter: ERROR:tornado.general:Uncaught
exception in ZMQStream callback
Key: ZEPPELIN-3505
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3505
Project: Zeppelin
Issue Type: Bug
Components: Interpreters, pySpark, python-interpreter,
zeppelin-interpreter
Affects Versions: 0.8.0, 0.9.0, 0.8.1
Reporter: Ruslan Dautkhanov
Getting following exceptions in IPython interpreter..
ERROR:tornado.general:Uncaught exception in ZMQStream callback
ValueError: signal only works in main thread
ERROR:tornado.general:Uncaught exception in zmqstream callback
ERROR:tornado.application:Exception in callback
...
raise RuntimeError("IOLoop is already running")
Complete list of exceptions -
{noformat}
DEBUG [2018-05-26 10:28:29,453] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: Traceback (most
recent call last):
DEBUG [2018-05-26 10:28:29,453] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/runpy.py", line 174, in
_run_module_as_main
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: "__main__",
fname, loader, pkg_name)
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/runpy.py", line 72, in _run_code
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: exec code in
run_globals
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda-4.4.0/lib/python2.7/site-packages/ipykernel_launcher.py",
line 16, in
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output:
app.launch_new_instance()
DEBUG [2018-05-26 10:28:29,454] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/traitlets/config/application.py",
line 658, in launch_instance
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: app.start()
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output:
ERROR:tornado.general:Uncaught exception in ZMQStream callback
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: Traceback (most
recent call last):
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/zmq/eventloop/zmqstream.py",
line 432, in _run_callback
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: callback(*args,
**kwargs)
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/tornado/stack_context.py",
line 276, in null_wrapper
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: return
fn(*args, **kwargs)
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/ipykernel/kernelbase.py",
line 283, in dispatcher
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: return
self.dispatch_shell(stream, msg)
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/ipykernel/kernelbase.py",
line 233, in dispatch_shell
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output:
self.pre_handler_hook()
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/ipykernel/kernelbase.py",
line 248, in pre_handler_hook
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPythonInterpreter.java[processLine]:411) - Process Output:
self.saved_sigint_handler = signal(SIGINT, default_int_handler)
DEBUG [2018-05-26 10:28:29,455] ({Exec Stream Pumper}
IPython
[GitHub] zeppelin issue #2882: ZEPPELIN-3290. Unnecessary message 'IPython is availab...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2882 hey @zjffdu thanks for making all these improvements, could we make sure there is at least one review before merging? @Leemoonsoo ---
[GitHub] zeppelin pull request #2882: ZEPPELIN-3290. Unnecessary message 'IPython is ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2882 ---
[GitHub] zeppelin pull request #2882: ZEPPELIN-3290. Unnecessary message 'IPython is ...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2882 ZEPPELIN-3290. Unnecessary message 'IPython is available, use IPython for PySparkInterpreter' ### What is this PR for? Trivial PR for removing the unnecessary message ### What type of PR is it? [Improvement] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-3290 ### How should this be tested? * CI pass ### 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-3290 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2882.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 #2882 commit 7bf8d6ea423f069fccc8647fab048b7c94c2ab42 Author: Jeff Zhang <zjffdu@...> Date: 2018-03-20T01:24:20Z ZEPPELIN-3290. Unnecessary message 'IPython is available, use IPython for PySparkInterpreter' ---
[jira] [Created] (ZEPPELIN-3353) Ship IPython prerequisites in PythonInterpreter
Jeff Zhang created ZEPPELIN-3353: Summary: Ship IPython prerequisites in PythonInterpreter Key: ZEPPELIN-3353 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3353 Project: Zeppelin Issue Type: Improvement Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3290) Unnecessary message 'IPython is available, use IPython for PySparkInterpreter'
Andreas Weise created ZEPPELIN-3290:
---
Summary: Unnecessary message 'IPython is available, use IPython
for PySparkInterpreter'
Key: ZEPPELIN-3290
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3290
Project: Zeppelin
Issue Type: Bug
Components: pySpark
Affects Versions: 0.8.0, 0.9.0
Reporter: Andreas Weise
When using IPython the following message is printed each and every time an
IPython interpreter (%python or %pyspark) is started the first time.
{noformat}
IPython is available, use IPython for PySparkInterpreter{noformat}
I would expect to see only a message when ipython is configured but NOT
working. Of course the error case message already exists, but this positive
message is kind of annoying.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3260) iPython shell (! magic command) doesn't print
Ruslan Dautkhanov created ZEPPELIN-3260:
---
Summary: iPython shell (! magic command) doesn't print
Key: ZEPPELIN-3260
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3260
Project: Zeppelin
Issue Type: Bug
Components: Core, front-end, pySpark, python-interpreter
Affects Versions: 0.8.0, 0.9.0
Reporter: Ruslan Dautkhanov
Attachments: image-2018-02-23-10-38-07-304.png
{code:java}
%ipyspark
! !echo 1; sleep 1; echo 2
{code}
uses ipython's shell magic command (! - exclamation mark), but in Zeppelin it
prints just two empty lines:
!image-2018-02-23-10-38-07-304.png!
Should have printed two lines with "1" and "2" in them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ZEPPELIN-3256) ipython backend: capture when backend ipython process dies
Ruslan Dautkhanov created ZEPPELIN-3256: --- Summary: ipython backend: capture when backend ipython process dies Key: ZEPPELIN-3256 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3256 Project: Zeppelin Issue Type: Bug Components: Core, pySpark, python-interpreter, zeppelin-interpreter Affects Versions: 0.7.3, 0.8.0 Reporter: Ruslan Dautkhanov Using `quit()` in the new ipython interpreter backend leads to ipython backend .. exiting, and a new paragraph run gets stuck in 'RUNNING' indefinitely, or at least until pySpark interpreter is restarted. Two suggestions: # Ignore `quit()` calls # More importantly - capture when IPython backend process dies (for this any other) reason so Spark interpreter would know it has to start a new session, and so it would also not show misleading 'RUNNING' state indefinitely on the front-end. First one might be easy to fix using something `def quit(): pass` or something as soon as ipython process starts. But again more importantly it would be great to capture and recognize events when ipython process exits or dies for some reason and pass this information up to Spark interpreter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zeppelin pull request #2810: ZEPPELIN-3239. unicode characters in an iPython...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2810 ---
[GitHub] zeppelin issue #2810: ZEPPELIN-3239. unicode characters in an iPython paragr...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2810 Awesomeï¼will merge it soon ---
[GitHub] zeppelin issue #2810: ZEPPELIN-3239. unicode characters in an iPython paragr...
Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/2810 Verified manually. Works as expected. Thanks a lot @zjffdu ---
[GitHub] zeppelin issue #2810: ZEPPELIN-3239. unicode characters in an iPython paragr...
Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/2810 thanks @zjffdu! will give this a try today. ---
[GitHub] zeppelin issue #2810: ZEPPELIN-3239. unicode characters in an iPython paragr...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2810 @Tagar Could you help try verify this PR ? Thanks ---
[GitHub] zeppelin pull request #2810: ZEPPELIN-3239. unicode characters in an iPython...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2810 ZEPPELIN-3239. unicode characters in an iPython paragraph makes Spark interpreter irresponsive ### What is this PR for? Fix the unicode issues in python2. ### What type of PR is it? [Bug Fix | Improvement ] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-3239 ### How should this be tested? * Unit test is added ### 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-3239 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2810.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 #2810 commit e7c0044b5167c21916eba166fc7d8f6643298e60 Author: Jeff Zhang <zjffdu@...> Date: 2018-02-20T08:58:47Z ZEPPELIN-3239. unicode characters in an iPython paragraph makes Spark interpreter irrsponsive ---
[jira] [Created] (ZEPPELIN-3239) unicode characters in an iPython paragraph makes Spark interpreter irrsponsive
Ruslan Dautkhanov created ZEPPELIN-3239:
---
Summary: unicode characters in an iPython paragraph makes Spark
interpreter irrsponsive
Key: ZEPPELIN-3239
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3239
Project: Zeppelin
Issue Type: Bug
Reporter: Ruslan Dautkhanov
Attachments: Zeppelin-iPython_para_with_Unicode.PNG
An unicode characters in an iPython paragraph makes Spark interpreter
irresponsive.
To reproduce, type into a new %ipyspark code following phase (yes, it's not a
valid python code but the imprtant part is that it has a long unicode dash
character ):
{code}
One following unicide character makes ipythonInterpreter not responding to
Cancel commands –
{code}
DEBUG interpreter log shows following:
{quote}DEBUG [2018-02-15 00:39:45,628] (\{pool-2-thread-2}
IPythonClient.java[stream_execute]:87) - stream_execute code:
One following unicide character makes ipythonInterpreter not responding to
Cancel commands –
DEBUG [2018-02-15 00:39:45,632] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output:
ERROR:root:Exception iterating responses: 'ascii' codec can't encode character
u'\u2013' in position 91: ordinal not in range(128)
DEBUG [2018-02-15 00:39:45,632] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: Traceback (most
recent call last):
DEBUG [2018-02-15 00:39:45,633] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: File
"/opt/cloudera/parcels/Anaconda/lib/python2.7/site-packages/grpc/_server.py",
line 401, in _take_response_from_response_iterator
ERROR [2018-02-15 00:39:45,633] (\{grpc-default-executor-0}
IPythonClient.java[onError]:138) - Fail to call IPython grpc
io.grpc.StatusRuntimeException: UNKNOWN: Exception iterating responses: 'ascii'
codec can't encode character u'\u2013' in position 91: ordinal not in range(128)
at io.grpc.Status.asRuntimeException(Status.java:543)
at
io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:395)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426)
at io.grpc.internal.ClientCallImpl.access$100(ClientCallImpl.java:76)
at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:512)
at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:429)
at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:544)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:117)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
DEBUG [2018-02-15 00:39:45,633] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: return
next(response_iterator), True
DEBUG [2018-02-15 00:39:45,633] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: File
"/tmp/zeppelin_ipython1942535087961089556/ipython_server.py", line 54, in
execute
DEBUG [2018-02-15 00:39:45,633] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: print(request.code)
DEBUG [2018-02-15 00:39:45,634] (\{Exec Stream Pumper}
IPythonInterpreter.java[processLine]:388) - Process Output: UnicodeEncodeError:
'ascii' codec can't encode character u'\u2013' in position 91: ordinal not in
range(128)
INFO [2018-02-15 00:39:58,894] (\{dispatcher-event-loop-23}
Logging.scala[logInfo]:54) - Registered executor
NettyRpcEndpointRef(spark-client://Executor) (10.20.33.75:40434) with ID 2
{quote}
Notice
"Process Output: UnicodeEncodeError: 'ascii' codec can't encode character
u'\u2013' in position 91: ordinal not in range(128) "
So iPython interpreter breaks on presence of any unicode data.
!Zeppelin-iPython_para_with_Unicode.PNG!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] zeppelin issue #2736: ZEPPELIN-3179. Improve error message when IPython is n...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2736 More if no more comments ---
[GitHub] zeppelin issue #2736: ZEPPELIN-3179. Improve error message when IPython is n...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2736 @felixcheung @prabhjyotsingh Could you help review it ? Thanks ---
[jira] [Created] (ZEPPELIN-3179) Improve error message when IPython is not available
Jeff Zhang created ZEPPELIN-3179: Summary: Improve error message when IPython is not available Key: ZEPPELIN-3179 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3179 Project: Zeppelin Issue Type: Improvement Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zeppelin pull request #2725: ZEPPELIN-3136. IPython Code Completion Improvem...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2725 ---
[GitHub] zeppelin issue #2725: ZEPPELIN-3136. IPython Code Completion Improvement
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2725 Tried it on local, works well. ---
[GitHub] zeppelin issue #2725: ZEPPELIN-3136. IPython Code Completion Improvement
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2725 Thanks @mebelousov for testing it. ---
[GitHub] zeppelin issue #2725: ZEPPELIN-3136. IPython Code Completion Improvement
Github user mebelousov commented on the issue: https://github.com/apache/zeppelin/pull/2725 I have tested. It's very useful bug fix. @zjffdu thank you! ---
[GitHub] zeppelin issue #2725: ZEPPELIN-3136. IPython Code Completion Improvement
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2725 @prabhjyotsingh @felixcheung Mind to help review it ? ---
[GitHub] zeppelin pull request #2725: ZPEPELIN-3136. IPython Code Completion Improvem...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2725 ZPEPELIN-3136. IPython Code Completion Improvement ### What is this PR for? This is for better code completion support for IPythonInterpreter ### What type of PR is it? [Improvement ] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-3136 ### How should this be tested? * Unit test is updated and Manually verified. ### 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-3136 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2725.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 #2725 commit 1179fc82563b6b5c5251b2c288cb094a4a94bc8f Author: Jeff Zhang <zjffdu@...> Date: 2018-01-12T03:45:16Z ZPEPELIN-3136. IPython Code Completion Improvement ---
[jira] [Created] (ZEPPELIN-2923) ipython related message is displayed when enabling a conda env
Hoon Park created ZEPPELIN-2923: --- Summary: ipython related message is displayed when enabling a conda env Key: ZEPPELIN-2923 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2923 Project: Zeppelin Issue Type: Bug Components: python-interpreter Reporter: Hoon Park Fix For: 0.8.0 ipython related message is displayed when enabling a conda env. I attached a GIF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin pull request #2474: [ZEPPELIN-2753] Basic Implementation of IPython...
Github user asfgit 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 issue #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 I will merge it if no more 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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit e869f31d07650685907eb00b0ce2d2c15869232d Author: Jeff Zhang <zjf...@apache.org> 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...
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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit e869f31d07650685907eb00b0ce2d2c15869232d Author: Jeff Zhang <zjf...@apache.org> 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...
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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit e869f31d07650685907eb00b0ce2d2c15869232d Author: Jeff Zhang <zjf...@apache.org> 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...
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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit e869f31d07650685907eb00b0ce2d2c15869232d Author: Jeff Zhang <zjf...@apache.org> 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...
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...
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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit e869f31d07650685907eb00b0ce2d2c15869232d Author: Jeff Zhang <zjf...@apache.org> 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 issue #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 ping Leemoonsoo @1ambda @felixcheung @prabhjyotsingh for 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 @Leemoonsoo I have fixed the issue, could you try it again ? Thanks --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2474 Tried last commit. I installed jupyter, IPython, ipykernel, grpcio in my conda environment and i configured my python interpreter like  And then i'm getting `No module named py4j.java_gateway` error on first `%python.ipython` execution  And second execution, `z` is not available.  Looks like py4j library is not in python path. @zjffdu Do you have any idea on 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...
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...
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  Verify matplotlib  Verify ZeppelinContext  Verify Streaming  ### 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 78fde23c39a9fef36cea3d074b09a4748bdc17c9 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython Interpreter commit bb4d35451e3a7e83d20a2a7f66f303f2258bdd16 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-17T00:29:59Z Add cursor for completion commit 3df231497a2b4b4bd0e3703151d25a0b0a932073 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-27T11:10:27Z use IPython first, otherwise fallback to the old PythonInterpreter commit 6d1f69bb74639ebe7c826a2ed807acfa8b02619e Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-28T07:49:29Z IPython Support for PySparkInterpreter commit 3179e9abb71ea63051c1dbb918276c9c24aba6e7 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-30T09:54:23Z Support streaming output commit 4c129c66e0eca39157a742d20bed7773ffedc0d5 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-08-04T02:01:34Z add more docs --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 @Leemoonsoo @1ambda @felixcheung @prabhjyotsingh I made several follow up commit. All the features in this stage is done. Please help review that. I believe it would be a big improvement for python 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Push another commit to support streaming output --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Push another commit to use IPython in PySparkInterpreter if IPython is available , otherwise fallback to the old implementation. --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Just push another commit to use IPythonInterpreter first, if it is not available, I will fallback it to the old PythonInterpreter. --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 @1ambda I did some investtigation on that, and puts some links in https://issues.apache.org/jira/browse/ZEPPELIN-2756, hope it would be helpful for you. --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2474 Let create a PR to fix the ASCII issue, we can test this PR based on the ASCII 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Thanks @Leemoonsoo for catching that. This is due to I miss cursor for code completion. Just pushed another commit to fix that and add more unit test for it. ``` // there's no completion for 'a.' because it is not recognized by compiler for now. String st = "a='hello'\na."; completions = interpreter.completion(st, st.length(), getInterpreterContext()); assertEquals(0, completions.size()); // define a first st = "a='hello'"; result = interpreter.interpret(st, getInterpreterContext()); assertEquals(InterpreterResult.Code.SUCCESS, result.code()); // now we can get the completion for `a.` st = "a."; completions = interpreter.completion(st, st.length(), getInterpreterContext()); // it is differnet for python2 and python3 and may even different for different minor version // so only verify it is larger than 20 assertTrue(completions.size() > 20); st = "a.ca"; completions = interpreter.completion(st, st.length(), getInterpreterContext()); // a.capitalize // a.casefold assertEquals(2, completions.size()); // cursor is in the middle of code st = "a.ca\b='hello"; completions = interpreter.completion(st, 4, getInterpreterContext()); // a.capitalize // a.casefold assertEquals(2, completions.size()); ``` --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2474 Is it expected completion list?  --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Yes, that works. It is covered in unit test (https://github.com/apache/zeppelin/pull/2474/files#diff-d9c8252d37a199d13b7157e88041c0e9R124). Also I manually verified 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2474 Tested 88a1f2f and ZeppelinContext works well. Does auto completion supposed to work? --- 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-2774) Use IPython in PySparkInterpreter
Jeff Zhang created ZEPPELIN-2774: Summary: Use IPython in PySparkInterpreter Key: ZEPPELIN-2774 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2774 Project: Zeppelin Issue Type: Sub-task Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin issue #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 @Leemoonsoo Regarding the ZeppelinContext, could you try that again ? It is covered in unit test, so should be able to work. I force committed it yesterday, the latest commit Id is 956befa4151128b9ee76df2e3eada512ab9e1025 --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Thanks for testing @Leemoonsoo . These special characters are for font color, create ZEPPELIN-2756 for that which might need help from @1ambda --- 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 @Leemoonsoo @1ambda @felixcheung @prabhjyotsingh 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 #2474: [ZEPPELIN-2753] Basic Implementation of IPython...
GitHub user zjffdu opened 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. ### 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 is added. ### Screenshots (if appropriate) Verify bokeh in IPython Interpreter  ### 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 e2fbf75e0bf3a814122fa51ea3a88da2823f0487 Author: Jeff Zhang <zjf...@apache.org> Date: 2017-07-02T07:51:14Z [ZEPPELIN-2753] Basic Implementation of IPython 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-2754) Support ZeppelinContext in IPython Interpreter
Jeff Zhang created ZEPPELIN-2754: Summary: Support ZeppelinContext in IPython Interpreter Key: ZEPPELIN-2754 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2754 Project: Zeppelin Issue Type: Sub-task Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ZEPPELIN-2753) Basic Implementation of IPython Interpreter
Jeff Zhang created ZEPPELIN-2753: Summary: Basic Implementation of IPython Interpreter Key: ZEPPELIN-2753 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2753 Project: Zeppelin Issue Type: Sub-task Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ZEPPELIN-2752) Support IPython in PythonInterpreter
Jeff Zhang created ZEPPELIN-2752: Summary: Support IPython in PythonInterpreter Key: ZEPPELIN-2752 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2752 Project: Zeppelin Issue Type: New Feature Reporter: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ZEPPELIN-2644) Import IPython Or any Databricks supported format Notebooks into Zeppelin
Nassir created ZEPPELIN-2644: Summary: Import IPython Or any Databricks supported format Notebooks into Zeppelin Key: ZEPPELIN-2644 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2644 Project: Zeppelin Issue Type: Bug Reporter: Nassir Can anyone help in importing IPython notebooks into Apache Zeppelin. I also would like to be able to use any of the export formats from Databricks such as DBC archive, IPython notebook, HTML, or source file. can zeppelin import any of these? Thanks Nassir -- This message was sent by Atlassian JIRA (v6.4.14#64029)
