Re: [VOTE] Release Apache Zeppelin 0.10.1 RC2

2022-02-27 Thread moon soo Lee
+1

On Thu, Feb 24, 2022 at 9:31 AM Prabhjyot Singh 
wrote:

> +1
>
> On Thu, Feb 24, 2022 at 1:58 PM Jeff Zhang  wrote:
>
>> Hi folks,
>>
>> I propose the following RC to be released for the Apache Zeppelin
>> 0.10.1 release.
>>
>>
>> The commit id is 1654ce3847f4ebce7b228f54671340569d25a32e :
>>
>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=1654ce3847f4ebce7b228f54671340569d25a32e
>>
>>
>>
>> This corresponds to the tag: v0.10.1-rc2 :
>>
>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.10.1-rc2
>>
>> The release archives (tgz), signature, and checksums are here
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.10.1-rc2/
>>
>> The release candidate consists of the following source distribution
>> archive
>> zeppelin-0.10.1.tgz
>>
>> In addition, the following supplementary binary distributions are provided
>> for user convenience at the same location
>> zeppelin-0.10.1-bin-all.tgz
>>
>>
>> The maven artifacts are here
>>
>> https://repository.apache.org/content/repositories/orgapachezeppelin-1323/org/apache/zeppelin/
>>
>> You can find the KEYS file here:
>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>
>> Release notes available at
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12350543
>>
>>
>> Vote will be open for next 72 hours (close at 12PM 26/Feb PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>>
>> [ ] -1 disapprove (and reason why)
>>
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>
> --
> Regards,
> Prabhjyot Singh
>


Re: [VOTE] Release Apache Zeppelin 0.10.0 RC2

2021-08-20 Thread moon soo Lee
+1

Thank Jeff for preparing the RC.


On Thu, Aug 19, 2021 at 7:24 PM Jeff Zhang  wrote:

> +1,  Verified most of the tutorial notes
>
> Jongyoul Lee  于2021年8月19日周四 下午12:20写道:
>
>> +1
>>
>> I've checked the basic example about this RC
>>
>> 2021년 8월 18일 (수) 오후 3:28, 님이 작성:
>>
>>> +1
>>>
>>>
>>>
>>> *From:* Philipp Dallig 
>>> *Sent:* Wednesday, August 18, 2021 3:24 PM
>>> *To:* us...@zeppelin.apache.org
>>> *Subject:* Re: [VOTE] Release Apache Zeppelin 0.10.0 RC2
>>>
>>>
>>>
>>> +1
>>>
>>> Am 18.08.21 um 08:01 schrieb Francois Reynald:
>>>
>>> +1
>>>
>>>
>>>
>>> On 18 Aug 2021, at 05:52, Jeff Zhang  wrote:
>>>
>>>
>>>
>>>
>>> Hi folks,
>>>
>>>
>>>
>>> I propose the following RC to be released for the Apache Zeppelin 0.10.0 
>>> release.
>>>
>>>
>>>
>>>
>>>
>>> The commit id is 8f85476c40df3536718c5aa2c07b519b6bb6607e :
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=8f85476c40df3536718c5aa2c07b519b6bb6607e
>>>
>>>
>>>
>>> This corresponds to the tag: v0.10.0-rc2 :
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.10.0-rc2
>>>
>>> The release archives (tgz), signature, and checksums are here
>>>
>>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.10.0-rc2/
>>>
>>>
>>>
>>> The release candidate consists of the following source distribution archive
>>>
>>> zeppelin-0.10.0.tgz
>>>
>>>
>>>
>>> In addition, the following supplementary binary distributions are provided
>>>
>>> for user convenience at the same location
>>>
>>> zeppelin-0.10.0-bin-all.tgz
>>>
>>>
>>>
>>>
>>>
>>> The maven artifacts are here
>>>
>>> https://repository.apache.org/content/repositories/orgapachezeppelin-1302/org/apache/zeppelin/
>>>
>>>
>>>
>>> You can find the KEYS file here:
>>>
>>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>>
>>>
>>>
>>> Release notes available at 
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349536==12316221
>>>
>>>
>>>
>>> Vote will be open for next 72 hours (close at 10PM 20/Aug PDT).
>>>
>>>
>>>
>>> [ ] +1 approve
>>>
>>> [ ] 0 no opinion
>>>
>>> [ ] -1 disapprove (and reason why)
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards
>>>
>>> Jeff Zhang
>>>
>>>
>>>
>>> *François Reynald | Educational Services*
>>> t. +33 (0) 624 200 125
>>> cloudera.com 
>>>
>>>
>>>
>>>
>>
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>>
>
>
> --
> Best Regards
>
> Jeff Zhang
>


[jira] [Created] (ZEPPELIN-5317) Automate document and website deploy

2021-04-08 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-5317:
--

 Summary: Automate document and website deploy
 Key: ZEPPELIN-5317
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5317
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee Moon Soo


Currently, Apache Zeppelin website and documentation are deployed through 
apache SVN "manually", page by page. 

After a pullrequest is merged, committers may forget or make a mistake on 
performing the manual SVN deployment process.

If we can make the entire website and documentation is generated as a single 
artifact (like docker image) and make deployment automated, then there will be 
fewer broken links and outdated documentation.

Or we can learn from other ASF projects about the best practice of releasing 
website and document.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-5261) Sandbox HTML result rendering

2021-02-24 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-5261:
--

 Summary: Sandbox HTML result rendering
 Key: ZEPPELIN-5261
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5261
 Project: Zeppelin
  Issue Type: Improvement
  Components: GUI
Affects Versions: 0.9.0
Reporter: Lee Moon Soo


Zeppelin display system allows users to render arbitrary HTML results inside a 
Note. This includes Javascript inlined in the HTML data to be rendered.

It can be used for a potential xss attack, when a user open a shared notebook 
from another user, which includes an exploit code inside HTML result in the 
Note.

 

There could a couple of different approaches to prevent this

 

a. Don't render HTML results unless the user explicitly 'trust' the Note.

    In this way, when a Note includes HTML results, Zeppelin UI can ask the 
user if user want to trust and render HTML result or not.

b. Sandbox HTML result rendering using iframe

    In this way, HTML result is rendered inside an iframe came from different 
domain. Because browser's xss protection, it prevents potential exploits 
rendered in iframe access to any data in the parent window (Zeppelin). This 
approach is implemented in Google Colab.

 

IMO, (b) is more favorable while it makes security depends on 'trust' of a 
user. However, there's some expected complexity on implementation and 
configuration, such as
 * Passing result data to render from parent window to the iframe came from a 
different domain
 * Automatically resize iframe based on its content
 * client webbrowser should able to access Iframe domain. Or should able to 
configure an alternative domain to load iframe source.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Running Zeppelin server and webscoket on different

2021-01-25 Thread moon
Hi,

I think you need to change the zeppelin server source code to do that.
Just curious, can two reverse proxies point to the same zeppelin server
port?

Thanks,
moon


On Mon, Jan 25, 2021 at 8:04 AM Great Info  wrote:

> Hi,
> I need to host zeppelin behind reverse proxy due to some restrictions, our
> current existing reverse proxy only can work for http so for webscoket I
> need to use another proxy (spring-cloud-gateway).
>
> So is it possible to configure the zeppelin server to use different ports
> for http and websocket?
>
>
>
> Regards
> Chethan
>


Re: [VOTE] Release Apache Zeppelin 0.9.0 (RC1)

2020-12-23 Thread moon
+1

Thank Jeff for preparing the new release!

On Wed, Dec 23, 2020 at 4:09 AM Alex Ott  wrote:

> +1 from me: checked the checksum for -bin-all, run tests for Cassandra
> interpreter.
>
> On Sun, Dec 20, 2020 at 9:26 AM Jeff Zhang  wrote:
>
>>
>> Hi folks,
>>
>> I propose the following RC to be released for the Apache Zeppelin
>> 0.9.0 release.
>>
>> The commit id is 9b839b5ae34ce42a350a78ec40e762ddf904a480 :
>>
>> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=commit;h=9b839b5ae34ce42a350a78ec40e762ddf904a480
>>
>> This corresponds to the tag: v0.9.0-rc1 :
>>
>> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.9.0-rc1
>>
>> The release archives (tgz), signature, and checksums are here
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.9.0-rc1/
>>
>> The release candidate consists of the following source distribution
>> archive
>> zeppelin-v0.9.0.tgz
>>
>> In addition, the following supplementary binary distributions are provided
>> for user convenience at the same location
>> zeppelin-0.9.0-bin-all.tgz
>>
>>
>> The maven artifacts are here
>> https://repository.apache.org/content/repositories/orgapachezeppelin-1285
>>
>> You can find the KEYS file here:
>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>
>> Release notes available at
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342692==12316221
>>
>> Vote will be open for next 72 hours (close at 1 am 23/Dec PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


[jira] [Created] (ZEPPELIN-5167) Cannot enable helium package due to EACCES: permission denied, mkdir '/.cache'

2020-12-20 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-5167:
--

 Summary: Cannot enable helium package due to EACCES: permission 
denied, mkdir '/.cache'
 Key: ZEPPELIN-5167
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5167
 Project: Zeppelin
  Issue Type: Bug
 Environment: I'm using the the zeppelin docker image
Reporter: Ori Nakar


Can not enable helium package due to

 
{code:java}
 INFO [2020-12-17 14:20:54,342] ({qtp1179381257-29} 
YarnTaskExecutor.java[execute]:54) - Running 'yarn config set cache-folder 
/zeppelin/local-repo/helium-bundle/yarn-cache 
--registry=https://registry.npmjs.org/' in /zeppelin/local-repo/helium-bundle
ERROR [2020-12-17 14:20:54,437] ({Thread-20} InputStreamHandler.java[log]:60) - 
/zeppelin/local-repo/helium-bundle/node/yarn/dist/node_modules/mkdirp/index.js:90
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
                    throw err0;
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
                    ^
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
Error: EACCES: permission denied, mkdir '/.cache'
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Error (native)
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Object.fs.mkdirSync (fs.js:922:18)
ERROR [2020-12-17 14:20:54,438] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at sync 
(/zeppelin/local-repo/helium-bundle/node/yarn/dist/node_modules/mkdirp/index.js:71:13)
ERROR [2020-12-17 14:20:54,439] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Function.sync 
(/zeppelin/local-repo/helium-bundle/node/yarn/dist/node_modules/mkdirp/index.js:77:24)
ERROR [2020-12-17 14:20:54,439] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Object. 
(/zeppelin/local-repo/helium-bundle/node/yarn/dist/bin/yarn.js:30:8)
ERROR [2020-12-17 14:20:54,440] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Module._compile (module.js:570:32)
ERROR [2020-12-17 14:20:54,440] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Object.Module._extensions..js (module.js:579:10)
ERROR [2020-12-17 14:20:54,440] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Module.load (module.js:487:32)
ERROR [2020-12-17 14:20:54,440] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at tryModuleLoad (module.js:446:12)
ERROR [2020-12-17 14:20:54,440] ({Thread-20} InputStreamHandler.java[log]:60) - 
    at Function.Module._load (module.js:438:3)
ERROR [2020-12-17 14:20:54,445] ({qtp1179381257-29} 
HeliumRestApi.java[enablePackage]:233) - 
com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'yarn 
config set cache-folder /zeppelin/local-repo/helium-bundle/yarn-cache 
--registry=https://registry.npmjs.org/' failed. (error code 1)
java.io.IOException: 
com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'yarn 
config set cache-folder /zeppelin/local-repo/helium-bundle/yarn-cache 
--registry=https://registry.npmjs.org/' failed. (error code 1)
at 
org.apache.zeppelin.helium.HeliumBundleFactory.buildPackage(HeliumBundleFactory.java:440)
at org.apache.zeppelin.helium.Helium.enable(Helium.java:324)
at 
org.apache.zeppelin.rest.HeliumRestApi.enablePackage(HeliumRestApi.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:76)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:148)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:191)
at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:200)
at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:103)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:493)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:415)
at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:104)
at 
org.glassfish.jersey.server.ServerRuntime$1.run

Re: CI plattform

2020-11-23 Thread moon soo Lee
Before, I tried to migrate to Github Actions. ZEPPELIN-4385
<https://issues.apache.org/jira/browse/ZEPPELIN-4385>.
Zeppelin project repository was not configured to trigger build (INFRA-19249
<https://issues.apache.org/jira/browse/INFRA-19249?focusedCommentId=16956356=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16956356>
).

However, it looks like other repositories under Apache GitHub organization
can leverage Github Actions. e.g.
https://github.com/apache/incubator-tvm/actions. So it looks like there's a
way to use Github Actions.

I also agree that the CI platform that just works for a new user without
any setup is pretty important.

Thanks,
moon



On Mon, Nov 23, 2020 at 6:11 PM Jeff Zhang  wrote:

> Thanks for bring this up @Philipp Dallig 
> This is also an issue for me, but I don't know what other better options we
> have, maybe we can use apache's jenkins platform, but it may be very slow.
> Or we can check what other apache project use for CI
>
> Philipp Dallig  于2020年11月21日周六 下午9:13写道:
>
> > Hi Folks,
> >
> > I think that travis-ci.org and travis-ci.com can no longer be used for
> > our CI tests. Due to a restriction for open source builds
> > (https://twitter.com/geerlingguy/status/1324480667984498689) I have
> > migrated my Zeppelin fork from travis-ci.org to travis-ci.com.
> >
> > Last week I received 1 credits for starting travis-ci.com build
> > jobs. Unfortunately these credits are used up very quickly due to the
> > many and long tests. I used up these 1 points within one day.
> >
> > Some facts from the timeline:
> >   - In May 2018 Travis CI announces open source project migration to
> > travis-ci.com
> > (
> >
> https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps
> > )
> >   - On Nov 2, 2020: Travis CI announces new pricing model, effectively
> > ends generous open source offering.
> > (https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing)
> >   - December 31, 2020: Travis-ci.org will be put into read-only mode.
> > (
> >
> https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#frequently-asked-questions
> > )
> >
> >
> > Do we have a plan for migration, and if so, what is our plan?
> >
> > Is anything planned by the Apache Foundation?
> >
> > I would prefer a CI platform where a new user with a pull request does
> > not have to do a CI setup or a setup with only a few steps. Of course, a
> > new CI platform should be as transparent as possible.
> >
> > With kind regards
> > Philipp Dallig
> >
> >
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: [Draft] Zeppelin Board report Oct 2020

2020-10-14 Thread moon soo Lee
Thank Jeff, Philipp, Felix for the quick review!

On Wed, Oct 14, 2020 at 10:49 PM Felix Cheung 
wrote:

> Looks good
>
> On Wed, Oct 14, 2020 at 9:01 PM Jeff Zhang  wrote:
>
>> +1, Thanks moon
>>
>> moon soo Lee  于2020年10月15日周四 上午11:58写道:
>>
>>> Hi Folks,
>>>
>>> Since the report due date is 14/Oct, I made a draft of it.
>>> Please review this.
>>>
>>> ## Description:
>>>
>>>  -  Apache Zeppelin is a collaborative data analytics and visualization
>>> tool
>>> for general-purpose data processing systems.
>>>
>>> ## Activity:
>>>
>>>  - 0.9.0-preview2 has released. Now we are planning the release of 0.9.0.
>>>
>>> ## Health report:
>>>
>>>  - +6 new code contributors since last report. 329 total.
>>>
>>> ## PMC changes:
>>>
>>>  - There are currently 22 committers and 11 PMC members in this project.
>>> The Committer-to-PMC ratio is 2:1.
>>>  - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
>>>  - We invited a new PMC member, but wait for his response.
>>>
>>> ## Committer base changes:
>>>
>>>  - Currently 22 committers.
>>>  - Last committer addition was Philipp Dallig on 2020-06-24
>>>
>>> ## Releases:
>>>
>>>  - 0.9.0-preview2 was released on July 27, 2020
>>>  - 0.9.0-preview1 was released on March 26, 2020
>>>  - 0.8.2 was released on Wed Sep 29 2019
>>>  - 0.8.1 was released on Wed Jan 23 2019
>>>  - 0.8.0 was released on Wed Jul 18 2018
>>>
>>>
>>> ## Mailing list activity:
>>>
>>>  - us...@zeppelin.apache.org:
>>> - 92 emails sent to list ( 173 in previous quarter)
>>>
>>> - dev@zeppelin.apache.org:
>>> - 777 emails sent to list ( 774 in previous quarter)
>>>
>>> ## JIRA activity:
>>>
>>>  - 132 JIRA tickets created in the last 3 months
>>>  - 88 JIRA tickets are closed in last 3 months.
>>>
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>


[Draft] Zeppelin Board report Oct 2020

2020-10-14 Thread moon soo Lee
Hi Folks,

Since the report due date is 14/Oct, I made a draft of it.
Please review this.

## Description:

 -  Apache Zeppelin is a collaborative data analytics and visualization tool
for general-purpose data processing systems.

## Activity:

 - 0.9.0-preview2 has released. Now we are planning the release of 0.9.0.

## Health report:

 - +6 new code contributors since last report. 329 total.

## PMC changes:

 - There are currently 22 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
 - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
 - We invited a new PMC member, but wait for his response.

## Committer base changes:

 - Currently 22 committers.
 - Last committer addition was Philipp Dallig on 2020-06-24

## Releases:

 - 0.9.0-preview2 was released on July 27, 2020
 - 0.9.0-preview1 was released on March 26, 2020
 - 0.8.2 was released on Wed Sep 29 2019
 - 0.8.1 was released on Wed Jan 23 2019
 - 0.8.0 was released on Wed Jul 18 2018


## Mailing list activity:

 - us...@zeppelin.apache.org:
- 92 emails sent to list ( 173 in previous quarter)

- dev@zeppelin.apache.org:
- 777 emails sent to list ( 774 in previous quarter)

## JIRA activity:

 - 132 JIRA tickets created in the last 3 months
 - 88 JIRA tickets are closed in last 3 months.


Re: Supported interpreters

2020-09-30 Thread moon soo Lee
I think you can just set up a PR in this case. But opening a JIRA issue is
always a good idea :)


On Wed, Sep 30, 2020 at 5:38 AM Andrea Santurbano  wrote:

> Thank you so much Moon,
> do I need to open a JIRA issue for it?
> Or I can just set up the PR?
>
> Il giorno mar 29 set 2020 alle ore 19:10 moon soo Lee <
> leemoon...@gmail.com>
> ha scritto:
>
> > Hi,
> >
> > You can find it from 'gh-pages' branch.
> >
> https://github.com/apache/zeppelin/blob/gh-pages/supported_interpreters.md
> >
> > 'gh-pages' keeps the source code of the website.
> > Each version of Zeppelin documentation (which you can find source code
> > under /docs dir of master branch) is added to the website after the
> > release, under "Docs" menu.
> >
> >
> >
> > On Tue, Sep 29, 2020 at 4:41 AM Andrea Santurbano 
> > wrote:
> >
> > > Hi guys,
> > > the list here:
> > > https://zeppelin.apache.org/supported_interpreters.html
> > > Is missing the Neo4j interpreter, how can I add it?
> > > I looked into the github repo but I didn't find anything.
> > >
> >
>


Re: Supported interpreters

2020-09-29 Thread moon soo Lee
Hi,

You can find it from 'gh-pages' branch.
https://github.com/apache/zeppelin/blob/gh-pages/supported_interpreters.md

'gh-pages' keeps the source code of the website.
Each version of Zeppelin documentation (which you can find source code
under /docs dir of master branch) is added to the website after the
release, under "Docs" menu.



On Tue, Sep 29, 2020 at 4:41 AM Andrea Santurbano  wrote:

> Hi guys,
> the list here:
> https://zeppelin.apache.org/supported_interpreters.html
> Is missing the Neo4j interpreter, how can I add it?
> I looked into the github repo but I didn't find anything.
>


[jira] [Created] (ZEPPELIN-5062) Highlight 0.9.0 new features and improvements on website

2020-09-22 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-5062:
--

 Summary: Highlight 0.9.0 new features and improvements on website
 Key: ZEPPELIN-5062
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5062
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee Moon Soo


Highlights 0.9.0 new features and improvements on website



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4985) Instant visual feedback on high latency network environment

2020-08-05 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4985:
--

 Summary: Instant visual feedback on high latency network 
environment
 Key: ZEPPELIN-4985
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4985
 Project: Zeppelin
  Issue Type: Improvement
Affects Versions: 0.8.2
Reporter: Lee Moon Soo


In high latency network environment (between web browser and zeppelin-server), 
some user actions on the browser (mouse click, keyboard input) such as 'run 
paragraph' and 'switch visualization', first send message to zeppelin server 
and wait for response message before making any update in the ui.

This make user feel ui 'freeze' for a while. Especially on frequent actions, 
like 
 * run paragraph
 * switch visualization

can make instant visual feedback without waiting for server response, like
 * run paragraph -> change paragraph status to PENDING
 * switch visualization -> switch visualization immediately, without waiting 
for server response.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [Proposal] Zeppelin Client API (Zeppelin SDK)

2020-07-31 Thread moon soo Lee
Looks really good!
Do you think to have a CLI on top of high-level API be also useful?


On Fri, Jul 31, 2020 at 7:13 AM Jeff Zhang  wrote:

> Thanks for your feedback, I have created ticket
> https://issues.apache.org/jira/browse/ZEPPELIN-4981
>
> Just like @Alex Ott   mentioned, this api may need
> several iterations, so I plan to make it as an experimental feature
> first, and then refine the api based on user feedback.
> .
>
> Alex Ott  于2020年7月31日周五 下午7:48写道:
>
>> Idea is very good - I think that we'll need to get several iterations of
>> API refinement, but current approach looks promising.
>>
>> On Fri, Jul 24, 2020 at 5:54 PM Jeff Zhang  wrote:
>>
>> > Hi Folks,
>> >
>> > I'd like to discuss this proposal with you about the zeppelin client api
>> > (zeppelin sdk).
>> > The background is that now Zeppelin’s main usage scenario is interactive
>> > data analysis. Although it provides rest api, it is not easy for an
>> > external system (e.g. scheduler system) to integrate Zeppelin for the
>> > scenario where zeppelin is used as a backend job service. So I propose
>> to
>> > introduce a new module: Zeppelin client api (Zeppelin SDK), whose
>> purpose
>> > is to provide easy api for external systems to integrate zeppelin.
>> >
>> > I have created a google doc for the details, welcome any comments and
>> > feedback.
>> >
>> >
>> >
>> https://docs.google.com/document/d/1bLLKKxleZlZpP9EFJlLLkJKwDBps-RNvzNwh3LFZWZ4/edit?usp=sharing
>> >
>> >
>> > --
>> > Best Regards
>> >
>> > Jeff Zhang
>> >
>>
>>
>> --
>> With best wishes,Alex Ott
>> http://alexott.net/
>> Twitter: alexott_en (English), alexott (Russian)
>>
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: K8s docker images

2020-07-29 Thread moon soo Lee
Sounds like a plan!

On Wed, Jul 29, 2020 at 4:19 AM Alex Ott  wrote:

> Hi Philipp
>
> That would be nice to do finally :-)
> from my side I'm ok with having only the latest one.
> Thank you for moving it forward!
>
>
> On Wed, Jul 29, 2020 at 1:11 PM Philipp Dallig 
> wrote:
>
> > Hi Zeppelin developer,
> >
> > I would like to move forward the provision of docker images for
> Kubernetes.
> >
> > Right now we have three open PR:
> >
> >   - https://github.com/apache/zeppelin/pull/3380
> >   - https://github.com/apache/zeppelin/pull/3769
> >   - https://github.com/apache/zeppelin/pull/3859
> >
> > I would like to close PR 3380 and PR 3769 in favour for PR 3859. I also
> > want to close ZEPPELIN-4154 and create a new JIRA ticket for PR 3859.
> >
> > As written in PR 3859 I agree with Alex Ott that multiple interpreter
> > images are difficult to handle.
> >
> > Can I move forward in this matter, what are your thoughts?
> >
> > Best Regards
> >
> > Philipp Dallig
> >
> >
> >
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


Re: [VOTE] Release Apache Zeppelin 0.9.0-preview2 (RC2)

2020-07-24 Thread moon soo Lee
+1

I tested

 - build from source
 - src package license file
 - bin package license file
 - new ui access

On Fri, Jul 24, 2020 at 12:36 AM Alex Ott  wrote:

> +1 from me. What's done:
>
> - checked the checksum
> - run spark samples
> - tested cassandra interpreter
> - installed some plugins from helium registry
>
>
> On Thu, Jul 23, 2020 at 5:04 PM Jeff Zhang  wrote:
>
>>
>> Hi folks,
>>
>> I propose the following RC to be released for the Apache Zeppelin 
>> 0.9.0-preview2 release.
>>
>>
>> The commit id is 31b9ed51f946fed934885d8fbb29e9c183552e70 : 
>> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=commit;h=31b9ed51f946fed934885d8fbb29e9c183552e70
>>
>> This corresponds to the tag: v0.9.0-preview2-rc2 : 
>> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.9.0-preview2-rc2
>>
>> The release archives (tgz), signature, and checksums are here 
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.9.0-preview2-rc2/
>>
>> The release candidate consists of the following source distribution archive
>> zeppelin-v0.9.0-preview2.tgz
>>
>> In addition, the following supplementary binary distributions are provided
>> for user convenience at the same location
>> zeppelin-0.9.0-preview2-bin-all.tgz
>>
>>
>> The maven artifacts are here 
>> https://repository.apache.org/content/repositories/orgapachezeppelin-1283/org/apache/zeppelin/
>>
>> You can find the KEYS file here: 
>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>
>> Release notes available at 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342692==12316221
>>
>> Vote will be open for next 72 hours (close at 8am 26/July PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


Re: [Draft] Zeppelin Board Report

2020-07-06 Thread moon soo Lee
Thank Jeff for writing a draft.
It looks good to me :)

On Mon, Jul 6, 2020 at 7:53 AM Jeff Zhang  wrote:

>
> Hi Folks,
>
> Here's the draft for this month zeppelin board report, let me know what
> you think.
>
>
> ## Description:
>
>  -  Apache Zeppelin is a collaborative data analytics and visualization
> tool
>
> for general-purpose data processing systems.
>
> ## Activity:
>
>  - 0.9.0-preview1 got many feedback from community and we make a lot of
> imporvements. Now We are planning the release of 0.9.0-preview2.
>
>  - A series of flink on zeppelin videos are published on Zeppelin's
> youtube channel.
>
>  -  2 security issues are still unresolved due to no enough
> knowledge, we are working with security team to resolve them asap.
> of security.
> zeppelin: Notebook permission bypass vulnerability
> 2018-08-20
> zeppelin: Apache Zeppelin LDAP Injection
> CVE-2019-10096.
>
>
>
> ## Health report:
>
>  - +16 new code contributors since last report. 323 total.
>
>
> ## PMC changes:
>
>  - There are currently 22 committers and 11 PMC members in this project.
> The Committer-to-PMC ratio is 2:1.
>
>  - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
>
>  - We invited a new PMC member, but wait for his response.
>
> ## Committer base changes:
>
>  - Currently 22 committers.
>
>  - Last committer addition was Philipp Dallig on 2020-06-24
>
> ## Releases:
>
>  - 0.9.0-preview1 was released on March 26, 2020
>
>  - 0.8.2 was released on Wed Sep 29 2019
>
>  - 0.8.1 was released on Wed Jan 23 2019
>
>  - 0.8.0 was released on Wed Jul 18 2018
>
>
> ## Mailing list activity:
>
>  - us...@zeppelin.apache.org:
>
> - 108 emails sent to list ( 122 in previous quarter)
>
> - dev@zeppelin.apache.org:
>
> - 863 emails sent to list ( 934 in previous quarter)
>
> ## JIRA activity:
>
>  - 228 JIRA tickets created in the last 3 months
>  - 136 JIRA tickets are closed in last 3 months.
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: [DISCUSS] Release 0.9.0 preview2

2020-07-01 Thread moon soo Lee
I don't see a particular blocker and looks like it's time to have preview2!
Shell we create an umbrella issue in Jira for 0.9.0 preview2 release
anyway, so people can track the progress of the release?

Thanks,
moon


On Tue, Jun 30, 2020 at 7:49 PM Jeff Zhang  wrote:

> Hi Folks,
>
> We discuss about releasing 0.9.0 preview2 several weeks ago, I think it is
> time to do that, let me know if you have any blocker issues that you would
> like to include in 0.9.0 preview2.
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: [Announce] New Zeppelin Committer: Philipp Dallig

2020-06-26 Thread moon soo Lee
It's exciting news because I was always impressed by high-quality code
contributions from Philipp Dalling.
Congratulations! Welcome aboard!

On Thu, Jun 25, 2020 at 11:23 PM Jeff Zhang  wrote:

>
> The Project Management Committee (PMC) for Apache Zeppelin
> has invited Philipp Dallig to become a committer and we are very pleased
> to announce that he has accepted.
>
> We greatly appreciate all of Philipp Dallig's hard work and generous
> contributions to the project. We look forward to continued involvement in
> the project.
>
> Congratulations & Welcome aboard Philipp Dallig !
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: Update Zeppelin Interpreter only leveragin Helium

2020-06-21 Thread moon soo Lee
What Helium does for the Interpreter is just downloading binaries from
maven repository.
*bin/install-interpreter.sh* is the CLI, which runs InstallInterpreter
<https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/install/InstallInterpreter.java>
class.

So, if multiple versions of interpreters are published to a maven
repository (with different neo4j driver versions),
Helium can help users to download different versions and install.

The interpreter maven artifacts are predefined in conf/interpreter-list
<https://github.com/apache/zeppelin/blob/master/conf/interpreter-list>,
however, *bin/install-interpreter.sh* can download any artifact using '-t'
flag.

Thanks,
moon


On Sun, Jun 21, 2020 at 7:51 AM Jeff Zhang  wrote:

> I don't know much about helium, so I can not help on that.
> But if the api is incompatible, you can also consider using reflection, you
> can refer to the spark/spark-shims module.
>
>
> Andrea Santurbano  于2020年6月21日周日 下午10:11写道:
>
> > Unfortunatelly no because there are different classes so we cannot use
> the
> > same approach.
> > Do you think it's something feasible use helium for that?
> >
> > Il giorno dom 21 giu 2020 alle 09:54 Jeff Zhang  ha
> > scritto:
> >
> > > If the api is compatible between different versions of Neo4j driver,
> then
> > > you can just don't ship Neo4j driver into zeppelin, let users provide
> > that.
> > > e.g. currently spark interpreter supports multiple versions of spark,
> > > Zeppelin doesn't' ship with any spark jars, it is user's responsibility
> > to
> > > provide that via specifying SPARK_HOME
> > >
> > >
> > >
> > > Andrea Santurbano  于2020年6月21日周日 下午3:35写道:
> > >
> > > > Hi guys,
> > > > If I want to update a zeppelin interpreter only there is a way to do
> > it?
> > > > Let me explain the use case, I want to use Zeppelin 0.8.2 with Neo4j
> > 4.0
> > > > and I need to update the driver version because the version bundled
> > with
> > > > the Neo4j interpreter is not compatible with Neo4j 4.0. Can I
> leverage
> > > > Helium for this? In case so how can I do it?
> > > > I have to do a PR for updating the Neo4j Interpreter in the master
> > branch
> > > > but I also want to provide support to the old version and I don't
> want
> > to
> > > > wait for a new release :D
> > > > Thanks a lot
> > > > Andrea
> > > >
> > >
> > >
> > > --
> > > Best Regards
> > >
> > > Jeff Zhang
> > >
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: Apache Zeppelin in The State of Developer Ecosystem survey 2020

2020-06-18 Thread moon soo Lee
Curious if the result in [2] was chosen from a list provided with the
question, or people typed their tool without a given list.
Anyway, a very interesting survey!
Thank Alex for sharing this.

On Thu, Jun 18, 2020 at 8:09 PM Jeff Zhang  wrote:

> Thanks for the sharing, Alex
>
> Alex  于2020年6月19日周五 上午2:41写道:
>
> > Hey,
> >
> > I just noticed that the recent Developer Ecosystem survey 2020 [1]
> includes
> > interesting data on Apache Zeppelin adoption in the "Big Data analytics
> > platform" section [2].
> >
> >  1. https://www.jetbrains.com/lp/devecosystem-2020/
> >  2. https://imgur.com/SJbMSmE
> >
> >
> > --
> > Alex
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: [ANNOUNCE] Welcome Yadong Xie, Hsuan Lee as New Committer

2020-04-29 Thread moon soo Lee
Excited to see great work with new UI. Welcome Yadong Xie, Hsuan Lee.

On Wed, Apr 29, 2020 at 7:03 AM Jeff Zhang  wrote:

> The Project Management Committee (PMC) for Apache Zeppelin
> has invited Yadong Xie and Hsuan Lee  to become a committer and we are very
> pleased
> to announce that they have accepted.
>
> We greatly appreciate all of Yadong Xie and Hsuan Lee's hard work and
> generous contributions to the project, especially on the new angular UI
> implementation. We look forward to continued involvement in the project.
>
> Congratulations & Welcome aboard Yadong Xie and Hsuan Lee !
>
> --
> Best Regards
>
> Jeff Zhang
>


[jira] [Created] (ZEPPELIN-4760) Add description and homepage information on github repository

2020-04-16 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4760:
--

 Summary: Add description and homepage information on github 
repository
 Key: ZEPPELIN-4760
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4760
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee Moon Soo
 Attachments: image-2020-04-16-22-01-37-953.png

Today, Zeppelin's Github repo description saying "Mirror of Apache Zeppelin".

!image-2020-04-16-22-01-37-953.png!

 

We can improve this using 
[.asf.yaml|https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4748) Let user dynamically format spark web ui url on Kubernetes environment through zeppelin.spark.uiWebUrl

2020-04-09 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4748:
--

 Summary: Let user dynamically format spark web ui url on 
Kubernetes environment through zeppelin.spark.uiWebUrl
 Key: ZEPPELIN-4748
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4748
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee Moon Soo
Assignee: Lee Moon Soo
 Fix For: 0.9.0


When Zeppelin is running on Kubernetes, SparkUI URL should be dynamically 
generated, while Service name for Spark interpreter Pod is generated on 
runtime. And Ingress controller or reverse-proxy route traffic to SparkUI.

Problem is, depends on those Ingress or reverse proxy configuration, SparkUI 
url should be generated in a different formats.

Currently, generated url format is hardcoded to 
"//-.". And setting 
'zeppelin.spark.uiWebUrl' static url doesn't make any sense while we can not 
know what url it will be before run.

 

Therefore, 'zeppelin.spark.uiWebUrl' need more make sense to take url format in 
case of Kubernetes.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Logging doesn't appear to work with Docker version of 0.9.0-preview1

2020-04-07 Thread moon soo Lee
When I build my own Docker image based on master branch, I experience the
same problem. But in my case /logs is not empty.

On Tue, Mar 31, 2020 at 1:50 PM Eric Pugh 
wrote:

> I’ve tried with building my own Docker image of Zeppelin, and using the
> apache/zeppelin:0.9.0 image:
>
> docker run -p 8080:8080 --rm -v $PWD/logs:/logs -v $PWD/notebook:/notebook
> -e ZEPPELIN_LOG_DIR='/logs' -e ZEPPELIN_NOTEBOOK_DIR='/notebook' --name
> zeppelin apache/zeppelin:0.9.0
>
>
> The /logs directory remains stubbornly empty!   I wanted to confirm with
> others that they see the same issue before opening a JIRA.
>
> Thanks
>
>
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
>
> This e-mail and all contents, including attachments, is considered to be
> Company Confidential unless explicitly stated otherwise, regardless of
> whether attachments are marked as such.
>
>


Re: Zeppelin Draft board report for April 2020

2020-04-06 Thread moon soo Lee
119 closed in the last 3 months

On Mon, Apr 6, 2020 at 10:46 AM Alex Ott  wrote:

> Looks great for me - do we have statistics on closed JIRA tickets?
>
> moon soo Lee  at "Mon, 6 Apr 2020 09:21:26 -0700" wrote:
>  msL> Thank Jeff for the draft.
>  msL> Looks great to me.
>
>  msL> On Mon, Apr 6, 2020 at 9:08 AM Jeff Zhang  wrote:
>
>  >> Hi Folks,
>  >>
>  >>
>  >> Here's draft of Zeppelin Report, let me know if you have concerns.
> Thanks
>  >>
>  >>
>  >>
>  >>
>  >> ## Description:
>  >>
>  >>  -  Apache Zeppelin is a collaborative data analytics and visualization
>  >> tool
>  >>
>  >> for general-purpose data processing systems.
>  >>
>  >>
>  >>
>  >> ## Activity:
>  >>
>  >>  - Zeppelin 0.9.0-preview1 is released in March, this is first time we
> have
>  >> preview major release. Because based on our experience, it is always
> not
>  >> possible do enough test and verification in 3 day's voting period
> because
>  >> of the complexity of zeppelin. So we would like to make preview
> release for
>  >> each major release.
>  >>
>  >>
>  >>
>  >>
>  >> ## Health report:
>  >>
>  >>  - +12 new code contributors since last report. 307 total
>  >>
>  >> ## PMC changes:
>  >>
>  >>  - Currently 11 PMC members.
>  >>
>  >>  - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
>  >>
>  >> ## Committer base changes:
>  >>
>  >>  - Currently 19 committers.
>  >>
>  >>  - Last committer addition was Alex Ott at Jan 1 2020
>  >>
>  >> ## Releases:
>  >>
>  >> - 0.9.0-preview1 was released on March 26, 2020
>  >>
>  >>  - 0.8.2 was released on Wed Sep 29 2019
>  >>
>  >>  - 0.8.1 was released on Wed Jan 23 2019
>  >>
>  >>  - 0.8.0 was released on Wed Jul 18 2018
>  >>
>  >>  - 0.7.3 was released on Wed Sep 20 2017
>  >>
>  >>  - 0.7.2 was released on Mon Jun 12 2017
>  >>
>  >>  - 0.7.1 was released on Fri Mar 31 2017
>  >>
>  >>  - 0.7.0 was released on Sun Feb 05 2017
>  >>
>  >>  - 0.6.2 was released on Fri Oct 14 2016
>  >>
>  >>  - 0.6.1 was released on Aug 15 2016
>  >>
>  >>  - 0.6.0 was released on Jul 02 2016
>  >>
>  >>  - 0.5.6-incubating was released on Jan 22 2016
>  >>
>  >>  - 0.5.5-incubating was released on Nov 18 2015
>  >>
>  >>  - 0.5.0-incubating was released on Jul 23 2015
>  >>
>  >> ## Mailing list activity:
>  >>
>  >>  - us...@zeppelin.apache.org:
>  >>
>  >> -  122 emails sent to list ( 151 in previous quarter)
>  >>
>  >> - dev@zeppelin.apache.org:
>  >>
>  >> - 934 emails sent to list ( 923 in previous quarter)
>  >>
>  >> ## JIRA activity:
>  >>
>  >>  - 175 JIRA tickets created in the last 3 months
>  >>
>  >>
>  >>
>  >> --
>  >> Best Regards
>  >>
>  >> Jeff Zhang
>  >>
>
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


Re: Zeppelin Draft board report for April 2020

2020-04-06 Thread moon soo Lee
Thank Jeff for the draft.
Looks great to me.

On Mon, Apr 6, 2020 at 9:08 AM Jeff Zhang  wrote:

> Hi Folks,
>
>
> Here's draft of Zeppelin Report, let me know if you have concerns. Thanks
>
>
>
>
> ## Description:
>
>  -  Apache Zeppelin is a collaborative data analytics and visualization
> tool
>
> for general-purpose data processing systems.
>
>
>
> ## Activity:
>
>  - Zeppelin 0.9.0-preview1 is released in March, this is first time we have
> preview major release. Because based on our experience, it is always not
> possible do enough test and verification in 3 day's voting period because
> of the complexity of zeppelin. So we would like to make preview release for
> each major release.
>
>
>
>
> ## Health report:
>
>  - +12 new code contributors since last report. 307 total
>
> ## PMC changes:
>
>  - Currently 11 PMC members.
>
>  - Last PMC addition was Jeff Zhang on Thu Jan 25 2018
>
> ## Committer base changes:
>
>  - Currently 19 committers.
>
>  - Last committer addition was Alex Ott at Jan 1 2020
>
> ## Releases:
>
> - 0.9.0-preview1 was released on March 26, 2020
>
>  - 0.8.2 was released on Wed Sep 29 2019
>
>  - 0.8.1 was released on Wed Jan 23 2019
>
>  - 0.8.0 was released on Wed Jul 18 2018
>
>  - 0.7.3 was released on Wed Sep 20 2017
>
>  - 0.7.2 was released on Mon Jun 12 2017
>
>  - 0.7.1 was released on Fri Mar 31 2017
>
>  - 0.7.0 was released on Sun Feb 05 2017
>
>  - 0.6.2 was released on Fri Oct 14 2016
>
>  - 0.6.1 was released on Aug 15 2016
>
>  - 0.6.0 was released on Jul 02 2016
>
>  - 0.5.6-incubating was released on Jan 22 2016
>
>  - 0.5.5-incubating was released on Nov 18 2015
>
>  - 0.5.0-incubating was released on Jul 23 2015
>
> ## Mailing list activity:
>
>  - us...@zeppelin.apache.org:
>
> -  122 emails sent to list ( 151 in previous quarter)
>
> - dev@zeppelin.apache.org:
>
> - 934 emails sent to list ( 923 in previous quarter)
>
> ## JIRA activity:
>
>  - 175 JIRA tickets created in the last 3 months
>
>
>
> --
> Best Regards
>
> Jeff Zhang
>


[jira] [Created] (ZEPPELIN-4699) Migrate helium registry infrastructure

2020-03-28 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4699:
--

 Summary: Migrate helium registry infrastructure
 Key: ZEPPELIN-4699
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4699
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee Moon Soo


Helium registry is located in 
https://s3.amazonaws.com/helium-package/helium.(json|js)

Source code for generating registry is located here,

[https://github.com/ZEPL/helium-package-registry]

 

However, the code and registry are not well maintained recently.

I think we can consider migrate registry and generation code to somewhere 
community can more easily maintain.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [VOTE] Release Apache Zeppelin 0.9.0-preview1 (RC1)

2020-03-25 Thread moon soo Lee
+1

Tested
 - The binary package can run tutorial notebook out of the box
 - Can build docker image
- scripts/docker/zeppelin/bin/Dockerfile give me some error on R
dependency installation. But I think it's not a blocker. We can address it
on next RC.
 - Zeppelin on Kubernetes
- Everything but Spark-2.4.5 does not run out of the box. I think it is
not a blocker. We can address it on next RC.




On Wed, Mar 25, 2020 at 11:21 AM Prabhjyot Singh 
wrote:

> +1
>
> On Wed, 25 Mar 2020 at 21:12, Eric Pugh 
> wrote:
>
> > Out of curiosity, is there a Docker version of 0.9.0 preview1 available?
> > I tend to run Zeppelin as a Docker image, and I know I had some
> challenges
> > with the 0.8.x line of Docker images from
> > https://hub.docker.com/r/apache/zeppelin.
> >
> > I did modify the ./scripts/docker/zeppelin/Dockerfile to load the
> > v0.0.0-preview1-rc1.bin.tgz distribution.
> >
> > Then I followed the steps in docs/setup/deployment/docker.md to try out
> > Zeppelin and it all appears to work as a Docker image!
> >
> > One thing to note was that it didn’t auto upgrade my old .json files into
> > the new .zpln files.  I had to manually upload them.  Is there any auto
> > upgrade feature for existing notebook files?
> >
> > So non binding +1 ;-)
> >
> > Eric
> >
> >
> >
> > On Mar 25, 2020, at 1:54 AM, Jongyoul Lee  wrote:
> >
> > +1
> >
> > 2020년 3월 24일 (화) 오전 12:15, Jeff Zhang 님이 작성:
> >
> >> Hi folks,
> >>
> >> I propose the following RC to be released for the Apache Zeppelin
> >> 0.9.0-preview1 release.
> >>
> >>
> >> The commit id is a74365c0813b451db1bc78def7d1ad1279429224 :
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=commit;h=a74365c0813b451db1bc78def7d1ad1279429224
> >>
> >> This corresponds to the tag: v0.9.0-preview1-rc1 :
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=zeppelin.git;a=shortlog;h=refs/tags/v0.9.0-preview1-rc1
> >>
> >> The release archives (tgz), signature, and checksums are here
> >>
> >>
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.9.0-preview1-rc1/
> >>
> >> The release candidate consists of the following source distribution
> >> archive
> >> zeppelin-v0.9.0-preview1.tgz
> >>
> >> In addition, the following supplementary binary distributions are
> provided
> >> for user convenience at the same location
> >> zeppelin-0.9.0-preview1-bin-all.tgz
> >>
> >>
> >> The maven artifacts are here
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachezeppelin-1276/org/apache/zeppelin/
> >>
> >> You can find the KEYS file here:
> >> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> >>
> >> Release notes available at
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342692==12316221
> >>
> >> Vote will be open for next 72 hours (close at 7am 26/March PDT).
> >>
> >> [ ] +1 approve
> >> [ ] 0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >>
> >> --
> >> Best Regards
> >>
> >> Jeff Zhang
> >>
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
> >
> > ___
> > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467
> > | http://www.opensourceconnections.com | My Free/Busy
> > 
> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed
> > <
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> > This e-mail and all contents, including attachments, is considered to be
> > Company Confidential unless explicitly stated otherwise, regardless
> > of whether attachments are marked as such.
> >
> >
>
> --
>
> Warm Regards,
>
> Prabhjyot Singh
>


Re: [DISCUSS] Release for 0.9.0-preview-1

2020-03-16 Thread moon soo Lee
Definitely +1

On Mon, Mar 16, 2020 at 8:02 AM Prabhjyot Singh 
wrote:

> Yes, +1, we have put in a lot of features. We should do it soon.
>
> On Mon, Mar 16, 2020, 8:28 PM Yadong Xie  wrote:
>
>> Big +1
>>
>> Eric Pugh  于2020年3月16日周一 下午10:54写道:
>>
>> > Big +1 from me.
>> >
>> >
>> > > On Mar 16, 2020, at 10:45 AM, Jeff Zhang  wrote:
>> > >
>> > > Hi Folks,
>> > >
>> > > I'd like to start the discussion of releasing of 0.9.0-preview-1. As
>> we
>> > discussed before releasing a preview version first is suitable for a
>> major
>> > release based on our previous experience[1]. The last major release
>> 0.8.0
>> > is in 2018, I do believe we should release 0.9 to allow more people try
>> > that and gather feedback. What do you think ?
>> > >
>> > >
>> > > [1]
>> >
>> https://lists.apache.org/thread.html/3812fd7dab53e1fed4140c826fc69fa5b718636371b6c7c677b4ae88%40%3Cdev.zeppelin.apache.org%3E
>> > <
>> >
>> https://lists.apache.org/thread.html/3812fd7dab53e1fed4140c826fc69fa5b718636371b6c7c677b4ae88%40%3Cdev.zeppelin.apache.org%3E
>> > >
>> > >
>> > > --
>> > > Best Regards
>> > >
>> > > Jeff Zhang
>> >
>> > ___
>> > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
>> > http://www.opensourceconnections.com <
>> > http://www.opensourceconnections.com/> | My Free/Busy <
>> > http://tinyurl.com/eric-cal>
>> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>> >
>> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
>> >
>> >
>> > This e-mail and all contents, including attachments, is considered to be
>> > Company Confidential unless explicitly stated otherwise, regardless of
>> > whether attachments are marked as such.
>> >
>> >
>>
>


Re: Autolink references in Github repo?

2020-03-11 Thread moon soo Lee
Cool! Thanks Alex!

On Tue, Mar 10, 2020 at 12:07 PM Alex Ott  wrote:

> the auto-linking was configured, and works now - you can see it at comment
> to https://github.com/apache/zeppelin/pull/3634 - unfortunately it works
> only for newly created/edited PRs
>
> On Sat, Mar 7, 2020 at 12:12 AM Jeff Zhang  wrote:
>
> > Thanks Alex
> >
> > Alex Ott  于2020年3月7日周六 上午3:01写道:
> >
> >> I've created https://issues.apache.org/jira/browse/INFRA-19934 for that
> >>
> >> On Mon, Mar 2, 2020 at 6:31 AM Alex Ott  wrote:
> >>
> >>> Ok. Thank you - I'll file Infra ticket
> >>>
> >>> On Mon, 2 Mar 2020, 03:37 moon soo Lee,  wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> I don't have admin rights to GitHub repo but ASF Infra does.
> >>>> Usually, configuration change on Github repo can be done by filing
> >>>> issues
> >>>> to ASF infra https://issues.apache.org/jira/projects/INFRA.
> >>>>
> >>>> Let me know if anything else I can help here.
> >>>>
> >>>> Thanks!
> >>>> moon
> >>>>
> >>>>
> >>>>
> >>>> On Sun, Mar 1, 2020 at 6:19 PM Jeff Zhang  wrote:
> >>>>
> >>>> > + Moon
> >>>> >
> >>>> > Moon should have the admin right
> >>>> >
> >>>> > Alex Ott  于2020年3月2日周一 上午1:39写道:
> >>>> >
> >>>> >> Hi all
> >>>> >>
> >>>> >> one question - who owns the Zeppelin repository at Github, or have
> >>>> >> administrative rights? It would be nice to configure Autolink
> >>>> references
> >>>> >> for Zeppelin repo to automatically create links to Jira for PRs,
> >>>> etc. I
> >>>> >> have very good experience of using them for my private projects...
> >>>> >>
> >>>> >> --
> >>>> >> With best wishes,Alex Ott
> >>>> >> http://alexott.net/
> >>>> >> Twitter: alexott_en (English), alexott (Russian)
> >>>> >>
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Best Regards
> >>>> >
> >>>> > Jeff Zhang
> >>>> >
> >>>>
> >>>
> >>
> >> --
> >> With best wishes,Alex Ott
> >> http://alexott.net/
> >> Twitter: alexott_en (English), alexott (Russian)
> >>
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


Re: Autolink references in Github repo?

2020-03-01 Thread moon soo Lee
Hi,

I don't have admin rights to GitHub repo but ASF Infra does.
Usually, configuration change on Github repo can be done by filing issues
to ASF infra https://issues.apache.org/jira/projects/INFRA.

Let me know if anything else I can help here.

Thanks!
moon



On Sun, Mar 1, 2020 at 6:19 PM Jeff Zhang  wrote:

> + Moon
>
> Moon should have the admin right
>
> Alex Ott  于2020年3月2日周一 上午1:39写道:
>
>> Hi all
>>
>> one question - who owns the Zeppelin repository at Github, or have
>> administrative rights? It would be nice to configure Autolink references
>> for Zeppelin repo to automatically create links to Jira for PRs, etc. I
>> have very good experience of using them for my private projects...
>>
>> --
>> With best wishes,Alex Ott
>> http://alexott.net/
>> Twitter: alexott_en (English), alexott (Russian)
>>
>
>
> --
> Best Regards
>
> Jeff Zhang
>


[jira] [Created] (ZEPPELIN-4619) Run a note from commandline

2020-02-14 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4619:
--

 Summary: Run a note from commandline
 Key: ZEPPELIN-4619
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4619
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee Moon Soo
Assignee: Lee Moon Soo
 Fix For: 0.9.0


Provide a command-line option to run a single note.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4618) Zeppelin on Kubernetes does not automatically configure Spark on Kubernetes

2020-02-14 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4618:
--

 Summary: Zeppelin on Kubernetes does not automatically configure 
Spark on Kubernetes
 Key: ZEPPELIN-4618
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4618
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee Moon Soo
Assignee: Lee Moon Soo
 Fix For: 0.9.0


Since ZEPPELIN-4440, Spark on Kubernetes is not correctly configured when 
Zeppelin is running on Kubernetes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [ANNOUNCE] Welcome Alex Ott as New Committer

2020-01-11 Thread moon soo Lee
little but late for the welcoming party here.
I couldn’t appreciate more about starting 2020 with this great news!
Welcome Alex Ott and appreciate your involvement and contributions!

Regards,
moon


On Sat, Jan 11, 2020 at 02:21 Alex Ott  wrote:

> Thank
>
> Thank you for introduction Jeff, and thank you all for greetings!
>
> I'm looking forward to make more contribution to this very interesting
> project!
>
> Prabhjyot Singh  at "Sat, 11 Jan 2020 14:17:57 +0530" wrote:
>  PS> Hello Alex,
>
>  PS> Hearty Greetings and a very warm welcome to you.
>
>  PS> On Sat, Jan 11, 2020, 2:16 PM Xun Liu  wrote:
>
>  PS> Hi, Alex Ott.
>  PS>
>  PS> Congratulations on becoming a committer of Apache Zeppelin !!
>  PS> :-)
>  PS>
>  PS> On Sat, Jan 11, 2020 at 4:38 PM Jongyoul Lee 
> wrote:
>  PS>
>  PS> That's really great!!
>  PS>
>  PS> I appreciate his activities against Apache Zeppelin and I'm
> really happy as
>  PS> I have already known how difficult to contribute an
> opensource continuously.
>  PS>
>  PS> Please keep helping make Apache Zeppelin healthy.
>  PS>
>  PS> Regards,
>  PS> JL
>  PS>
>  PS> 2020년 1월 7일 (화) 오후 6:48, Jeff Zhang 님이 작성:
>  PS>
>  >> The Project Management Committee (PMC) for Apache Zeppelin
>  >> has invited Alex Ott to become a committer and we are very pleased
>  >> to announce that he has accepted.
>  >>
>  >> We greatly appreciate all of Alex's hard work and generous
> contributions to
>  >> the project. We look forward to continued involvement in the project.
>  >>
>  >> Congratulations & Welcome aboard Alex !
>  >>
>  >>
>  >> --
>  >> Best Regards
>  >>
>  >> Jeff Zhang
>  >>
>
>  PS> --
>  PS> 이종열, Jongyoul Lee, 李宗烈
>  PS> http://madeng.net
>
>
>
> --
> With best wishes,Alex Ott
> http://alexott.net/
> Twitter: alexott_en (English), alexott (Russian)
>


Re: [DISCUSS] Create a preview for Zeppelin 0.9.0 before making RC

2019-12-16 Thread moon soo Lee
Right, 3 days for each RC for a major release is too short.
+1 for creating a preview and docker image as well :)

On Mon, Dec 16, 2019 at 7:40 AM Andrea Santurbano  wrote:

> Yes please!
> Would be awesome have a Docker container in order test it :)
>
> Il giorno lun 16 dic 2019 alle ore 16:24 Jeff Zhang  ha
> scritto:
>
> > Hi Folks,
> >
> > We have already done lots of works on 0.9.0, I think we should consider
> > about make a release for 0.9.0. But since Zeppelin is a very complicated
> > project considering its rich features, the regular process of testing it
> > for 3 days for each RC is too short in my opinion, so I suggest to
> create a
> > preview for each major release. Then the community has more time to test
> it
> > and we have more time to fix bugs and ensure the release quality. What do
> > you think ?
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>


Recognizing contributors

2019-11-13 Thread moon soo Lee
Hi,

I'd like to have a discussion about recognizing contributors.
Many people contribute Apache Zeppelin in many different ways,

One way via code contribution, another way via non-code contributions like
creating videos, writing articles, UI design, providing talks, and so on.

I think code contributors are recognized in release notes [1]. Even GitHub
provides a contributor page [2] that anyone has access to. However,
non-code contributors are not well recognized today, IMO.

I believe, recognizing/appreciating all types of contributions really help
make the community healthy.

How about have a contributor list in 'Contributors' page [3] on website and
let contributors add themselves? Maybe it can be looks like the 'Current
Committers' page [4] on Spark project, but for contributors. Or we can also
try list contributors in release note [1].

Or do you have any better ideas and opinions? Please share your thoughts
about the right way of recognizing contributors.

Thanks,
moon

[1]
http://zeppelin.apache.org/releases/zeppelin-release-0.8.2.html#contributors
[2] https://github.com/apache/zeppelin/graphs/contributors
[3] http://zeppelin.apache.org/community.html
[4] https://spark.apache.org/committers.html


Re: Automatic update of the Helium registry doesn't work?

2019-11-03 Thread moon soo Lee
cc ahyoung. Could you take a look?? And, any good idea how we can we move
helium.json and related code zeppelin project source tree?


On Sun, Nov 3, 2019 at 06:01 Jeff Zhang  wrote:

> + Moon
>
> I think helium.json on S3 is maintained by ZEPL, Moon should know the
> details.
>
>
> Alex Ott  于2019年11月3日周日 下午6:52写道:
>
> > Hi all
> >
> > I've noticed that Helium registry (
> > https://s3.amazonaws.com/helium-package/helium.json) is still listing
> > zeppelin-leaflet 1.0.4 as the latest, although 1.0.5 was released 5
> months
> > ago (https://www.npmjs.com/package/zeppelin-leaflet) with some
> > improvements
> > regarding omitting the points that have null value for one of the
> > coordinates.
> >
> > As I understood from documentation, registry should be regenerated
> > automatically on publish of the new versions, but this doesn't happen.
> >
> > How we can enforce it?
> >
> > --
> > With best wishes,Alex Ott
> > http://alexott.net/
> > Twitter: alexott_en (English), alexott (Russian)
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>


[jira] [Created] (ZEPPELIN-4387) travis_check.py

2019-10-17 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4387:
--

 Summary: travis_check.py
 Key: ZEPPELIN-4387
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4387
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee Moon Soo
Assignee: Lee Moon Soo


Migrating all tests from Travis to Github Actions takes time.

 

Meanwhile, we can make Github Actions run travis_check.py script and get rid of 
Jenkins. Which is relatively easy to do.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4385) Move CI to Github Action from Jenkins + Travis

2019-10-16 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4385:
--

 Summary: Move CI to Github Action from Jenkins + Travis
 Key: ZEPPELIN-4385
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4385
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee Moon Soo


Currently, when a new pull request is created,

 

 1. Individual contributor's travis integration build branch

 2. Jenkins (managed by ASF infra) triggered and check individual contributor's 
travis build status

 3. Pull request build status is displayed based on Jenkins's check result

 

There was two reasons why Zeppelin project uses Jenkins + Individual 
contributor's travis integration.

 * Travis build slots in ASF organization is limited and couldn't get enough 
slot to build pullrequest and often PR waits more than 12h to be scheduled

 * Restarting individual flaky tests is not possible. while individual 
contributor doesn't have permission to access ASF's travis integration. 
Therefore, Flaky test fail require full test matrix restart and that was quite 
painful. While full test matrix run again produce other flaky test fails.

 

 

However, Jenkins now only triggered by pullrequest from comitters. 
https://issues.apache.org/jira/browse/INFRA-19249

 

Lack of integration test on pull requests really make collative development 
difficult, in the community.

 

Recently, Github added CI functionality through [Github 
Actions.|https://github.com/features/actions]

I think we need to consider this. Reasons are

 

 - Can build all pull requests

 - Non shared build slots (Build slot is not shared with other ASF project, 
unlike Travis)

 - Individual contributor also able to run CI build their branch before making 
PR

 

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Why not all Pull-Request runs Jenkins?

2019-10-10 Thread moon soo Lee
Just filed an infra issue https://issues.apache.org/jira/browse/INFRA-19249

Thanks,
moon



On Wed, Oct 9, 2019 at 8:25 PM Jeff Zhang  wrote:

> I also notice this issue, My PR will run jenkins job, but lots of
> contributors' PR don't trigger jenkins job.
>
>
>
> moon soo Lee  于2019年10月10日周四 上午8:32写道:
>
> > Hi,
> >
> > I can see some Pull-Request does not run Jenkins, like below
> >
> > https://github.com/apache/zeppelin/pull/3480
> > [image: image.png]
> >
> > And some does run Jenkins, like below
> >
> > https://github.com/apache/zeppelin/pull/3479
> >
> > [image: image.png]
> >
> > It looks like Jenkins is triggered only when github apache organization
> > member creates pull-request. Is it true?
> >
> > Does anyone have idea why Jenkins is not running for all pullrequests?
> >
> > Thanks,
> > moon
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Why not all Pull-Request runs Jenkins?

2019-10-09 Thread moon soo Lee
Hi,

I can see some Pull-Request does not run Jenkins, like below

https://github.com/apache/zeppelin/pull/3480
[image: image.png]

And some does run Jenkins, like below

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

[image: image.png]

It looks like Jenkins is triggered only when github apache organization
member creates pull-request. Is it true?

Does anyone have idea why Jenkins is not running for all pullrequests?

Thanks,
moon


[jira] [Created] (ZEPPELIN-4363) Flaky test - ParagraphActionsIT.testSingleDynamicFormTextInput

2019-10-01 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4363:
--

 Summary: Flaky test - 
ParagraphActionsIT.testSingleDynamicFormTextInput
 Key: ZEPPELIN-4363
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4363
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee Moon Soo
 Attachments: image-2019-10-01-14-32-30-390.png

[https://api.travis-ci.org/v3/job/592216145/log.txt]
{code:java}
 Results : Tests in error: 
ParagraphActionsIT.testSingleDynamicFormTextInput:536->AbstractZeppelinIT.setTextOfParagraph:49
 » NoSuchElement Tests run: 30, Failures: 0, Errors: 1, Skipped: 0{code}
screenshot taken here is

!image-2019-10-01-14-32-30-390.png!

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4362) Tests around Flink interpreter are redundant in .travis.yml

2019-10-01 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4362:
--

 Summary: Tests around Flink interpreter are redundant in 
.travis.yml
 Key: ZEPPELIN-4362
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4362
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee Moon Soo
Assignee: Lee Moon Soo


Looks like .travis.yml runs Flink interpreter in multiple test matrix.

There's test matrix for 'flink'
{code:java}
# Test flink module- sudo: required  jdk: "openjdk8"  dist: xenial  
env: PYTHON="3" SPARKR="true" PROFILE="-Pscala-2.11" BUILD_FLAG="clean 
install -Pbuild-distr -DskipRat -am" TEST_FLAG="verify -Pusing-packaged-distr 
-DskipRat" MODULES="-pl flink" TEST_PROJECTS="-DfailIfNoTests=false" {code}
However, test matrix for 'interpreter modules' also runs test in 'flink' modules
{code:java}
# Test interpreter modules- jdk: "openjdk8"  dist: xenial  env: 
PYTHON="3" SPARKR="true" SCALA_VER="2.10" TENSORFLOW="1.0.0" 
PROFILE="-Pscala-2.10" BUILD_FLAG="install -DskipTests -DskipRat -am" 
TEST_FLAG="test -DskipRat" MODULES="-pl $(echo 
.,zeppelin-interpreter,zeppelin-interpreter-api,${INTERPRETERS} | sed 
's/!//g')" TEST_PROJECTS="" {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4361) PersonalizeActionsIT.testGraphAction test fail

2019-10-01 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4361:
--

 Summary: PersonalizeActionsIT.testGraphAction test fail
 Key: ZEPPELIN-4361
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4361
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee Moon Soo


[https://api.travis-ci.org/v3/job/591740764/log.txt]
{code:java}
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 161.099 sec <<< 
FAILURE! - in org.apache.zeppelin.integration.PersonalizeActionsIT
testGraphAction(org.apache.zeppelin.integration.PersonalizeActionsIT)  Time 
elapsed: 50.642 sec  <<< FAILURE!
java.lang.AssertionError: The output of graph mode is not changed
Expected: "fa fa-bar-chart"
 but: was "fa fa-table"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.rules.ErrorCollector$1.call(ErrorCollector.java:65)
at org.junit.rules.ErrorCollector.checkSucceeds(ErrorCollector.java:78)
at org.junit.rules.ErrorCollector.checkThat(ErrorCollector.java:63)
at 
org.apache.zeppelin.integration.PersonalizeActionsIT.testGraphAction(PersonalizeActionsIT.java:252)


Results :

Failed tests: 
  PersonalizeActionsIT.testGraphAction:252 The output of graph mode is not 
changed
Expected: "fa fa-bar-chart"
 but: was "fa fa-table"

Tests run: 30, Failures: 1, Errors: 0, Skipped: 0 {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [ANNOUNCE] Apache Zeppelin 0.8.2 released

2019-09-30 Thread moon soo Lee
Great work!

On Sun, Sep 29, 2019 at 9:46 PM Prabhjyot Singh 
wrote:

> Awesome!
>
> Thank you so much Jeff for taking care of this.
>
> Congratulations community.
>
> On Sun, 29 Sep 2019, 2:15 pm Jeff Zhang,  wrote:
>
>> The Apache Zeppelin community is pleased to announce the availability of
>> the 0.8.2 release.
>>
>> Zeppelin is a collaborative data analytics and visualization tool for
>> distributed, general-purpose data processing system such as Apache Spark,
>> Apache Flink, etc.
>>
>> This is another minor release after the last minor release 0.8.1
>> The community put significant effort into improving Apache Zeppelin since 
>> the last release. 26 patches for improvements and bug fixes.
>>
>> We encourage you to download the latest release 
>> fromhttp://zeppelin.apache.org/download.html
>> Release note is available 
>> athttp://zeppelin.apache.org/releases/zeppelin-release-0.8.2.html
>>
>> We welcome your help and feedback. For more information on the project and
>> how to get involved, visit our website at http://zeppelin.apache.org/
>>
>> Thank you all users and contributors who have helped to improve Apache
>> Zeppelin.
>>
>> Regards,
>> The Apache Zeppelin community
>>
>>


[jira] [Created] (ZEPPELIN-4357) LivyInterpreterIT fail

2019-09-27 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4357:
--

 Summary: LivyInterpreterIT fail
 Key: ZEPPELIN-4357
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4357
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee Moon Soo


{code:java}
Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 271.271 sec <<< 
FAILURE! - in org.apache.zeppelin.livy.LivyInterpreterIT
testSharedInterpreter(org.apache.zeppelin.livy.LivyInterpreterIT)  Time 
elapsed: 38.941 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.zeppelin.livy.LivyInterpreterIT.testSharedInterpreter(LivyInterpreterIT.java:768)

testSparkRInterpreter(org.apache.zeppelin.livy.LivyInterpreterIT)  Time 
elapsed: 23.92 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.zeppelin.livy.LivyInterpreterIT.testSparkRInterpreter(LivyInterpreterIT.java:602)

 INFO [2019-09-27 16:48:56,063] ({Thread-0} Logging.scala[info]:39) - Shutting 
down cluster pool.

Results :

Failed tests: 
  LivyInterpreterIT.testSharedInterpreter:768 expected: but was:
  LivyInterpreterIT.testSparkRInterpreter:602 expected: but was:

Tests run: 6, Failures: 2, Errors: 0, Skipped: 0
 {code}
 

[https://api.travis-ci.org/v3/job/590204255/log.txt]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4352) Test fail after ZEPPELIN-4331

2019-09-25 Thread Lee Moon Soo (Jira)
Lee Moon Soo created ZEPPELIN-4352:
--

 Summary: Test fail after ZEPPELIN-4331
 Key: ZEPPELIN-4352
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4352
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee Moon Soo


Unittest fail after

https://issues.apache.org/jira/browse/ZEPPELIN-4331

 

[https://api.travis-ci.org/v3/job/589061181/log.txt]
{code:java}
Results :

Failed tests: 
  CassandraInterpreterTest.should_describe_table:693 expected:<...ndex_interval 
= 2048[];<...> but was:<...ndex_interval = 2048[AND 
memtable_flush_period_in_ms = 0];<...>
  CassandraInterpreterTest.should_describe_keyspace:609 
expected:<...ndex_interval = 2048[;complex_table's 
indicesNameTargetclustering2idxclustering2idx1indexed1idx2indexed2keys_map_idxkeys(key_indexed_map)pk2idxpk2As CQL 
statementCREATE INDEX clustering2idx ON 
live_data.complex_table (clustering2);CREATE INDEX idx1 ON 
live_data.complex_table (indexed1);CREATE INDEX idx2 ON live_data.complex_table 
(indexed2);CREATE INDEX keys_map_idx ON live_data.complex_table 
(keys(key_indexed_map));CREATE INDEX pk2idx ON live_data.complex_table 
(pk2);sensor_dataColumn TypeColumn NameData 
Typesensor_iduuidmonthintcharacteristicsmaptext, 
textmodel_numbertextprovidertextdatetimestampvaluedoubleAs CQL 
statementCREATE TABLE live_data.sensor_data 
(sensor_id uuid,month int,date timestamp,characteristics maptext, text 
static,model_number text static,provider text static,value double,PRIMARY KEY 
((sensor_id, month), date)) WITH CLUSTERING ORDER BY (date DESC)AND 
read_repair_chance = 0.0AND dclocal_read_repair_chance = 0.1AND 
gc_grace_seconds = 864000AND bloom_filter_fp_chance = 0.01AND caching = { 
'keys' : 'ALL', 'rows_per_partition' : 'NONE' }AND comment = ''AND compaction = 
{ 'class' : 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy' 
}AND compression = { 'sstable_compression' : 
'org.apache.cassandra.io.compress.LZ4Compressor' }AND default_time_to_live = 
0AND speculative_retry = '99.0PERCENTILE'AND min_index_interval = 128AND 
max_index_interval = 2048;stationsColumn TypeColumn NameData 
Typestation_iduuidsensorsfrozenmapuuid, 
frozenlive_data.geolocationAs 
CQL statementCREATE TABLE live_data.stations (station_id 
uuid,sensors frozenmapuuid, 
frozenlive_data.geolocation,PRIMARY KEY (station_id)) WITH 
read_repair_chance = 0.0AND dclocal_read_repair_chance = 0.1AND 
gc_grace_seconds = 864000AND bloom_filter_fp_chance = 0.01AND caching = { 
'keys' : 'ALL', 'rows_per_partition' : 'NONE' }AND comment = ''AND compaction = 
{ 'class' : 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy' 
}AND compression = { 'sstable_compression' : 
'org.apache.cassandra.io.compress.LZ4Compressor' }AND default_time_to_live = 
0AND speculative_retry = '99.0PERCENTILE'AND min_index_interval = 128AND 
max_index_interval = 2048];<...> but was:<...ndex_interval = 
2048[AND memtable_flush_period_in_ms = 0;complex_table's 
indicesNameTargetclustering2idxclustering2idx1indexed1idx2indexed2keys_map_idxkeys(key_indexed_map)pk2idxpk2As CQL 
statementCREATE INDEX clustering2idx ON 
live_data.complex_table (clustering2);CREATE INDEX idx1 ON 
live_data.complex_table (indexed1);CREATE INDEX idx2 ON live_data.complex_table 
(indexed2);CREATE INDEX keys_map_idx ON live_data.complex_table 
(keys(key_indexed_map));CREATE INDEX pk2idx ON live_data.complex_table 
(pk2);sensor_dataColumn TypeColumn NameData 
Typesensor_iduuidmonthintcharacteristicsmaptext, 
textmodel_numbertextprovidertextdatetimestampvaluedoubleAs CQL 
statementCREATE TABLE live_data.sensor_data 
(sensor_id uuid,month int,date timestamp,characteristics maptext, text 
static,model_number text static,provider text static,value double,PRIMARY KEY 
((sensor_id, month), date)) WITH CLUSTERING ORDER BY (date DESC)AND 
read_repair_chance = 0.0AND dclocal_read_repair_chance = 0.1AND 
gc_grace_seconds = 864000AND bloom_filter_fp_chance = 0.01AND caching = { 
'keys' : 'ALL', 'rows_per_partition' : 'NONE' }AND comment = ''AND compaction = 
{ 'class' : 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy' 
}AND compression = { 'sstable_compression' : 
'org.apache.cassandra.io.compress.LZ4Compressor' }AND default_time_to_live = 
0AND speculative_retry = '99.0PERCENTILE'AND min_index_interval = 128AND 
max_index_interval = 2048AND memtable_flush_period_in_ms = 
0;stationsColumn TypeColumn NameData 
Typestation_iduuidsensorsfrozenmapuuid, 
frozenlive_data.geolocationAs 
CQL statementCREATE TABLE live_data.stations (station_id 
uuid,sensors frozenmapuuid, 
frozenlive_data.geolocation,PRIMARY KEY (station_id)) WITH 
read_repair_chance = 0.0AND dclocal_read_repair_chance = 0.1AND 
gc_grace_seconds = 864000AND bloom_filter_fp_chance = 0.01AND caching = { 
'keys' : 'ALL', 'rows_per_partition' : 'NONE' }AND comment 

[jira] [Created] (ZEPPELIN-4351) Broken test after ZEPPELIN-4311

2019-09-25 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4351:
--

 Summary: Broken test after ZEPPELIN-4311
 Key: ZEPPELIN-4351
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4351
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee moon soo


Test broken after

https://issues.apache.org/jira/browse/ZEPPELIN-4311

 
{code:java}
Failed tests: 
  InterpreterRestApiTest.testRestartInterpreterPerNote:308 expected:<...y">
markdown
[
]> but was:<...y">
markdown
[]>
 {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4349) Flaky test - org.apache.zeppelin.python.IPythonInterpreterTest.testIPythonPlotting

2019-09-24 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4349:
--

 Summary: Flaky test - 
org.apache.zeppelin.python.IPythonInterpreterTest.testIPythonPlotting
 Key: ZEPPELIN-4349
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4349
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


[https://api.travis-ci.org/v3/job/589060103/log.txt]
{code:java}
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.611 sec <<< 
FAILURE! - in org.apache.zeppelin.python.IPythonInterpreterTest
testIPythonPlotting(org.apache.zeppelin.python.IPythonInterpreterTest)  Time 
elapsed: 4.674 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<3>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at 
org.apache.zeppelin.python.IPythonInterpreterTest.testIPythonPlotting(IPythonInterpreterTest.java:234)

Running org.apache.zeppelin.python.PythonDockerInterpreterTest
 WARN [2019-09-24 20:54:09,148] ({Exec Default Executor} 
ProcessLauncher.java[onProcessFailed]:111) - Process is failed due to 
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
 INFO [2019-09-24 20:54:09,148] ({Exec Default Executor} 
ProcessLauncher.java[transition]:86) - Process state is transitioned to 
TERMINATED
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
org.apache.zeppelin.python.PythonDockerInterpreterTest

Results :

Failed tests: 
  IPythonInterpreterTest.testIPythonPlotting:234 expected:<2> but was:<3>

Tests run: 33, Failures: 1, Errors: 0, Skipped: 0 {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4348) Flaky test - ZeppelinSparkClusterTest.zRunTest

2019-09-24 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4348:
--

 Summary: Flaky test - ZeppelinSparkClusterTest.zRunTest
 Key: ZEPPELIN-4348
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4348
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


{code:java}

20:33:30,993 ERROR org.apache.thrift.server.TThreadPoolServer:315 - Thrift 
error occurred during processing of message.
org.apache.thrift.transport.TTransportException
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86)
at 
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:425)
at 
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:321)
at 
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:225)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:27)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:310)
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)
20:33:30,993  WARN 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:141 - 
ignore the exception when shutting down
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.callRemoteFunction(RemoteInterpreterProcess.java:122)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess.stop(RemoteInterpreterManagedProcess.java:133)
at 
org.apache.zeppelin.interpreter.ManagedInterpreterGroup.close(ManagedInterpreterGroup.java:106)
at 
org.apache.zeppelin.interpreter.ManagedInterpreterGroup.close(ManagedInterpreterGroup.java:88)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.thrift.transport.TTransportException
at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86)
at 
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:425)
at 
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:321)
at 
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:225)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:77)
at 
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.recv_shutdown(RemoteInterpreterService.java:347)
at 
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.shutdown(RemoteInterpreterService.java:335)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess$1.call(RemoteInterpreterManagedProcess.java:136)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess$1.call(RemoteInterpreterManagedProcess.java:133)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.callRemoteFunction(RemoteInterpreterProcess.java:118)
... 4 more
20:33:30,996  INFO 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:147 - 
Remote process terminated
20:33:30,997  INFO org.apache.zeppelin.rest.AbstractTestRestApi:303 - 
Terminating test Zeppelin...
20:33:31,004  INFO org.eclipse.jetty.server.AbstractConnector:341 - Stopped 
ServerConnector@49d8e094{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
20:33:31,004  WARN 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:233 - 
Process is exited with exit value 0
20:33:31,005  INFO org.apache.zeppelin.interpreter.util.ProcessLauncher:86 - 
Process state is transitioned to COMPLETED
20:33:31,005  INFO org.eclipse.jetty.server.session:167 - node0 Stopped 
scavenging
20:33:31,032  INFO org.eclipse.jetty.server.handler.ContextHandler:1045 - 
Stopped 
o.e.j.w.WebAppContext@6a7e1738{zeppelin-web,/,file:///home/travis/build/Leemoonsoo/zeppelin/zeppelin-web/dist/,UNAVAILABLE}
20:33:33,036  INFO org.apache.zeppelin.rest.AbstractTestRestApi:367 - 
Connecting to http://localhost:8080/api/version
20:33:33,037  INFO org.apache.commons.httpclient.HttpMethodDirector:439 - I/O 
exception (java.net.ConnectException) caught when processing request: 
Connection refused (Connection refused)
20:33:33,038  INFO org.apache.commons.httpclient.HttpMethodDirector:445 - 
Retrying request
20:33:33,038  INFO org.apache.commons.httpclient.HttpMethodDirector:439 - I/O 
exception (java.net.ConnectException) caught when processing request: 
Connection refused (Connection refused)
20:33:33,038  INFO org.apache.commons.httpclient.HttpMethodDirector:445 - 
Retrying request
20:33:33,039  INFO

Re: [DISCUSS] Release 0.8.2

2019-09-24 Thread moon soo Lee
+1

On Mon, Sep 23, 2019 at 8:16 PM Prabhjyot Singh 
wrote:

> +1
>
> I see a lot of issues are fixed in the past few months. This sounds a
> good intermediate step before 0.9 release.
>
> On Tue, 24 Sep 2019 at 00:23, Eric Pugh 
> wrote:
>
>> The iPython related fixes would address some issues I’ve run into!
>>
>> On Sep 22, 2019, at 11:31 PM, Jeff Zhang  wrote:
>>
>> Hi Folks,
>>
>> 0.8.1 is released half year ago (Jan 2019), I'd to start the discussion
>> about releasing of 0.8.2 which fixed several critical issues. Let me know
>> your thoughts, thanks.
>>
>>
>> https://jira.apache.org/jira/issues/?jql=project%20%3D%20ZEPPELIN%20AND%20fixVersion%20%3D%200.8.2
>>
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>>
>> ___
>> *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467
>> | http://www.opensourceconnections.com | My Free/Busy
>> 
>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed
>> 
>> This e-mail and all contents, including attachments, is considered to be
>> Company Confidential unless explicitly stated otherwise, regardless
>> of whether attachments are marked as such.
>>
>>
>
> --
> Regards,
> Prabhjyot Singh
>


[jira] [Created] (ZEPPELIN-4339) Flaky tests org.apache.zeppelin.AbstractZeppelinIT#testAngularDisplay

2019-09-19 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4339:
--

 Summary: Flaky tests 
org.apache.zeppelin.AbstractZeppelinIT#testAngularDisplay
 Key: ZEPPELIN-4339
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4339
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
 Attachments: image-2019-09-19-15-15-38-804.png

Flaky test 

 

19:41:34,777 ERROR org.apache.zeppelin.AbstractZeppelinIT:142 - Exception in 
ZeppelinIT while testAngularDisplay org.openqa.selenium.TimeoutException: 
Expected condition failed: waiting for 
org.apache.zeppelin.AbstractZeppelinIT$1@5c530d1e (tried for 120 second(s) with 
1 SECONDS interval) at 
org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:263) 
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231) at 
org.apache.zeppelin.AbstractZeppelinIT.pollingWait(AbstractZeppelinIT.java:99) 
at 
org.apache.zeppelin.AbstractZeppelinIT.waitForParagraph(AbstractZeppelinIT.java:73)
 at 
org.apache.zeppelin.integration.ZeppelinIT.testAngularDisplay(ZeppelinIT.java:108)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498) at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
at org.junit.rules.Verifier$1.evaluate(Verifier.java:35) at 
org.junit.rules.RunRules.evaluate(RunRules.java:20) at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at 
org.junit.runners.ParentRunner.run(ParentRunner.java:363) at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) 
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) 
Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate 
element: 
\{"method":"xpath","selector":"(//div[@ng-controller=\"ParagraphCtrl\"])[3]//div[contains(@class,
 'control')]//span[2][contains(.,'FINISHED')]"} Command duration or timeout: 0 
milliseconds at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method) at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
 at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at 
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) 
at 
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
 at 
org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
 at 
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
 at 
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
 at 
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
 at 
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
 at 
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601) at 
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:371)
 at 
org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:473)
 at org.openqa.selenium.By$ByXPath.findElement(By.java:361) at 
org.openqa.selenium.remote.Re

[jira] [Created] (ZEPPELIN-4338) Docker image build error

2019-09-19 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4338:
--

 Summary: Docker image build error
 Key: ZEPPELIN-4338
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4338
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0, 0.8.2


Docker image build error with /script/docker/zeppelin/bin/Dockerfile

 
{code:java}
After this operation, 103 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  r-base-core r-cran-boot r-cran-cluster r-cran-foreign r-cran-mass
  r-cran-kernsmooth r-cran-lattice r-cran-nlme r-cran-matrix r-cran-mgcv
  r-cran-rpart r-cran-survival r-cran-class r-cran-nnet r-cran-spatial
  r-cran-codetools r-recommended r-base r-base-dev r-base-html r-doc-html
E: There were unauthenticated packages and -y was used without 
--allow-unauthenticated
The command '/bin/sh -c echo "$LOG_TAG Install R related packages" &&     echo 
"deb http://cran.rstudio.com/bin/linux/ubuntu xenial/" | tee -a 
/etc/apt/sources.list &&     gpg --keyserver keyserver.ubuntu.com --recv-key 
E084DAB9 &&     gpg -a --export E084DAB9 | apt-key add - &&     apt-get -y 
update &&     apt-get -y install r-base r-base-dev &&     R -e 
"install.packages('knitr', repos='http://cran.us.r-project.org')" &&     R -e 
"install.packages('ggplot2', repos='http://cran.us.r-project.org')" &&     R -e 
"install.packages('googleVis', repos='http://cran.us.r-project.org')" &&     R 
-e "install.packages('data.table', repos='http://cran.us.r-project.org')" &&    
 apt-get -y install libcurl4-gnutls-dev libssl-dev &&     R -e 
"install.packages('devtools', repos='http://cran.us.r-project.org')" &&     R 
-e "install.packages('Rcpp', repos='http://cran.us.r-project.org')" &&     
Rscript -e "library('devtools'); library('Rcpp'); 
install_github('ramnathv/rCharts')"' returned a non-zero code: 100{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ZEPPELIN-4333) Escape popup dialog title and message

2019-09-17 Thread Lee moon soo (Jira)
Lee moon soo created ZEPPELIN-4333:
--

 Summary: Escape popup dialog title and message
 Key: ZEPPELIN-4333
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4333
 Project: Zeppelin
  Issue Type: Task
  Components: front-end
Affects Versions: 0.8.1
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.8.2


There're couple of places we're not escaping contents of popup dialog (title, 
message)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: [VOTE] Creating feature branch for zeppelin new ui initiative

2019-09-09 Thread moon soo Lee
+1
Looking forward to

On Thu, Sep 5, 2019 at 10:48 PM Xun Liu  wrote:

> +1
> Very looking forward to
>
> Xun Liu
> Best Regards
>
> > On Sep 6, 2019, at 11:18 AM, Jongyoul Lee  wrote:
> >
> > +1
> >
> > On Thu, Sep 5, 2019 at 10:17 PM Jeff Zhang  wrote:
> >
> >> Just to be clear that this thread is about voting of creating separated
> >> feature branch. Regarding merging this into master, we can discuss it
> >> later. Because previously we also thought about moving frontend code
> out of
> >> zeppelin project into subproject. So that there could be multiple
> frontend
> >> implementations, each of them in different subproject.
> >>
> >>
> >> Jeff Zhang  于2019年9月5日周四 上午10:33写道:
> >>
> >>>
> >>> Hi all,
> >>>
> >>> There's one thread [1] discussing about the new zeppelin ui initiative.
> >> It
> >>> looks like the community have reach consensus on this.
> >>>
> >>> Considering this is a large effort and most of work is on frontend, I
> >>> would suggest to create a new feature branch for this initiative. So
> that
> >>> the development of this initiative can move fast and without breaking
> the
> >>> current master branch. Later at proper time, we can consider to merge
> it
> >>> back into master branch, since the most of the work is in frontend, I
> >>> believe the merge won't be too difficult. Let's vote for creating
> feature
> >>> branch for this. Here's my +1
> >>>
> >>>
> >>> [1]
> >>>
> >>
> https://lists.apache.org/thread.html/6ba4722d6eab70366d11bc43d727ca51a4539446e34d24ed7578b00c@%3Cusers.zeppelin.apache.org%3E
> >>>
> >>>
> >>>
> >>> --
> >>> Best Regards
> >>>
> >>> Jeff Zhang
> >>>
> >>
> >>
> >> --
> >> Best Regards
> >>
> >> Jeff Zhang
> >>
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
>
>
>


Re: [DISCUSS] Notebook serving

2019-04-26 Thread moon soo Lee
Hi,

Although https://github.com/apache/zeppelin/pull/3356/files implements the
basic functionality of the design,
few key features are not yet implemented and many things can be improved.
Also we can even expand the scope, like,

 - Scaling (or autoscaling) serving is not yet implemented. Need to design
how we want to scale (manually by chaning # of replica or using autoscaling
using horizontal autoscaler, or maybe both?)
 - Routing table generation is based on periodic polling of services. Can
be improved by using watch api in kubernetes.
 - Notebook serving design take care of Testing of notebook because we can
not think serving notebook in production without test. But what about Code
review? do we need? if yes, how do we want to handle this for notebooks?
 - We have Test task and Serving task. Do we also need Training for Machine
learning use case?
 - Serving task runs at least one ZeppelinServer and an Interpreter JVM
process. Will there be a way to reduce memory footprint? like a
using graalvm in the container. So hundreds and thousands of small models
can be deployed without much overhead.
 - Every component, TestTask, ServingTask, ContextStorage, MetricStorage
are pluggable. Good! And do we need additional implementation for them?
currently Kubernetes environment is default implementation for all of the
component, but how about integrate with other popular software frameworks?
like Kubeflow, TensroflowServing, etc?

I think there are a lot of interesting topics beyond the pullrequest I
made. So, hope this be part of GSoC.

Thanks,
moon

On Fri, Apr 26, 2019 at 1:50 AM Dragos Dublea 
wrote:

> Hello,
>
> Happy Day!
>
> It is great to follow the improvements on this topic in this Pull Request
> <https://github.com/apache/zeppelin/pull/3356/files>.
> Is this project not going to be the part of GSoC any further? Is there a
> scope for FE as a part of GSoC?
>
> Thanks,
>
>
>
> On Tue, 16 Apr 2019 at 23:06, moon soo Lee  wrote:
>
> > Hi,
> >
> > You're right. I joined the program as a mentor.
> > Thanks again for the interest to the project and to this topic.
> >
> > Thanks,
> > moon
> >
> > On Sat, Apr 13, 2019 at 8:50 AM Dragos Dublea <
> dubleadragos2...@gmail.com>
> > wrote:
> >
> >> Hello,
> >>
> >> I will be very glad to take up any subtasks or participate in a
> >> discussion about this project if you get time for the discussion.
> >>
> >> As I will begin with my vacation soon, I am excited to work on this
> >> project with the Zeppelin community.
> >>
> >> Thank you
> >>
> >> On Wed, Apr 10, 2019, 4:03 PM Dragos Dublea  >
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> Thank you so much for your reply. AFAIK, Only the student signup period
> >>> is over. Mentors can still join the program. They will have to receive
> an
> >>> invite from the organization admins. Here, in this case, Apache
> Software
> >>> Foundation org admins will have to send the invite link to enable your
> >>> signup.
> >>>
> >>> Thanks again
> >>>
> >>>
> >>>
> >>> On Wed, 10 Apr 2019 at 13:23, moon soo Lee  wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Thanks for the interest in this topic. I realized mentor sign up
> period
> >>>> is
> >>>> finished.
> >>>> Let me see if there's a way to add myself as a GsoC mentor or any
> other
> >>>> alternative.
> >>>>
> >>>> Regards,
> >>>> moon
> >>>>
> >>>> On Tue, Apr 9, 2019 at 9:55 PM Dragos Dublea <
> >>>> dubleadragos2...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> > Hello,
> >>>> >
> >>>> > This is a very interesting topic. I did go through the design doc.
> >>>> Can you
> >>>> > please mentor me to implement this? I am very much interested in
> >>>> taking it
> >>>> > up.
> >>>> >
> >>>> > Thanks
> >>>> >
> >>>> > On 2019/03/26 21:31:16, moon soo Lee  wrote:
> >>>> > > Hi,>
> >>>> > >
> >>>> > > There're some challenges bringing a model inside notebook to a
> >>>> > production>
> >>>> >
> >>>> > > environment.>
> >>>> > > Many many organizations, the most common practice I see today is
> >&

Re: New committer: Liu Xun

2019-04-17 Thread moon soo Lee
Congrats Liu Xun and welcome!


On Wed, Apr 17, 2019 at 8:17 PM Jeff Zhang  wrote:

> The Project Management Committee (PMC) for Apache Zeppelin
> has invited Liu Xun to become a committer and we are pleased
> to announce that he has accepted.
>
> Thanks Liu Xun's contribution to apache zeppelin.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> --
> Best Regards
>
> Jeff Zhang
>


Re: [DISCUSS] Notebook serving

2019-04-16 Thread moon soo Lee
Hi,

You're right. I joined the program as a mentor.
Thanks again for the interest to the project and to this topic.

Thanks,
moon

On Sat, Apr 13, 2019 at 8:50 AM Dragos Dublea 
wrote:

> Hello,
>
> I will be very glad to take up any subtasks or participate in a discussion
> about this project if you get time for the discussion.
>
> As I will begin with my vacation soon, I am excited to work on this
> project with the Zeppelin community.
>
> Thank you
>
> On Wed, Apr 10, 2019, 4:03 PM Dragos Dublea 
> wrote:
>
>> Hello,
>>
>> Thank you so much for your reply. AFAIK, Only the student signup period
>> is over. Mentors can still join the program. They will have to receive an
>> invite from the organization admins. Here, in this case, Apache Software
>> Foundation org admins will have to send the invite link to enable your
>> signup.
>>
>> Thanks again
>>
>>
>>
>> On Wed, 10 Apr 2019 at 13:23, moon soo Lee  wrote:
>>
>>> Hi,
>>>
>>> Thanks for the interest in this topic. I realized mentor sign up period
>>> is
>>> finished.
>>> Let me see if there's a way to add myself as a GsoC mentor or any other
>>> alternative.
>>>
>>> Regards,
>>> moon
>>>
>>> On Tue, Apr 9, 2019 at 9:55 PM Dragos Dublea >> >
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > This is a very interesting topic. I did go through the design doc. Can
>>> you
>>> > please mentor me to implement this? I am very much interested in
>>> taking it
>>> > up.
>>> >
>>> > Thanks
>>> >
>>> > On 2019/03/26 21:31:16, moon soo Lee  wrote:
>>> > > Hi,>
>>> > >
>>> > > There're some challenges bringing a model inside notebook to a
>>> > production>
>>> >
>>> > > environment.>
>>> > > Many many organizations, the most common practice I see today is
>>> > something>
>>> > > like>
>>> > >
>>> > > 1. Data scientist develop a model in a data science notebook.>
>>> > > 2. SW engineer rewrites the model, to meet the production
>>> requirements.>
>>> > >
>>> > > In other words, data scientists do not have self-service capability.
>>> And>
>>> > > the organization is spending a lot of time for reimplementing model
>>> for>
>>> > > production.>
>>> > >
>>> > > I tried to identify the gaps between data science notebook and
>>> > production>
>>> >
>>> > > environment, and what can possibly address them. So models that
>>> created
>>> > by>
>>> > > data scientists in the notebook can go production with minimum
>>> efforts.>
>>> > >
>>> > > I made a proposal to solve this problem. Please review and comment.
>>> Any>
>>> > > ideas and feedbacks are welcome. You can make a modification if
>>> needed.>
>>> > >
>>> >
>>> >
>>> https://docs.google.com/document/d/1YA6q8W9yO8a88xzLDYs9zv_fKu2_cnB58rmQbakxi1I/edit?usp=sharing
>>> > >
>>> > >
>>> > > This document is linked from>
>>> > > https://issues.apache.org/jira/browse/ZEPPELIN-3994>
>>> > >
>>> > > Thanks,>
>>> > > moon>
>>> > >
>>> >
>>>
>>


Re: 0.8.2-SNAPSHOT: WebSocket Write EOF 1006

2019-04-10 Thread moon
>
> NotebookServer.java[onClose]:372) - Closed connection to 10.39.227.226 :
> 58950. (1006) WebSocket Write EOF


Looks like this is connection error between browser and ZeppelinServer.
Do you see any other log or particular behavior when you experience the
problem?

Thanks,
moon

On Thu, Mar 28, 2019 at 7:34 AM J.Dadashev  wrote:

> Hello,
>
> I have created a docker container based on Python 3.7 with matplotlib and
> some other libraries.
> Here is my Dockerfile:
>
> RUN apt-get update
> RUN pip install --upgrade pip
> RUN pip install numpy pandas scipy matplotlib
> RUN apt-get install -y libaio-dev
> RUN apt-get clean
>
> I build the image:
> docker build --build-arg http_proxy=http://host:port --build-arg
> https_proxy=http:// host:port -t custompy37 .
>
> Then I activate my docker container:
> %python.docker activate custompy37
>
> Then I run the attached notebook multiple times.
>
> Eventually I get the error below:
>
> NotebookServer.java[onClose]:372) - Closed connection to 10.39.227.226 :
> 58950. (1006) WebSocket Write EOF
>
> Questions:
> 1) Is it a known issue
> 2) What causes that?
>
> Thanks,
> Jim
>
>


Re: [DISCUSS] Notebook serving

2019-04-10 Thread moon soo Lee
Hi,

Thanks for the interest in this topic. I realized mentor sign up period is
finished.
Let me see if there's a way to add myself as a GsoC mentor or any other
alternative.

Regards,
moon

On Tue, Apr 9, 2019 at 9:55 PM Dragos Dublea 
wrote:

> Hello,
>
> This is a very interesting topic. I did go through the design doc. Can you
> please mentor me to implement this? I am very much interested in taking it
> up.
>
> Thanks
>
> On 2019/03/26 21:31:16, moon soo Lee  wrote:
> > Hi,>
> >
> > There're some challenges bringing a model inside notebook to a
> production>
>
> > environment.>
> > Many many organizations, the most common practice I see today is
> something>
> > like>
> >
> > 1. Data scientist develop a model in a data science notebook.>
> > 2. SW engineer rewrites the model, to meet the production requirements.>
> >
> > In other words, data scientists do not have self-service capability. And>
> > the organization is spending a lot of time for reimplementing model for>
> > production.>
> >
> > I tried to identify the gaps between data science notebook and
> production>
>
> > environment, and what can possibly address them. So models that created
> by>
> > data scientists in the notebook can go production with minimum efforts.>
> >
> > I made a proposal to solve this problem. Please review and comment. Any>
> > ideas and feedbacks are welcome. You can make a modification if needed.>
> >
>
> https://docs.google.com/document/d/1YA6q8W9yO8a88xzLDYs9zv_fKu2_cnB58rmQbakxi1I/edit?usp=sharing
> >
> >
> > This document is linked from>
> > https://issues.apache.org/jira/browse/ZEPPELIN-3994>
> >
> > Thanks,>
> > moon>
> >
>


[jira] [Created] (ZEPPELIN-4100) Builtin visualization enhanced streaming support

2019-03-29 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-4100:
--

 Summary: Builtin visualization enhanced streaming support
 Key: ZEPPELIN-4100
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4100
 Project: Zeppelin
  Issue Type: Task
Affects Versions: 0.8.1
Reporter: Lee moon soo
 Fix For: 0.9.0


ZEPPELIN-3340 introduced support for streaming data visualization.

However, has some limitations like
 # Initial chart selection and setup required
 # Switching visualization during progress is not possible
 # Multiple paragraphs in a note cannot be updated in real-time (while multiple 
paragraphs cannot run concurrently).

 

This issue will address limitation 1, 2, 3. So a note can have multiple 
visualizations that updated in real-time, with capabilities to change chart 
type on the fly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[DISCUSS] Notebook serving

2019-03-26 Thread moon soo Lee
Hi,

There're some challenges bringing a model inside notebook to a production
environment.
Many many organizations, the most common practice I see today is something
like

1. Data scientist develop a model in a data science notebook.
2. SW engineer rewrites the model, to meet the production requirements.

In other words, data scientists do not have self-service capability. And
the organization is spending a lot of time for reimplementing model for
production.

I tried to identify the gaps between data science notebook and production
environment, and what can possibly address them. So models that created by
data scientists in the notebook can go production with minimum efforts.

I made a proposal to solve this problem. Please review and comment. Any
ideas and feedbacks are welcome. You can make a modification if needed.
https://docs.google.com/document/d/1YA6q8W9yO8a88xzLDYs9zv_fKu2_cnB58rmQbakxi1I/edit?usp=sharing

This document is linked from
https://issues.apache.org/jira/browse/ZEPPELIN-3994

Thanks,
moon


Re: Zeppelin in GSOC 2019

2019-03-04 Thread moon soo Lee
Hi,

Great to see your interest to project. Thanks!
Looks like we need volunteers for a mentor and some backend subject for
GSoC2019.
Any ideas?

Best,
moon




On Mon, Mar 4, 2019 at 3:05 PM Vasiliy Morkovkin 
wrote:

> Hi everyone, I'm pursuing bachelor degree at Moscow institute of physics
> and technology and eager to contribute to Zeppelin in context of GSOC
> 2019. I've become a real fan of Zeppelin over the past couple of months,
> using it at my job. But I have found out only one ticket (front-end
> task) with label of GSOC 2019 on your Jira. Perhaps you may have any
> ideas for new features or improvements in Zeppelin, but you don't have
> enough hands on them. It would be wonderful if anyone agreed to mentor
> these ideas within GSOC :)
> Currently I am in a position of Scala developer (back-end) for 1.5 year.
> I also can write in Java or Python without any problems if necessary.
> Really fond of databases and highload. Also I have experience with some
> other great Apache projects like Cassandra, Kafka and Spark.
>
> Best regards, Basil Morkovkin.
>
>


[jira] [Created] (ZEPPELIN-4024) Dark theme

2019-02-26 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-4024:
--

 Summary: Dark theme
 Key: ZEPPELIN-4024
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4024
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo


Who don't want dark theme? :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-4023) Document note file conversion from 0.8 -> 0.9

2019-02-26 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-4023:
--

 Summary: Document note file conversion from 0.8 -> 0.9
 Key: ZEPPELIN-4023
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4023
 Project: Zeppelin
  Issue Type: Task
  Components: documentation
Reporter: Lee moon soo
 Fix For: 0.9.0


Since 0.9.0 changes note file naming convention, how to convert existing note 
files need to be documented and well explained from install / upgrade section.
 * Include note file naming convention change on release note
 * Explain how to convert old files to newer version in 
docs/setup/operation/upgrading.md
 * Add docs for property zeppelin.notebook.new_format.convert and 
zeppelin.notebook.new_format.delete_old introduced 
[https://github.com/apache/zeppelin/pull/3189]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-4022) Release 0.9.0

2019-02-26 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-4022:
--

 Summary: Release 0.9.0
 Key: ZEPPELIN-4022
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4022
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
 Fix For: 0.9.0


Umbrella issue that tracks release 0.9.0.

Please link any blockers here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-4004) RemoteResource.invokeMethod() has broken

2019-02-13 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-4004:
--

 Summary: RemoteResource.invokeMethod() has broken
 Key: ZEPPELIN-4004
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4004
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Lee moon soo
Assignee: Lee moon soo


RemoteResource is a representation of object in ResourcePool in Interpreter 
running on another process.

RemoteResource provides a invokeMethod() to call method of an object remotely, 
which is not working now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: ipython

2019-02-07 Thread moon
Great question.

with Zeppelin-0.8.x, IPython server (in Python interpreter) can run inside
its own docker container.
You can check
http://zeppelin.apache.org/docs/0.8.1/interpreter/python.html#docker to see
how it works.

with Zeppelin-0.9.x (not released yet, build from source), all interpreter
including Zeppelin itself can run in the container on Kubernetes.
You can check
http://zeppelin.apache.org/docs/0.9.0-SNAPSHOT/quickstart/kubernetes.html
to see how it works.

Hope this helps.

Thanks,
moon

On Mon, Feb 4, 2019 at 12:52 PM  wrote:

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


[jira] [Created] (ZEPPELIN-3994) Notebook serving

2019-02-07 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3994:
--

 Summary: Notebook serving
 Key: ZEPPELIN-3994
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3994
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee moon soo


h2. Motivation

Notebook is useful for interactive analysis. But bringing a model in a Note to 
production is another challenge. Often, we see two approaches

a. Call paragraph using Rest API to ZeppelinServer
b. Reimplement model outside the notebook and deploy it without using Zeppelin.

Approach a) brings some headache because of Zeppelin server is not fault 
tolerant and can be restarted at any moment intentionally (for changing 
configuration, etc). Also notebook to be run through REST API can be changed at 
any time without notice.

Approach b) has a clear down side. "re-implementation".

So, It'll be great if a Note can be deployed independently from ZeppelinServer 
with RestAPI endpoint, with high availability support. It makes following 
usecase really easy and reliable for production use
 # Create model in Zeppelin (or any function)
 # Click deploy button in a Note
 # Access model (any function) using REST api.

h2. Requirements
 * Note can be deployed through GUI in a single click ('Deploy' button on every 
Note)
 * Once Note is deployed, it runs independently from ZeppelinServer. Deployed 
Note should keep up and running even if ZeppelinServer is restarting/stopped.
 * ZeppelinServer provide a GUI to manage deployments
 * Deployed note should be highly available.
 * Runs on Kubernetes

h2. Design
h3. Deploy button

Each note have a 'Deploy' button.
h3. On deploy button click

On 'Deploy' button click, following will happen.
 * ZeppelinServer creates a new Pod
 ** The pod snapshot Notebook directory mount it.
 ** The pod runs another ZeppelinServer
 ** Current login session information is transferred to the new ZeppelinServer
 * ZeppelinServer in a new Pod runs paragraphs in the Note

 ** Depends on Note, it'll run multiple interpreters.
 ** Interpreters are running in Kubernetes Deployment Resource instead of Pod 
resource.
 * Once all paragraphs are successfully run, delete a new ZeppelinServer Pod 
and all other Interpreter Deployment resource except for default Interpreter 
Deployment resource of the Note.

For  example, when A note has Markdown and Python paragraph with python as 
default interpreter of a Note, then ZeppelinServer, python and Markdown 
interpreter will be created after 'deploy' button click, but ZeppelinServer and 
Markdown interpreter will be terminated after successful note run. And Python 
interpreter will be remained for serving.

h3. Register model (or any function) to be served

Each interpreter has a 
[ResourcePool|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/ResourcePool.java].
 And ResourcePool is programmatically accessible by enduser. For example, user 
can register arbitrary object into ResourcePool using API.
{code:java}
%spark
val myModel = 
z.put("model_1", myModel){code}
h3. Access model (or any function) from Rest api Endpoint

Every object registered in the ResourcePool is wrapped by 
[Resource|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/Resource.java#L151].
 Resource provide method invocation using 
[Resource.invokeMethod()|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/Resource.java#L151].

RemoteInterpreterServer provide a rest api endpoint to call method of Resource 
in its ResourcePool. Such as
{code:java}
//{code}
and pass parameters of method using POST param or something.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3989) Configure IPython Interpreter in Docker image

2019-02-03 Thread Lee moon soo (JIRA)
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)


[jira] [Created] (ZEPPELIN-3988) Text output include '\r' char does not displayed correctly

2019-02-03 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3988:
--

 Summary: Text output include '\r' char does not displayed correctly
 Key: ZEPPELIN-3988
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3988
 Project: Zeppelin
  Issue Type: Task
Affects Versions: 0.8.0
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.8.1


Text output '\r' is not displayed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3982) Document how to setup development environment for Zeppelin on Kubernetes

2019-02-01 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3982:
--

 Summary: Document how to setup development environment for 
Zeppelin on Kubernetes
 Key: ZEPPELIN-3982
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3982
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
Assignee: Lee moon soo


Explain how to setup development environment for Zeppelin on Kubernetes that 
enables local development without build package and docker image on every code 
change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3954) Use "kubectl create -f" instead of "kubectl apply -f"

2019-01-18 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3954:
--

 Summary: Use "kubectl create -f" instead of "kubectl apply -f"
 Key: ZEPPELIN-3954
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3954
 Project: Zeppelin
  Issue Type: Improvement
  Components: Kubernetes
    Reporter: Lee moon soo


Use "kubectl create -f" instead of "kubectl apply -f" on creating interpreter 
pod.
 Possible problem explained in [this 
comment|https://github.com/apache/zeppelin/pull/3240#discussion_r248567845].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3868) Quick start menu link broken in the website

2018-11-16 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3868:
--

 Summary: Quick start menu link broken in the website
 Key: ZEPPELIN-3868
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3868
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee moon soo
Assignee: Lee moon soo


Quickstart menu item link has broken.

For example go to page
https://zeppelin.apache.org/community.html

and then click "QuickStart" on the menu.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3854) Flaky test - org.apache.zeppelin.scheduler.RemoteSchedulerTest.testAbortOnPending

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3854:
--

 Summary: Flaky test - 
org.apache.zeppelin.scheduler.RemoteSchedulerTest.testAbortOnPending
 Key: ZEPPELIN-3854
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3854
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


https://api.travis-ci.org/v3/job/446566408/log.txt

{code}
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.265 sec <<< 
FAILURE! - in org.apache.zeppelin.scheduler.RemoteSchedulerTest
testAbortOnPending(org.apache.zeppelin.scheduler.RemoteSchedulerTest)  Time 
elapsed: 7.019 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.zeppelin.scheduler.RemoteSchedulerTest.testAbortOnPending(RemoteSchedulerTest.java:258)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3853) Flaky test - IPySparkInterpreterTest

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3853:
--

 Summary: Flaky test - IPySparkInterpreterTest
 Key: ZEPPELIN-3853
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3853
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


IPySparkInterpreterTest
https://api.travis-ci.org/v3/job/446566416/log.txt

{code}
08:35:39,940  INFO org.apache.zeppelin.python.IPythonInterpreter:334 - Kill 
IPython Process
08:35:39,946 ERROR io.grpc.internal.SerializingExecutor:126 - Exception while 
executing runnable 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed@64d7d2fe
java.lang.NullPointerException
at 
io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:434)
at 
io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at 
io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at 
io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at 
io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:678)
at 
io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at 
io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at 
io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at 
io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:403)
at 
io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
at 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546)
at 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467)
at 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:584)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at 
io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
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)
08:35:39,949  INFO org.apache.zeppelin.spark.NewSparkInterpreter:138 - Close 
SparkInterpreter
Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 194.415 sec <<< 
FAILURE! - in org.apache.zeppelin.spark.IPySparkInterpreterTest
testIPythonAdvancedFeatures(org.apache.zeppelin.spark.IPySparkInterpreterTest)  
Time elapsed: 35.429 sec  <<< ERROR!
java.lang.RuntimeException: Fail to open IPythonInterpreter
at 
org.apache.zeppelin.python.IPythonInterpreter.launchIPythonKernel(IPythonInterpreter.java:309)
at 
org.apache.zeppelin.python.IPythonInterpreter.open(IPythonInterpreter.java:148)
at 
org.apache.zeppelin.spark.IPySparkInterpreter.open(IPySparkInterpreter.java:66)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at 
org.apache.zeppelin.spark.IPySparkInterpreterTest.startInterpreter(IPySparkInterpreterTest.java:93)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3852) Flaky test - org.apache.zeppelin.helium.HeliumBundleFactoryTest

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3852:
--

 Summary: Flaky test - 
org.apache.zeppelin.helium.HeliumBundleFactoryTest
 Key: ZEPPELIN-3852
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3852
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


org.apache.zeppelin.helium.HeliumBundleFactoryTest sometimes hangs

{code}
Running org.apache.zeppelin.helium.HeliumBundleFactoryTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
02:51:04,445  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller:83 - Installing 
node version v6.9.1
02:51:04,448  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller:314 - Downloading 
https://nodejs.org/dist/v6.9.1/node-v6.9.1-linux-x64.tar.gz to 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/node-v6.9.1-linux-x64.tar.gz
02:51:04,450  INFO 
com.github.eirslett.maven.plugins.frontend.lib.ProxyConfig:27 - No proxies 
configured
02:51:04,450  INFO 
com.github.eirslett.maven.plugins.frontend.lib.FileDownloader:91 - No proxy was 
configured, downloading directly
02:51:05,810  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller:301 - Unpacking 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/node-v6.9.1-linux-x64.tar.gz
 into 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/node/tmp
02:51:06,641  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller:153 - Copying node 
binary from 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/node/tmp/node-v6.9.1-linux-x64/bin/node
 to 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/node/node
02:51:06,796  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller:182 - Installed 
node locally.
02:51:06,798  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NPMInstaller:117 - Installing 
npm version 3.10.8
02:51:06,798  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NPMInstaller:198 - Downloading 
http://registry.npmjs.org//npm/-/npm-3.10.8.tgz to 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/npm-3.10.8.tar.gz
02:51:06,799  INFO 
com.github.eirslett.maven.plugins.frontend.lib.ProxyConfig:27 - No proxies 
configured
02:51:06,799  INFO 
com.github.eirslett.maven.plugins.frontend.lib.FileDownloader:91 - No proxy was 
configured, downloading directly
02:51:06,912  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NPMInstaller:185 - Unpacking 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/npm-3.10.8.tar.gz
 into 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/node/node_modules
02:51:07,343  INFO 
com.github.eirslett.maven.plugins.frontend.lib.NPMInstaller:165 - Installed npm 
locally.
02:51:07,346  INFO 
com.github.eirslett.maven.plugins.frontend.lib.YarnInstaller:97 - Installing 
Yarn version v0.21.3
02:51:07,346  INFO 
com.github.eirslett.maven.plugins.frontend.lib.YarnInstaller:154 - Downloading 
https://github.com/yarnpkg/yarn/releases/download/v0.21.3/yarn-v0.21.3.tar.gz 
to 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/yarn-v0.21.3./yarn-v0.21.3.tar.gz
02:51:07,346  INFO 
com.github.eirslett.maven.plugins.frontend.lib.ProxyConfig:27 - No proxies 
configured
02:51:07,348  INFO 
com.github.eirslett.maven.plugins.frontend.lib.FileDownloader:91 - No proxy was 
configured, downloading directly
02:51:07,532  WARN org.apache.http.client.protocol.ResponseProcessCookies:129 - 
Invalid cookie header: "Set-Cookie: has_recent_activity=1; path=/; expires=Mon, 
05 Nov 2018 03:51:07 -". Invalid 'expires' attribute: Mon, 05 Nov 2018 
03:51:07 -
02:51:07,533  WARN org.apache.http.client.protocol.ResponseProcessCookies:129 - 
Invalid cookie header: "Set-Cookie: logged_in=no; domain=.github.com; path=/; 
expires=Fri, 05 Nov 2038 02:51:07 -; secure; HttpOnly". Invalid 'expires' 
attribute: Fri, 05 Nov 2038 02:51:07 -
02:51:08,002  INFO 
com.github.eirslett.maven.plugins.frontend.lib.YarnInstaller:141 - Unpacking 
/home/travis/build/apache/zeppelin/zeppelin-zengine/target/tmp/ZeppelinLTest_nodeCache/cache/yarn-v0.21.3./yarn-v0.21.3.tar.gz
 into 
/home/travis/build/apac

[jira] [Created] (ZEPPELIN-3851) Flaky test - LivyInterpreterIT

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3851:
--

 Summary: Flaky test - LivyInterpreterIT
 Key: ZEPPELIN-3851
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3851
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


Flaky test on 
 - LivyInterpreterIT.testPySparkInterpreter
 - 
LivyInterpreterIT.testSparkInterpreterWithDisplayAppInfo_StringWithoutTruncation
 - LivyInterpreterIT.testSparkInterpreter

{code}
18/11/05 02:59:45 INFO Client: Application report for 
application_1541386527524_0006 (state: ACCEPTED)
18/11/05 02:59:45 INFO Client: 
 client token: N/A
 diagnostics: N/A
 ApplicationMaster host: N/A
 ApplicationMaster RPC port: -1
 queue: default
 start time: 1541386785198
 final status: UNDEFINED
 tracking URL: 
http://travis-job-ebd07cc4-099c-4b69-be82-33e56b246eba:40966/proxy/application_1541386527524_0006/
 user: travis
18/11/05 02:59:45 INFO ShutdownHookManager: Shutdown hook called
18/11/05 02:59:45 INFO ShutdownHookManager: Deleting directory 
/tmp/spark-261368a3-9d39-4f78-92fa-88ff256924c9

YARN Diagnostics: 
Application killed by user.
at 
org.apache.zeppelin.livy.BaseLivyInterpreter.createSession(BaseLivyInterpreter.java:332)
at 
org.apache.zeppelin.livy.BaseLivyInterpreter.initLivySession(BaseLivyInterpreter.java:186)
at 
org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:163)
at 
org.apache.zeppelin.livy.LivyInterpreterIT.testSparkInterpreter(LivyInterpreterIT.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
 INFO [2018-11-05 03:01:10,292] ({main} LivyInterpreterIT.java[tearDown]:71) - 
Shutting down livy at 
http://travis-job-ebd07cc4-099c-4b69-be82-33e56b246eba:8998
Tests run: 6, Failures: 1, Errors: 2, Skipped: 0, Time elapsed: 366.203 sec <<< 
FAILURE! - in org.apache.zeppelin.livy.LivyInterpreterIT
testPySparkInterpreter(org.apache.zeppelin.livy.LivyInterpreterIT)  Time 
elapsed: 25.45 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.zeppelin.livy.LivyInterpreterIT.testPySparkInterpreter(LivyInterpreterIT.java:397)

testSparkInterpreterWithDisplayAppInfo_StringWithoutTruncation(org.apache.zeppelin.livy.LivyInterpreterIT)
  Time elapsed: 90.882 sec  <<< ERROR!
org.apache.zeppelin.interpreter.InterpreterException: Fail to create session, 
please check livy interpreter log and livy server log
at 
org.apache.zeppelin.livy.BaseLivyInterpreter.createSession(B

[jira] [Created] (ZEPPELIN-3850) "Run all paragraphs" button runs only the first paragraph on the note

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3850:
--

 Summary: "Run all paragraphs" button runs only the first paragraph 
on the note
 Key: ZEPPELIN-3850
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3850
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.9.0
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


On master branch, "Run all paragraphs" button runs only the first paragraph.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3849) Note id is displayed instead of name

2018-11-05 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3849:
--

 Summary: Note id is displayed instead of name
 Key: ZEPPELIN-3849
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3849
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.9.0
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


Note name is not displayed correctly after ZEPPELIN-2619



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3848) zeppelin-web dev mode does not work

2018-11-04 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3848:
--

 Summary: zeppelin-web dev mode does not work
 Key: ZEPPELIN-3848
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3848
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


zeppelin-web development mode `npm run dev` does not work with error.
{code:java}
module.js:471

    throw err;

    ^




Error: Cannot find module 'webpack/bin/config-yargs'

    at Function.Module._resolveFilename (module.js:469:15)

    at Function.Module._load (module.js:417:25)

    at Module.require (module.js:497:17)

    at require (internal/module.js:20:19)

    at Object. 
(/Users/moon/Projects/zeppelin/zeppelin-web/node_modules/webpack-dev-server/bin/webpack-dev-server.js:54:1)

    at Module._compile (module.js:570:32)

    at Object.Module._extensions..js (module.js:579:10)

    at Module.load (module.js:487:32)

    at tryModuleLoad (module.js:446:12)

    at Function.Module._load (module.js:438:3){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3840) Zeppelin on Kubernetes

2018-10-31 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3840:
--

 Summary: Zeppelin on Kubernetes
 Key: ZEPPELIN-3840
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3840
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


h2.  
h2. Goal

Make Zeppelin run on Kubernetes environment.

 - Run Zeppelin daemon as a Deployment, with RBAC to create/delete Pods for 
interpreters

 - Run Standard interpreters as Pods 

 - Run Spark interpreter with Spark Cluster deployed in Kubernetes cluster.
h2. How it works
 # Zeppelin-daemon is deployed in Kubernetes with necessary Role (RBAC).
e.g. kubectl apply -f ${ZEPPELIN_HOME}/k8s/zeppelin.yaml
 # Zeppelin-daemon automatically configure itself to use 
K8sStandardInterpreterLauncher, K8sSparkInterpreterLauncher instead of 
[StandardInterpreterLauncher|https://github.com/apache/zeppelin/blob/master/zeppelin-plugins/launcher/standard/src/main/java/org/apache/zeppelin/interpreter/launcher/StandardInterpreterLauncher.java],
 
[SparkInterpreterLauncher|https://github.com/apache/zeppelin/blob/master/zeppelin-plugins/launcher/spark/src/main/java/org/apache/zeppelin/interpreter/launcher/SparkInterpreterLauncher.java].
 ## K8sStandardInterpreterLauncher run an interpreter as a Pod
 ## K8sSparkInterpreterLauncher run spark interpreter with Spark cluster in the 
Kubernetes cluster.

So user can start to use Zeppelin on Kubernetes with zero configuration.

 

Customize the interpreter pod

User can easily modify, extend zeppelin.yaml as their needs. (like mount volume 
to persist configuration and notebook, etc) To provide the same customization 
capability to interpreter pod, Zeppelin stores interpreter pod spec (yaml) 
files in the directory "${ZEPPELIN_HOME}/k8s/interpreter/", and all yaml files 
in the directory. So user can modify pod spec file or add more.
h2. Spark interpreter in Kubernetes

Spark Interpreter not only runs itself in Kubernetes as a Pod, but also creates 
Spark cluster. Spark-summit can deploy spark cluster as well in Kubernetes. see 
[https://spark.apache.org/docs/2.3.0/running-on-kubernetes.html.] Also there's 
a PR we can check [https://github.com/apache/zeppelin/pull/2637].

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3839) A Tutorial notebook filename is not compatible with MS Windows

2018-10-31 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3839:
--

 Summary: A Tutorial notebook filename is not compatible with MS 
Windows
 Key: ZEPPELIN-3839
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3839
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


[https://github.com/apache/zeppelin/pull/3186] includes '|' (pipe) in one of 
Tutorial notebook filename.

'|' is reserved char in windows filesystem. see 
[https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file].

This is also a reason why appveyor is failing.

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3837) Make 'how to build' up to date.

2018-10-30 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3837:
--

 Summary: Make 'how to build' up to date.
 Key: ZEPPELIN-3837
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3837
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


docs/setup/basics/how_to_build.md is bit outdated.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3836) zeppelin.apache.org/docs/latest points 0.7.3, instead of 0.8.0

2018-10-30 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3836:
--

 Summary: zeppelin.apache.org/docs/latest points 0.7.3, instead of 
0.8.0
 Key: ZEPPELIN-3836
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3836
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
Assignee: Lee moon soo


[https://zeppelin.apache.org/docs/latest] points 0.7.3 version doc, instead of 
0.8.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3835) Update website "what's new" section for 0.8.0 release.

2018-10-29 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3835:
--

 Summary: Update website "what's new" section for 0.8.0 release.
 Key: ZEPPELIN-3835
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3835
 Project: Zeppelin
  Issue Type: Task
Reporter: Lee moon soo
Assignee: Lee moon soo


Update website "what's new" section for 0.8.0 release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC6)

2018-06-26 Thread moon soo Lee
+1

Best,
moon

On Wed, Jun 27, 2018 at 12:40 AM NineQS CloverHearts <
cloverhearts...@gmail.com> wrote:

> +1
> 
> From: Belousov Maksim Eduardovich 
> Sent: Tuesday, June 26, 2018 10:27:49 PM
> To: dev@zeppelin.apache.org
> Subject: RE: [VOTE] Release Apache Zeppelin 0.8.0 (RC6)
>
> +1
>
>
> Regards,
>
> Maksim Belousov
>
> -Original Message-
> From: Prabhjyot Singh [mailto:prabhjyotsi...@apache.org]
> Sent: Monday, June 25, 2018 11:33 AM
> To: dev 
> Subject: Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC6)
>
> +1
>
> On Mon, 25 Jun 2018 at 06:05, Jeff Zhang  wrote:
>
> > Here's my +1.
> >
> > I build it from source successfully and ran spark tutorial in local,
> > yarn-client, yarn-cluster mode successfully.
> >
> >
> >
> > Jeff Zhang 于2018年6月25日周一 上午8:34写道:
> >
> > > Hi folks,
> > >
> > > I propose the following RC to be released for the Apache Zeppelin
> > > 0.8.0 release.
> > >
> > > The commit id is 603cc492f5e322c73915501e8cf65970d0c61870
> > >
> > >  *
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=603c
> > c492f5e322c73915501e8cf65970d0c61870
> > <
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=603c
> > c492f5e322c73915501e8cf65970d0c61870
> > >*
> > >
> > >
> > > This corresponds to the tag: v0.8.0-rc6
> > >
> > > The release archives (tgz), signature, and checksums are here *
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc6/ <
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc6/>*
> > >
> > >
> > > The release candidate consists of the following source distribution
> > archive zeppelin-0.8.0.tgz
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location zeppelin-0.8.0-bin-all.tgz
> > >
> > > zeppelin-0.8.0-bin-netinst.tgz
> > >
> > > The maven artifacts are here *
> > https://repository.apache.org/content/repositories/orgapachezeppelin-1
> > 252
> > > <
> > https://repository.apache.org/content/repositories/orgapachezeppelin-1
> > 252
> > >*
> > >
> > > You can find the KEYS file here:
> > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > >
> > > Release notes available at
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316
> > 221=12339144
> > >
> > > Vote will be open for next 72 hours (close at 6PM 27/June PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> >
> > --
> >
> > Warm Regards,
> >
> > Prabhjyot Singh
> >
> >
>


Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC5)

2018-06-22 Thread moon soo Lee
+1

Thanks,
moon

On Fri, Jun 22, 2018 at 17:08 Belousov Maksim Eduardovich
 wrote:

> +1
>
>
> Regards,
>
> Maksim Belousov
>
> -Original Message-
> From: Jeff Zhang [mailto:zjf...@gmail.com]
> Sent: Thursday, June 21, 2018 10:18 AM
> To: dev@zeppelin.apache.org
> Subject: Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC5)
>
> Here's my +1
>
> I build it from source code successfully, and run zeppelin tutorial note
> successfully in local, yarn-client, yarn-cluster mode under spark-2.3
>
>
>
> Miquel Angel Andreu Febrer 于2018年6月20日周三
> 下午1:58写道:
>
> > Thanks Jeff,
> >
> > LGTM
> >
> > +1
> >
> >
> > El mié., 20 jun. 2018 7:56, Prabhjyot Singh
> > 
> > escribió:
> >
> > > +1
> > >
> > > On Wed, 20 Jun 2018 at 10:48, CloverHearts
> > > 
> > > wrote:
> > >
> > > > Awesome +1
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Jun 20, 2018 at 11:41 AM +0900, "Jeff Zhang" <
> > zjf...@apache.org>
> > > > wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi folks,
> > > >
> > > > I propose the following RC to be released for the Apache Zeppelin
> > > > 0.8.0 release.
> > > >
> > > > The commit id is adc2e63c1ff1f7690ba7b3c10984c8024e379a31
> > > >
> > > >  *
> > > >
> > >
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=adc2
> > e63c1ff1f7690ba7b3c10984c8024e379a31
> > > > *
> > > >
> > > >
> > > >
> > > > This corresponds to the tag: v0.8.0-rc5
> > > >
> > > > The release archives (tgz), signature, and checksums are here
> > > > *https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc
> > > > 5/
> > > > *
> > > >
> > > >
> > > > The release candidate consists of the following source
> > > > distribution archive zeppelin-0.8.0.tgz
> > > >
> > > > In addition, the following supplementary binary distributions are
> > > provided
> > > > for user convenience at the same location
> > > > zeppelin-0.8.0-bin-all.tgz
> > > >
> > > > zeppelin-0.8.0-bin-netinst.tgz
> > > >
> > > > The maven artifacts are here
> > > > *
> > > >
> > >
> > https://repository.apache.org/content/repositories/orgapachezeppelin-1
> > 242/
> > > > *
> > > >
> > > > You can find the KEYS file here:
> > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > >
> > > > Release notes available at
> > > >
> > > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316
> > 221=12339144
> > > >
> > > > Vote will be open for next 72 hours (close at 8PM 22/June PDT).
> > > >
> > > > [ ] +1 approve
> > > > [ ] 0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > > --
> > > >
> > > > Warm Regards,
> > > >
> > > > Prabhjyot Singh
> > > >
> > > >
> > >
> >
>


[jira] [Created] (ZEPPELIN-3554) Flaky test - InterpreterContextTest.testThreadLocal

2018-06-19 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3554:
--

 Summary: Flaky test - InterpreterContextTest.testThreadLocal
 Key: ZEPPELIN-3554
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3554
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.9.0


Flaky test - InterpreterContextTest.testThreadLocal
{code:java}
testThreadLocal(org.apache.zeppelin.interpreter.InterpreterContextTest)  Time 
elapsed: 0.004 sec  <<< FAILURE!
java.lang.AssertionError: expected null, but 
was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at 
org.apache.zeppelin.interpreter.InterpreterContextTest.testThreadLocal(InterpreterContextTest.java:29){code}
 

Full logs

https://api.travis-ci.org/v3/job/394317200/log.txt



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC4)

2018-05-31 Thread moon soo Lee
+1
Verified

 - Signature
 - License exists
 - Build from source
 - Run tutorial notebooks
 - Install helium visualizaitons
 - Works with multiple spark version

Thanks Jeff for preparing the release.

On Wed, May 30, 2018 at 8:54 AM Miquel Angel Andreu Febrer <
miquelangeland...@gmail.com> wrote:

> +1
>
> Test the principal interpretes and works successfuly
>
>
> El mié., 30 may. 2018 16:12, Jeff Zhang  escribió:
>
> > I will start with my +1
> >
> > I build source code successfully and can run spark tutorial note.
> >
> > Try zeppelin-0.8.0-bin-all and run spark tutorial note successfully under
> > local, yarn-client and yarn-cluster mode. also run it under livy
> > interpreter and impersonation mode
> > Try zeppelin-0.8.0-bin-netinst and run spark tutorial note successfully
> > under local, yarn-client and yarn-cluster mode.
> >
> > Jeff Zhang 于2018年5月30日周三 下午10:08写道:
> >
> > > Hi folks,
> > >
> > > I propose the following RC to be released for the Apache Zeppelin
> > > 0.8.0 release.
> > >
> > >
> > > The commit id is 41d9e0ac3f908da2eb4167984271aced78a8bfc6
> > >
> > >  *
> >
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=41d9e0ac3f908da2eb4167984271aced78a8bfc6
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=41d9e0ac3f908da2eb4167984271aced78a8bfc6
> > >*
> > >
> > >
> > >
> > > This corresponds to the tag: v0.8.0-rc4
> > >
> > > The release archives (tgz), signature, and checksums are here *
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc4/ <
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc4/>*
> > >
> > >
> > > The release candidate consists of the following source distribution
> > archive zeppelin-0.8.0.tgz
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location zeppelin-0.8.0-bin-all.tgz
> > >
> > > zeppelin-0.8.0-bin-netinst.tgz
> > >
> > > The maven artifacts are here *
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1195/
> > > <
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1195/
> > >*
> > >
> > > You can find the KEYS file here:
> > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > >
> > > Release notes available at
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12339144
> > >
> > > Vote will be open for next 72 hours (close at 7AM 2/June PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> >
>


Re: [VOTE] Release Apache Zeppelin 0.8.0 (RC2)

2018-05-15 Thread moon soo Lee
Thanks Jeff preparing the release.

+1

 - License exists in source/binary package
 - Signature
 - Build from source
 - Run tutorial notebooks

I think ./bin/install-interpreter.sh does not work because 0.8.0 artifacts
are not published yet. If ./bin/install-interpreter.sh command have a
capability to add staging repo (
https://repository.apache.org/content/repositories/orgapachezeppelin-1124/)
that'll be helpful verifying RC.

On Tue, May 15, 2018 at 10:42 AM Sanjay Dasgupta 
wrote:

> -1
>
> I downloaded zeppelin-0.8.0-bin-netinst.tgz, and then tried to install the
> shell and jdbc interpreters. Both attempts failed (Ubuntu 16.04, Oracle JDK
> 1.8.0_171).
>
> The error while trying to install the shell interpreter is shown below:
>
> $ ./bin/install-interpreter.sh --name shell
>
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> MaxPermSize=512m; support was removed in 8.0
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
>
> [jar:file:/home/yajnas/Desktop/Data-Analytics-AI/zeppelin/zeppelin-0.8.0-rc2-bin-netinst/lib/interpreter/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
>
> [jar:file:/home/yajnas/Desktop/Data-Analytics-AI/zeppelin/zeppelin-0.8.0-rc2-bin-netinst/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Install shell(org.apache.zeppelin:zeppelin-shell:0.8.0) to
>
> /home/yajnas/Desktop/Data-Analytics-AI/zeppelin/zeppelin-0.8.0-rc2-bin-netinst/interpreter/shell
> ...
> org.sonatype.aether.RepositoryException: Cannot fetch dependencies for
> org.apache.zeppelin:zeppelin-shell:0.8.0
> at
>
> org.apache.zeppelin.dep.DependencyResolver.getArtifactsWithDep(DependencyResolver.java:179)
> at
>
> org.apache.zeppelin.dep.DependencyResolver.loadFromMvn(DependencyResolver.java:128)
> at
> org.apache.zeppelin.dep.DependencyResolver.load(DependencyResolver.java:76)
> at
> org.apache.zeppelin.dep.DependencyResolver.load(DependencyResolver.java:93)
> at
> org.apache.zeppelin.dep.DependencyResolver.load(DependencyResolver.java:85)
> at
>
> org.apache.zeppelin.interpreter.install.InstallInterpreter.install(InstallInterpreter.java:170)
> at
>
> org.apache.zeppelin.interpreter.install.InstallInterpreter.install(InstallInterpreter.java:134)
> at
>
> org.apache.zeppelin.interpreter.install.InstallInterpreter.install(InstallInterpreter.java:126)
> at
>
> org.apache.zeppelin.interpreter.install.InstallInterpreter.main(InstallInterpreter.java:278)
> Caused by: org.sonatype.aether.resolution.DependencyResolutionException:
> Could not find artifact org.apache.zeppelin:zeppelin-shell:jar:0.8.0 in
> central (http://repo1.maven.org/maven2/)
> at
>
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
> at
>
> org.apache.zeppelin.dep.DependencyResolver.getArtifactsWithDep(DependencyResolver.java:176)
> ... 8 more
> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
> Could not find artifact org.apache.zeppelin:zeppelin-shell:jar:0.8.0 in
> central (http://repo1.maven.org/maven2/)
> at
>
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:537)
> at
>
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
> at
>
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
> ... 9 more
> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could
> not find artifact org.apache.zeppelin:zeppelin-shell:jar:0.8.0 in central (
> http://repo1.maven.org/maven2/)
> at
>
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:971)
> at
>
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:966)
> at
>
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:707)
> at
>
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:701)
> at
>
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector.get(WagonRepositoryConnector.java:452)
> at
>
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:456)
> ... 11 more
> $
>
>
> On Tue, May 15, 2018 at 9:34 PM, Renjith Kamath 
> wrote:
>
> > +1
> > verified both
> >
> > Thanks & Regards,
> > RK
> >
> > On Tue, May 15, 2018 at 3:14 PM, Miquel Angel Andreu Febrer <
> > miquelangeland...@gmail.com> wrote:
> >
> > > +1
> > >
> > > Launched the packages with docker and works well
> > >
> > > El mar., 15 may. 2018 11:06, Jeff Zhang  escribió:
> > >
> > > > Here's my +1
> > > >
> > > > I 

[jira] [Created] (ZEPPELIN-3285) Unnecessary margin before the title of note

2018-03-02 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3285:
--

 Summary: Unnecessary margin before the title of note
 Key: ZEPPELIN-3285
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3285
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Lee moon soo
 Attachments: image-2018-03-02-15-59-39-827.png

There's unnecessary margin before the title.

!image-2018-03-02-15-59-39-827.png!

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3284) z.getInterpreterContext().out().clear() broken in Python interpreter

2018-03-02 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3284:
--

 Summary: z.getInterpreterContext().out().clear() broken in Python 
interpreter
 Key: ZEPPELIN-3284
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3284
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Lee moon soo
 Attachments: image-2018-03-02-15-54-38-942.png

Zeppelin 0.7.x, %spark and %python interpreter able to clear output using 
z.getInterpreterContext().out().clear()

!image-2018-03-02-15-54-38-942.png!

 

However, master branch and branch-0.8, PythonInterpreter does not provide the 
same capability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-3283) InterpreterOutput.toInterpreterResultMessage() and InterpreterOutput.getInterpreterResultMessages() are redundant

2018-03-02 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-3283:
--

 Summary: InterpreterOutput.toInterpreterResultMessage() and 
InterpreterOutput.getInterpreterResultMessages() are redundant
 Key: ZEPPELIN-3283
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3283
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee moon soo


org.apache.zeppelin.interpreter.InterpreterOutput.toInterpreterResultMessage() 
and 
org.apache.zeppelin.interpreter.InterpreterOutput.getInterpreterResultMessages()
 are redundant



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [Discussion] 0.8.0 Release

2017-12-27 Thread moon soo Lee
Cool. Thanks for the volunteer.

Why don't we update issue link of
https://issues.apache.org/jira/browse/ZEPPELIN-2385? I think issue link is
bit out dated.
We can remove issue links if they're not expected in 0.8.0, add issue links
if they must be included in 0.8.0.
So everyone can track the progress of 0.8.0 in the same place.

Thanks,
moon


On Wed, Dec 27, 2017 at 8:17 AM Belousov Maksim Eduardovich <
m.belou...@tinkoff.ru> wrote:

> This is great news.
>
> Our team will take part in testing and bug fixing.
>
>
> Thanks,
>
> Maksim Belousov
>
>
> -Original Message-
> From: Miquel Angel Andreu Febrer [mailto:miquelangeland...@gmail.com]
> Sent: Wednesday, December 27, 2017 3:46 PM
> To: dev@zeppelin.apache.org
> Subject: Re: [Discussion] 0.8.0 Release
>
> Hello everyone,
>
> I think it's a good idea, I do not know if we are pending some important
> issues for the 0.8.0, we should see in jira. I can help with the management
> of the 0.8.0 release if the new release will be launched at the end of
> January
>
> Regards
>
> El 27 dic. 2017 13:35, "Jeff Zhang" <zjf...@gmail.com> escribió:
>
> > Hi folks,
> >
> > It is a long time since our last release, and many new features are
> > added into 0.8.0, so I think we could think about to prepare the
> > release of 0.8.0, if no volunteer to be the release manager, I
> > volunteer to be the release manager of this version. My current
> > thinking is to make the release at the end of January. Any thinking and
> comments ?
> >
>


Re: [DISCUSS] Review process

2017-12-18 Thread moon soo Lee
Hi,

Current review process[1] does require either at least a +1 from committer
or 24 hours for lazy consensus.

Pullrequest can be open for 1 or 2 days for additional review, but i think
they're not hard requirements. (e.g. Hotfixes are already being merged
without waiting additional review)

So, technically, current policy allows any committer can start review, mark
+1 and merge immediately without any delay if necessary.

Thanks,
moon

[1]
http://zeppelin.apache.org/contribution/contributions.html#the-review-process


On Mon, Dec 18, 2017 at 2:13 AM Belousov Maksim Eduardovich <
m.belou...@tinkoff.ru> wrote:

> +1 for non-delay merging.
> Our team have opened approved PR [1] for 5 days.
>
> I didn't find any pages with `consensus how to review and merge
> contributions`.
> It would be nice to write a check list for reviewer.
>
> The development of Zeppelin is very important for us and we want to review
> new commits.
>
>
> [1] https://github.com/apache/zeppelin/pull/2697
>
>
> Thanks,
> Maksim Belousov
>
> -Original Message-
> From: Jongyoul Lee [mailto:jongy...@gmail.com]
> Sent: Monday, December 18, 2017 12:12 PM
> To: dev <dev@zeppelin.apache.org>
> Subject: Re: [DISCUSS] Review process
>
> Thank you for the replying it. I think so
>
> On Mon, Dec 18, 2017 at 3:15 PM, Miquel Angel Andreu Febrer <
> miquelangeland...@gmail.com> wrote:
>
> > I agree, ig is necessary to have no delay afternoon merging. I think
> > it will help speed up processes and help contributors
> >
> > El 18 dic. 2017 4:33, "Jongyoul Lee" <jongy...@gmail.com> escribió:
> >
> > Hi committers,
> >
> > I want to suggest one thing about our reviewing process. We have the
> > policy to wait for one-day before merging some PRs. AFAIK, It's
> > because we reduce mistakes and prevent abuses from committing by owner
> > without reviewing it concretely. I would like to change this policy to
> > remove delay after merging it. We, recently, don't have much reviewers
> > and committers who can merge continuously, and in my case, I,
> > sometimes, forget some PRs that I have to merge. And I also believe
> > all committers have consensus how to review and merge contributions.
> >
> > How do you think of it?
> >
> > JL
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>


Re: Disable cron runs

2017-10-13 Thread moon soo Lee
Hi,

Currently, there's no easy way to disable cron.
I think it's okay to add configuration parameter that disables all cron
run, while the default value of the parameter enable the cron (for backward
compatibility).

Let me know if you need any help on this.

Thanks,
moon

On Wed, Oct 4, 2017 at 2:35 AM Belousov Maksim Eduardovich <
m.belou...@tinkoff.ru> wrote:

> Hello, dev!
>
> Our team have about 600 notes and 35 of them are scheduled. Some scheduled
> notes create tables in DB and send e-mails.
> We want to hide testing activities when we test notes on another server.
> Now we remove cron parameters in json files. It is not cool.
>
> Are there any workarounds to disable running of notes with cron?
> Can it be a good decision to add a new server parameter that will disable
> all cron runs?
>
>
> Thanks,
>
> Maksim Belousov
>
>


[jira] [Created] (ZEPPELIN-2994) Websocket/REST API to access ResourcePool

2017-10-13 Thread Lee moon soo (JIRA)
Lee moon soo created ZEPPELIN-2994:
--

 Summary: Websocket/REST API to access ResourcePool
 Key: ZEPPELIN-2994
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2994
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee moon soo


h2. Motivation

[ResourcePool|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/ResourcePool.java]
 is general purpose, distributed map across interpreter processes.

ResourcePool currently provides

* Put / Get any object
* List objects
* Invoke method of object in the ResourcePool

Because of ResourcePool is (logically) distributed across Interpreters, 
interpreter can use it to communicate to other interpreters. Pass interpreter 
result to other interpreter, let other interpreter call directly call one of 
the method of SparkContext, etc.

h2. Websocket/REST API to ResourcePool

However, currently ResourcePool API is only accessible in Interpreter. If 
front-end can have Websocket/Rest API to the ResourcePool, we'll have usages 
like

* Interpreter store 
[TableData|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/tabledata/TableData.java]
 into the ResourcePool.
* Front-end read TableData directly from ResourcePool. (and visualize data)

This will open possibilities of

* Move pivot routine to the backend (because current pivot works in front-end 
with partial data)
* Realtime visualization update on front-end as data changes




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


  1   2   3   >