Re: [DISCUSS] Zeppelin-0.5.5-incubating release and next release

2015-11-04 Thread Mina Lee 
There are bunch of useful features after last release indeed!
+1 for moving to vote

On Thu, Nov 5, 2015 at 1:42 PM, Corneau Damien  wrote:

> +1 for moving to vote
> And try to do 2 releases this month!
>
> On Thu, Nov 5, 2015 at 5:15 AM, Alexander Bezzubov 
> wrote:
>
> > Great stuff, thank you Moon for excellent (as usual) release management!
> >
> > +1 for moving to a vote
> >
> > On Wed, Nov 4, 2015 at 11:35 PM, moon soo Lee  wrote:
> >
> > > Hi folks,
> > >
> > > Release 0.5.5 was tracked by
> > > https://issues.apache.org/jira/browse/ZEPPELIN-311,
> > > and finally branch-0.5.5 is created (
> > > https://issues.apache.org/jira/browse/ZEPPELIN-369)
> > > and release candidate is created from it
> > > https://dist.apache.org/repos/dist/dev/incubator/zeppelin/.
> > >
> > > Please take a look. If there're no critical problem, I'd suggest move
> on
> > to
> > > vote process.
> > >
> > > There're a lot of really nice features and improvements expected to
> merge
> > > soon. So i also suggest having following release immediately after
> those
> > > nice features are ready, I think this can be 0.5.6-incubating release.
> > >
> > > What do you think?
> > >
> > >
> > > Thanks,
> > > moon
> > >
> >
> >
> >
> > --
> > --
> > Kind regards,
> > Alexander.
> >
>

Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.5-incubating

2015-11-05 Thread Mina Lee 
+1
2015. 11. 6. 오전 12:01에 "moon soo Lee" 님이 작성:

> Hi folks,
>
> I propose the following RC to be released for the Apache Zeppelin
> (incubating) 0.5.5-incubating release.
>
>
> The commit id is 72e38d0b3c3ba8b08ba1176c2eb2c38661a54d31 :
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git;a=commit;h=72e38d0b3c3ba8b08ba1176c2eb2c38661a54d31
>
> This corresponds to the tag: v0.5.5 :
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git;a=tag;h=refs/tags/v0.5.5
>
> The release archives (tgz), signature, and checksums are here
>
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.5-incubating-rc1/
>
> The release candidate consists of the following source distribution archive
> zeppelin-0.5.5-incubating.tgz
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location
> zeppelin-0.5.5-incubating-bin-all.tgz
>
>
> The maven artifacts are here
>
> https://repository.apache.org/content/repositories/orgapachezeppelin-1001/org/apache/zeppelin/
>
> You can find the KEYS file here:
> https://dist.apache.org/repos/dist/release/incubator/zeppelin/KEYS
>
> Release notes available at
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221&version=12333531
>
> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>

Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.5-incubating (RC2)

2015-11-08 Thread Mina Lee 
+1 for restarting vote with rc3

On Sun, Nov 8, 2015 at 3:04 PM, moon soo Lee  wrote:

> following issues are found during rc2 verification.
>
> https://issues.apache.org/jira/browse/ZEPPELIN-404
> https://issues.apache.org/jira/browse/ZEPPELIN-405
> https://issues.apache.org/jira/browse/ZEPPELIN-406
>
> and i think vote need to be restarted with rc3. Would restarting this vote
> be okay?
>
> Thanks,
> moon
>
> On Sun, Nov 8, 2015 at 9:23 AM moon soo Lee  wrote:
>
> > Last release (0.5.0-incubating), LICENSE and NOTICE file were pointed
> out.
> > If someone can help verify LICENSE and NOTICE file, that would be really
> > appreciated.
> >
> > Best,
> > moon
> >
> >
> > On Sun, Nov 8, 2015 at 1:17 AM moon soo Lee  wrote:
> >
> >> Thanks for verifying.
> >> Cos also mentioned about version in the branch.
> >> What could be proper version number in the branch?
> >>
> >> Best,
> >> moon
> >>
> >> On Sun, Nov 8, 2015 at 12:42 AM Jeff Steinmetz <
> >> jeffrey.steinm...@gmail.com> wrote:
> >>
> >>> Confirming we are building off of this branch for 0.5.5
> >>>
> >>> https://github.com/apache/incubator-zeppelin/tree/branch-0.5.5
> >>>
> >>>
> >>>
> >>> If so, is there a reason this branch has the version set to 0.5.6
> >>>
> >>> 0.5.6-incubating-SNAPSHOT
> >>>
> >>> Here
> >>>
> >>>
> >>>
> https://github.com/apache/incubator-zeppelin/blob/branch-0.5.5/pom.xml#L37
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On 11/7/15, 2:15 AM, "tog"  wrote:
> >>>
> >>> >Did test spark, pyspark  on various notes in local mode
> >>> >
> >>> >+1
> >>> >
> >>> >On 7 November 2015 at 09:55, moon soo Lee  wrote:
> >>> >
> >>> >> Thanks for verifying.
> >>> >>
> >>> >> You'll still need to set proper profile depends on your use case.
> >>> >> Binary package in release candidate (rc2) has been built with
> >>> >>
> >>> >> "-Pspark-1.5 -Phadoop-2.4 -Pyarn -Ppyspark"
> >>> >>
> >>> >> see
> >>> >>
> >>> >>
> >>>
> https://github.com/apache/incubator-zeppelin/blob/master/dev/create_release.sh#L125
> >>> >>
> >>> >> You'll able to create the same binary with the profile above.
> >>> >>
> >>> >> Thanks,
> >>> >> moon
> >>> >>
> >>> >> On Sat, Nov 7, 2015 at 6:40 PM Eran Witkon 
> >>> wrote:
> >>> >>
> >>> >> > Hi,
> >>> >> > I just downloaded zeppelin-0.5.5-incubating.tgz  from
> >>> >> >
> >>> >> >
> >>> >>
> >>>
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.5-incubating-rc2/
> >>> >> > ,
> >>> >> > built it using 'mvn clean package -DskipTests' and run it but I
> get
> >>> :
> >>> >> > sc.version 1.4.1
> >>> >> > and pyspark:
> >>> >> > pyspark is not responding Traceback (most recent call last): File
> >>> >> > "/tmp/zeppelin_pyspark.py", line 20, in  from
> >>> py4j.java_gateway
> >>> >> > import java_import, JavaGateway, GatewayClient
> >>> >> > ImportError: No module named py4j.java_gateway
> >>> >> >
> >>> >> > is the the right place or is these expected for release 0.5.5
> >>> >> >
> >>> >> >
> >>> >> > On Sat, Nov 7, 2015 at 2:13 AM Alexander Bezzubov  >
> >>> >> wrote:
> >>> >> >
> >>> >> > > +1 (binding)
> >>> >> > >
> >>> >> > > thank you Moon for addressing RC1 issues in such timely manner!
> >>> >> > >
> >>> >> > > On Sat, Nov 7, 2015, 07:50 Felix Cheung <
> >>> felixcheun...@hotmail.com>
> >>> >> > wrote:
> >>> >> > >
> >>> >> > > > +1 tested spark pyspark flink looks good.
> >>> >> > > >
> >>> >> > > >
> >>> >> > > >
> >>> >> > > >
> >>> >> > > >
> >>> >> > > >
> >>> >> > > > On Fri, Nov 6, 2015 at 1:19 PM -0800, "Vinay Shukla" <
> >>> >> > > > vinayshu...@gmail.com> wrote:
> >>> >> > > > Thanks Guillaume. Validating with the bin tarball now.
> >>> >> > > >
> >>> >> > > > On Fri, Nov 6, 2015 at 11:37 AM, tog <
> >>> guillaume.all...@gmail.com>
> >>> >> > wrote:
> >>> >> > > >
> >>> >> > > > > Vinay
> >>> >> > > > >
> >>> >> > > > > What you have is normal behavior since you used the src
> >>> tarball.
> >>> >> You
> >>> >> > > have
> >>> >> > > > > to use the bin distribution to achieve what you want to do.
> >>> >> > > > >
> >>> >> > > > > Cheers
> >>> >> > > > > Guillaume
> >>> >> > > > >
> >>> >> > > > > On 6 November 2015 at 18:49, Vinay Shukla <
> >>> vinayshu...@gmail.com>
> >>> >> > > wrote:
> >>> >> > > > >
> >>> >> > > > >> -1
> >>> >> > > > >>
> >>> >> > > > >> Apologies, if I am missing some steps. I expected the
> >>> tarball to
> >>> >> > just
> >>> >> > > > let
> >>> >> > > > >> me launch Zeppelin daemon w/o any config required.
> >>> >> > > > >> Here are the steps I followed.
> >>> >> > > > >>
> >>> >> > > > >> Downloaded Zeppelin tarball
> >>> >> > > > >> wget
> >>> >> > > > >>
> >>> >> > > > >>
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.5-incubating-rc2/zeppelin-0.5.5-incubating.tgz
> >>> >> > > > >>
> >>> >> > > > >> tar xvf zeppelin-0.5.5-incubating.tgz
> >>> >> > > > >>
> >>> >> > > > >> cd zeppelin-0.5.5-incubating
> >>> >> > > > >> bin/zeppelin-daemon.sh start
> >>> >> > > > >>
> >>> >> > > > >> Server fails t

Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.5-incubating (RC3)

2015-11-14 Thread Mina Lee 
+1

On Fri, Nov 13, 2015 at 4:42 PM, Jongyoul Lee  wrote:

> +1 for tested on spark yarn.
>
> On Fri, Nov 13, 2015 at 11:49 AM, Henry Saputra 
> wrote:
>
> > NOTICE file looks good
> > LICENSE file looks good
> > DISCLAIMER file exists
> > Signature file looks good
> > No 3rd party executables
> > License headers correct
> > Source compiled
> >
> > +1
> >
> >
> >
> > On Wed, Nov 11, 2015 at 4:32 AM, moon soo Lee  wrote:
> > > Hi folks,
> > >
> > > Since vote for 0.5.5-incubating RC2 was canceled (vote:
> > > http://s.apache.org/DXi, cancel: http://s.apache.org/Lce)
> > >
> > > https://issues.apache.org/jira/browse/ZEPPELIN-404,
> > > https://issues.apache.org/jira/browse/ZEPPELIN-405,
> > > https://issues.apache.org/jira/browse/ZEPPELIN-406
> > > addressed the issue found in RC2.
> > >
> > > I propose the following RC (RC3) to be released for the Apache Zeppelin
> > > (incubating) 0.5.5-incubating release.
> > >
> > > The commit id is e4743e71d2421f5b6950f9e0f346f07bb84f1671 :
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git;a=commit;h=e4743e71d2421f5b6950f9e0f346f07bb84f1671
> > >
> > > This corresponds to the tag: v0.5.5 :
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git;a=tag;h=refs/tags/v0.5.5
> > >
> > > The release archives (tgz), signature, and checksums are here
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.5-incubating-rc3/
> > >
> > > The release candidate consists of the following source distribution
> > archive
> > > zeppelin-0.5.5-incubating.tgz
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location
> > > zeppelin-0.5.5-incubating-bin-all.tgz
> > >
> > >
> > > The maven artifacts are here
> > >
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1003
> > >
> > > You can find the KEYS file here:
> > > https://dist.apache.org/repos/dist/release/incubator/zeppelin/KEYS
> > >
> > > Release notes available at
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221&version=12333531
> > >
> > > Vote will be open for next 72 hours (close at 4:30am 14/Nov PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> >
>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>

Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.6-incubating (RC2)

2016-01-14 Thread Mina Lee 
+1 (binding)

On Wed, Jan 13, 2016 at 9:53 PM, Corneau Damien 
wrote:

> +1 (binding)
>
> On Thu, Jan 14, 2016 at 2:38 PM, moon soo Lee  wrote:
>
> > +1 (binding)
> >
> > On Tue, Jan 12, 2016 at 9:09 PM Felix Cheung 
> > wrote:
> >
> > > +1
> > >
> > > Tested:
> > > packaged spark, external sparkSpark/Scala, pyspark, md, sh, flink,
> > various
> > > UI features
> > > Found and filed these bugs, I don't think they are blockers:
> > >
> > > https://issues.apache.org/jira/browse/ZEPPELIN-599  notebook search
> > > should search paragraph titlehttps://
> > > issues.apache.org/jira/browse/ZEPPELIN-600  notebook search should
> have
> > a
> > > way to clear search and return to the previous pagehttps://
> > > issues.apache.org/jira/browse/ZEPPELIN-601  import new note, add from
> > url
> > > textbox is not clearing buttons from previous choiceshttps://
> > > issues.apache.org/jira/browse/ZEPPELIN-602  elasticsearch throws
> > > ArrayIndexOutOfBoundsException for interpreting an empty paragraph
> > >  > From: abezzu...@nflabs.com
> > > > Date: Wed, 13 Jan 2016 13:58:19 +0900
> > > > Subject: Re: [VOTE] Release Apache Zeppelin (incubating)
> > > 0.5.6-incubating (RC2)
> > > > To: dev@zeppelin.incubator.apache.org
> > > >
> > > > +1 (binding)
> > > >
> > > > On Tue, Jan 12, 2016 at 9:55 AM, Jongyoul Lee 
> > > wrote:
> > > >
> > > > > +1 (binding), looks good to move forward to Spark 1.6
> > > > >
> > > > > On Mon, Jan 11, 2016 at 11:27 PM, Alexander Bezzubov <
> > > abezzu...@nflabs.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I am pleased to be calling this vote for the following RC2 to be
> > > release
> > > > > as
> > > > > > Apache Zeppelin incubating-0.5.6
> > > > > >
> > > > > > Vote on RC1 got canceled, next issues were included in the RC2
> > > > > >   https://issues.apache.org/jira/browse/ZEPPELIN-564
> > > > > >   https://issues.apache.org/jira/browse/ZEPPELIN-565
> > > > > >   https://github.com/apache/incubator-zeppelin/pull/616 - Fix
> > > > > > documentation
> > > > > >   https://github.com/apache/incubator-zeppelin/pull/617 - Fix
> > > website
> > > > > >   https://github.com/apache/incubator-zeppelin/pull/618 - Spark
> > 1.6
> > > > > > for embedded
> > > > > > dependency in binary package
> > > > > >   https://github.com/apache/incubator-zeppelin/pull/613 - Fix +
> > (new
> > > > > > paragraph)
> > > > > > appearing in iframe link
> > > > > >   https://github.com/apache/incubator-zeppelin/pull/605 -
> Pyspark
> > > does
> > > > > > not work
> > > > > > in yarn-client without spark.yarn.isPython set true
> > > > > >
> > > > > >
> > > > > > The release candidate consists of the following source
> distribution
> > > > > archive
> > > > > > zeppelin-0.5.6-incubating.tgz
> > > > > >
> > > > > > In addition, the following supplementary binary distributions are
> > > > > provided
> > > > > > for
> > > > > > user convenience at the same location
> > > > > > zeppelin-0.5.6-incubating-bin-all.tgz
> > > > > >
> > > > > > The source zip, including signatures, digests, etc. can be found
> > at:
> > > > > > *
> > > > > >
> > > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.6-incubating-rc2/
> > > > > > <
> > > > > >
> > > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/zeppelin/0.5.6-incubating-rc2/
> > > > > > >*
> > > > > >
> > > > > > The maven artifacts are here
> > > > > > *
> > > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1006
> > > > > > <
> > > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachezeppelin-1006
> > > > > > >*
> > > > > >
> > > > > > The Git tag is v0.5.6
> > > > > > The Git commit ID is 8698d0e5d376800b174d8b604f584b86b3037d65
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-zeppelin.git;a=commit;h=8698d0e5d376800b174d8b604f584b86b3037d65
> > > > > >
> > > > > > Release artifacts are signed with the following key:
> > > > > > https://people.apache.org/keys/committer/bzz
> > > > > >
> > > > > > KEYS file available here:
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/zeppelin/KEYS
> > > > > >
> > > > > > 131 issues were closed/resolved for this release:
> > > > > >
> > > https://issues.apache.org/jira/browse/ZEPPELIN/fixforversion/12334165/
> > > > > >
> > > > > > Release note highlights can be found here:
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221&version=12334165
> > > > > >
> > > > > > The vote will be open for 72 hours.
> > > > > > Please download the release candidate and evaluate the necessary
> > > items
> > > > > > including checking hashes, signatures, build from source, and
> test.
> > > > > >
> > > > > > The please vote:
> > > > > > [ ] +1 Release this package as Zeppelin 0.5.6-incubating
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 Do not release this package because because...
> > > > >

Re: csv dependencies loaded in %spark but not %sql in spark 1.6/zeppelin 0.5.6

2016-02-02 Thread mina lee 
This issue has been fixed few days ago in master branch.

Here is the PR
https://github.com/apache/incubator-zeppelin/pull/673

And related issues filed in JIRA before
https://issues.apache.org/jira/browse/ZEPPELIN-194
https://issues.apache.org/jira/browse/ZEPPELIN-381

With the latest master branch, we recommend you to load dependencies via
interpreter setting menu instead of %dep interpreter.

If you want to know how to set dependencies with latest master branch,
please check doc

and
let me know if it works.

Cheers,
Mina

On Tue, Feb 2, 2016 at 12:50 PM, Lin, Yunfeng  wrote:

> I’ve created an issue in jira
>
>
>
> https://issues.apache.org/jira/browse/ZEPPELIN-648
>
>
>
> *From:* Benjamin Kim [mailto:bbuil...@gmail.com]
> *Sent:* Tuesday, February 02, 2016 3:34 PM
> *To:* us...@zeppelin.incubator.apache.org
> *Cc:* dev@zeppelin.incubator.apache.org
> *Subject:* Re: csv dependencies loaded in %spark but not %sql in spark
> 1.6/zeppelin 0.5.6
>
>
>
> Same here. I want to know the answer too.
>
>
>
>
>
> On Feb 2, 2016, at 12:32 PM, Jonathan Kelly 
> wrote:
>
>
>
> Hey, I just ran into that same exact issue yesterday and wasn't sure if I
> was doing something wrong or what. Glad to know it's not just me!
> Unfortunately I have not yet had the time to look any deeper into it. Would
> you mind filing a JIRA if there isn't already one?
>
>
>
> On Tue, Feb 2, 2016 at 12:29 PM Lin, Yunfeng  wrote:
>
> Hi guys,
>
>
>
> I load spark-csv dependencies in %spark, but not in %sql using apache
> zeppelin 0.5.6 with spark 1.6.0. Everything is working fine in zeppelin
> 0.5.5 with spark 1.5 through
>
>
>
> Do you have similar problems?
>
>
>
> I am loading spark csv dependencies (
> https://github.com/databricks/spark-csv
> 
> )
>
>
>
> Using:
>
> %dep
>
> z.load(“PATH/commons-csv-1.1.jar”)
>
> z.load(“PATH/spark-csv_2.10-1.3.0.jar”)
>
> z.load(“PATH/univocity-parsers-1.5.1.jar:)
>
> z.load(“PATH/scala-library-2.10.5.jar”)
>
>
>
> I am able to load a csv from hdfs using data frame API in spark. It is
> running perfect fine.
>
> %spark
>
> val df = sqlContext.read
>
> .format("com.databricks.spark.csv")
>
> .option("header", "false") // Use finrst line of all files as header
>
> .option("inferSchema", "true") // Automatically infer data types
>
> .load("hdfs://sd-6f48-7fe6:8020/tmp/people.txt")   // this is a file
> in HDFS
>
> df.registerTempTable("people")
>
> df.show()
>
>
>
> This also work:
>
> %spark
>
> val df2=sqlContext.sql(“select * from people”)
>
> df2.show()
>
>
>
> But this doesn’t work….
>
> %sql
>
> select * from people
>
>
>
> java.lang.ClassNotFoundException:
> com.databricks.spark.csv.CsvRelation$$anonfun$1$$anonfun$2 at
> java.net.URLClassLoader$1.run(URLClassLoader.java:366) at
> java.net.URLClassLoader$1.run(URLClassLoader.java:355) at
> java.security.AccessController.doPrivileged(Native Method) at
> java.net.URLClassLoader.findClass(URLClassLoader.java:354) at
> java.lang.ClassLoader.loadClass(ClassLoader.java:425) at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at
> java.lang.ClassLoader.loadClass(ClassLoader.java:358) at
> java.lang.Class.forName0(Native Method) at
> java.lang.Class.forName(Class.java:270) at
> org.apache.spark.util.InnerClosureFinder$$anon$4.visitMethodInsn(ClosureCleaner.scala:435)
> at org.apache.xbean.asm5.ClassReader.a(Unknown Source) at
> org.apache.xbean.asm5.ClassReader.b(Unknown Source) at
> org.apache.xbean.asm5.ClassReader.accept(Unknown Source) at
> org.apache.xbean.asm5.ClassReader.accept(Unknown Source) at
> org.apache.spark.util.ClosureCleaner$.getInnerClosureClasses(ClosureCleaner.scala:84)
> at
> org.apache.spark.util.ClosureCleaner$.org$apache$spark$util$ClosureCleaner$$clean(ClosureCleaner.scala:187)
> at org.apache.spark.util.ClosureCleaner$.clean(ClosureCleaner.scala:122) at
> org.apache.spark.SparkContext.clean(SparkContext.scala:2055) at
> org.apache.spark.rdd.RDD$$anonfun$mapPartitions$1.apply(RDD.scala:707) at
> org.apache.spark.rdd.RDD$$anonfun$mapPartitions$1.apply(RDD.scala:706) at
> org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:150)
> at
> org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:111)
> at org.apache.spark.rdd.RDD.withScope(RDD.scala:316) at
> org.apache.spark.rdd.RDD.mapPartitions(RDD.scala:706) at
> com.databricks.spark.csv.CsvRelation.tokenRdd(CsvRelation.scala:90) at
> com.databricks.spark.csv.CsvRelation.buildScan(CsvRelation.scala:104) at
> com.databricks.spark.csv.CsvRelation.buildScan(CsvRelation.scala:152) at
> org.apache.spark.sql.execution.datasources.DataSourceStrategy$$anonfun$4.appl

Re: csv dependencies loaded in %spark but not %sql in spark 1.6/zeppelin 0.5.6

2016-02-02 Thread Mina Lee 
@Janathan Zeppelin community plans to release every 3 months so I expect
next release will be around end of April.

@Lin The workaround I can think of right now is adding libraries to
ZEPPELIN_CLASSPATH in bin/interpreter.sh
To do this,
  1. place all libraries you need(commons-csv-1.1.jar, spark-csv_2.10-1.
3.0.jar, univocity-parsers-1.5.1.jar) under one specific directory. Note
that there should be only files not subdirectories. I will name it as
"/my/path/spark-csv" for the ease of explanation.
  2. open bin/interpreter.sh
  3. Add following code `addJarInDir "/mydir/path/spark-csv"` to line
130.(I assume that you are using zeppelin-0.5.6-incubating)
  4. restart Zeppelin

Hope this helps


On Tue, Feb 2, 2016 at 1:30 PM, Lin, Yunfeng  wrote:

> Thanks! Is there a possible workaround for 0.5.6 before releasing 0.6.0?
>
>
>
> *From:* Jonathan Kelly [mailto:jonathaka...@gmail.com]
> *Sent:* Tuesday, February 02, 2016 4:19 PM
> *To:* dev@zeppelin.incubator.apache.org; users
> *Subject:* Re: csv dependencies loaded in %spark but not %sql in spark
> 1.6/zeppelin 0.5.6
>
>
>
> Awesome, thank you! BTW, I know that the Zeppelin 0.5.6 release was only
> very recently, but do you happen to know yet when you plan on releasing
> 0.6.0?
>
>
>
> On Tue, Feb 2, 2016 at 1:07 PM mina lee  wrote:
>
> This issue has been fixed few days ago in master branch.
>
> Here is the PR
> https://github.com/apache/incubator-zeppelin/pull/673
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dzeppelin_pull_673&d=BQMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=b2BXWa66OlJ_NWqk5P310M6mGfus8eDC5O4J0-nePFY&m=P05kinGmpfFiWwLExz9hZO76uI5rpP5SoqI8JJ2UWEY&s=hkFOUihaS8xvGHC2psZm_eTCpaIbp9JvGoR0Y6XV2wc&e=>
>
> And related issues filed in JIRA before
> https://issues.apache.org/jira/browse/ZEPPELIN-194
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ZEPPELIN-2D194&d=BQMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=b2BXWa66OlJ_NWqk5P310M6mGfus8eDC5O4J0-nePFY&m=P05kinGmpfFiWwLExz9hZO76uI5rpP5SoqI8JJ2UWEY&s=AvJcgiZOLR_OmESYH5osZSMnYd9_A6DBRo9CxjYsxuY&e=>
> https://issues.apache.org/jira/browse/ZEPPELIN-381
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ZEPPELIN-2D381&d=BQMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=b2BXWa66OlJ_NWqk5P310M6mGfus8eDC5O4J0-nePFY&m=P05kinGmpfFiWwLExz9hZO76uI5rpP5SoqI8JJ2UWEY&s=6iFF2WKrNwEJZ68upi94jfS_2wCVPZHeZE0aTzS4slc&e=>
>
> With the latest master branch, we recommend you to load dependencies via
> interpreter setting menu instead of %dep interpreter.
>
> If you want to know how to set dependencies with latest master branch,
> please check doc
> <
> https://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/manual/dependencymanagement.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zeppelin.incubator.apache.org_docs_0.6.0-2Dincubating-2DSNAPSHOT_manual_dependencymanagement.html&d=BQMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=b2BXWa66OlJ_NWqk5P310M6mGfus8eDC5O4J0-nePFY&m=P05kinGmpfFiWwLExz9hZO76uI5rpP5SoqI8JJ2UWEY&s=8vqDxxyOWAchE7NS0L2BLpav1-tIPMXDwE0ndsqln-E&e=>
> >
> and
> let me know if it works.
>
> Cheers,
> Mina
>
> On Tue, Feb 2, 2016 at 12:50 PM, Lin, Yunfeng 
> wrote:
>
> > I’ve created an issue in jira
> >
> >
> >
> > https://issues.apache.org/jira/browse/ZEPPELIN-648
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ZEPPELIN-2D648&d=BQMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=b2BXWa66OlJ_NWqk5P310M6mGfus8eDC5O4J0-nePFY&m=P05kinGmpfFiWwLExz9hZO76uI5rpP5SoqI8JJ2UWEY&s=hlbpHl6qhaZZD5ZWy6DeFySuZEZt3JysxHFYer2shG8&e=>
> >
> >
> >
> > *From:* Benjamin Kim [mailto:bbuil...@gmail.com]
> > *Sent:* Tuesday, February 02, 2016 3:34 PM
> > *To:* us...@zeppelin.incubator.apache.org
> > *Cc:* dev@zeppelin.incubator.apache.org
> > *Subject:* Re: csv dependencies loaded in %spark but not %sql in spark
> > 1.6/zeppelin 0.5.6
> >
> >
> >
> > Same here. I want to know the answer too.
> >
> >
> >
> >
> >
> > On Feb 2, 2016, at 12:32 PM, Jonathan Kelly 
> > wrote:
> >
> >
> >
> > Hey, I just ran into that same exact issue yesterday and wasn't sure if I
> > was doing something wrong or what. Glad to know it's not just me!
> > Unfortunately I have not yet had the time to look any deeper into it.
> Would
> > you mind filing a JIRA if there isn't already one?
> >
> >
> >
> > On Tue, Feb 2, 2016 at 12:29 PM Lin, Yunfeng 
> wrote:
> &g

Re: [DISCUSS] Graduate Zeppelin from the Incubator

2016-02-04 Thread Mina Lee 
I think Zeppelin meets the requirements for graduation.

Zeppelin community is growing fast and getting more diverse. Number of
contributors has increased more than 7 times and three new committers are
admitted since Zeppelin became Apache podling project. And release, vote
related discussions have adopted ASF way so far.
Also Zeppelin is the one of the projects making big synergy with other
apache projects by providing different back-end interpreters(ex spark,
hive, flink, hbase, cassandra, etc)

so +1 for graduation.

On Thu, Feb 4, 2016 at 8:13 AM, madhuka udantha 
wrote:

> +1 for graduation
>
> On Thu, Feb 4, 2016 at 8:59 PM, DuyHai Doan  wrote:
>
> > I was reading the link provided by Leemoonsoo about the Apache project
> > maturity model. (
> >
> http://community.apache.org/apache-way/apache-project-maturity-model.html)
> >
> >
> > > QU20 The project puts a very high priority on producing secure software
> >
> > It's related to security and I know that there is a commit on Shiro
> > authentication already by hayssams (kudo to him by the way). There is
> also
> > some JIRA ticket to add documentation about Kerberos (
> > https://github.com/apache/incubator-zeppelin/pull/640). Don't know if
> > there
> > is a JIRA to add doc for Shiro yet. Anyway, on the chapter of security,
> all
> > the works are being done and are on good way.
> >
> > Under the Community topic, I think all the points are covered (for
> example,
> > becoming a committer (point CO50) is clearly documented in
> CONTRIBUTING.md)
> > as well as consensus (point CO60).
> >
> > Under the Consensus Building chapter, every discussion related to release
> > or votes have been exposed so far publicly on the mailing list.
> >
> >  As far as I see, all the points are covered.
> >
> >  Now my personal opinion as a community member is that it's high time for
> > the project to graduate. Until now I did not feel comfortable advising
> > Zeppelin for customers to deploy in production because of lack of
> security
> > but since security support (at least for authentication) is in the trunk
> > and the improvements are on the way, I don't see any blocker anymore.
> >
> > So a big +1 for me
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Feb 4, 2016 at 2:28 PM, Ahyoung Ryu 
> > wrote:
> >
> > > Totally agree with @anthonycorbacho. I think it's time to graduate and
> > step
> > > forward.
> > > So, ++1 !
> > >
> > > 2016년 2월 4일 목요일, Anthony Corbacho님이 작성한
> 메시지:
> > >
> > > > Hi,
> > > >
> > > > I dont see any reason why we shouldn't start a vote.
> > > > unlike release, it doesnt require any specific features (For specific
> > > > feature like R or ACL, we can add it as a requirement for the first
> > > release
> > > > as TLP),
> > > > so for me its a big +1.
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, Feb 4, 2016 at 5:41 PM, Victor Manuel Garcia <
> > > > victor.gar...@beeva.com > wrote:
> > > >
> > > > > Hi guys,
> > > > > In my opinion we can graduate from the incubator. I think we all
> well
> > > > > controlled procedures, regardless of new features that also will be
> > > > > improved or adding . For example we need to greatly improve the
> > > > > documentation, but i since  is not necesary for graduation.
> > > > >
> > > > > +1 for graduation
> > > > >
> > > > > congrats for the work...!!!
> > > > >
> > > > > 2016-02-04 9:13 GMT+01:00 Alexander Bezzubov  > > > >:
> > > > >
> > > > > > Jakob,
> > > > > >
> > > > > > thank you for pointing this out, it is exactly as you describe
> > (there
> > > > > were
> > > > > > 3 releases since joining the incubator)
> > > > > >
> > > > > > If we could keep this thread focused on graduation and get more
> > > > oppinions
> > > > > > from other participants - that would awesome!
> > > > > >
> > > > > > Its great to see people volonteering to help with particular
> > features
> > > > for
> > > > > > the next release here, but please feel free to fork the thread
> for
> > > > > further
> > > > > > discussion on technical details.
> > > > > >
> > > > > > --
> > > > > > Alex
> > > > > >
> > > > > > On Thu, Feb 4, 2016, 08:51 Jakob Homan  > > > > wrote:
> > > > > >
> > > > > > > Hey all-
> > > > > > >A data point and observation from an ASF Member and
> Incubator
> > > PMC
> > > > > > > Member...
> > > > > > >
> > > > > > >Moon is correct that readiness for graduation is a function
> of
> > > > > > > community development and adherence to the Apache Way, rather
> any
> > > > > > > specific feature or tech milestones.  Since entering Incubator,
> > > > > > > Zeppelin's had two relatively easy releases, has finished the
> > > > > > > incubation checklist
> > > > > > > (http://incubator.apache.org/projects/zeppelin.html), has
> added
> > > new
> > > > > > > commiters, etc.  In short, Zeppelin's in a good position to
> > > graduate
> > > > > > > from my perspective.
> > > > > > >
> > > > > > >Resolution of specific PRs should be handled in a speedy
> > matter,
> > > > > > > but there doesn't seem to be any di

Re: March 2016 Report

2016-02-28 Thread mina lee 
If there is no one already working on, I'd like to take charge this time.

On Mon, Feb 29, 2016 at 8:50 AM Alexander Bezzubov  wrote:

> Hi people,
>
> Are there anybody working on March incubator report?
>
> --
> Alex
>
> On Fri, Feb 26, 2016 at 4:16 AM, Marvin Humphrey 
> wrote:
>
> > Greetings, {podling} developers!
> >
> > This is a reminder that your report is due next Wednesday, March
> > 2nd.  Details below.
> >
> > Best,
> >
> > Marvin Humphrey, Report Manager for March, on behalf of the
> > Incubator PMC
> >
> > ---
> >
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 16 March 2016, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, March 2nd).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > http://wiki.apache.org/incubator/March2016
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

Re: March 2016 Report

2016-02-29 Thread Mina Lee 
Hi developers,
here is the draft report for march 2016.
Please review and feel free to add if I missed something.


Zeppelin

A collaborative data analytics and visualization tool for distributed,
general-purpose data processing systems such as Apache Spark, Apache Flink,
etc.

Zeppelin has been incubating since 2014-12-23.

Three most important issues to address in the move towards graduation:

  1. Prove PPMC's maturity by handling dispute in community gracefully
  2. Community growth: more committers from different organizations

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  Updating long term roadmap [1] to embrace community needs is in
discussion.

  [1]
http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-users/201602.mbox/browser

How has the community developed since the last report?

  Traffic in users@ and dev@ grew: +38 subscribers in @dev, +83 subscribers
in users@ since last report.
  Talks at several conferences are scheduled [2].

  [2] https://cwiki.apache.org/confluence/display/ZEPPELIN/Community

How has the project developed since the last report?

  209 patches have been merged from 42 different contributors since last
report.
  Integration to JDBC, Apache HBase, Elasticsearch, Scalding, Tachyon has
been added.
  Authentication and notebook authorization have implemented.

Date of last release:

  2016-01-22

When were the last committers or PMC members elected?

  2016-01-16

On Mon, Feb 29, 2016 at 4:20 PM, Alexander Bezzubov  wrote:

> Mina, thanks a lot for taking care!
>
> Please feel free to post draft here so we can help you with it.
>
> --
> Alex
>
> On Mon, Feb 29, 2016 at 1:00 PM, mina lee  wrote:
>
> > If there is no one already working on, I'd like to take charge this time.
> >
> > On Mon, Feb 29, 2016 at 8:50 AM Alexander Bezzubov 
> wrote:
> >
> > > Hi people,
> > >
> > > Are there anybody working on March incubator report?
> > >
> > > --
> > > Alex
> > >
> > > On Fri, Feb 26, 2016 at 4:16 AM, Marvin Humphrey 
> > > wrote:
> > >
> > > > Greetings, {podling} developers!
> > > >
> > > > This is a reminder that your report is due next Wednesday, March
> > > > 2nd.  Details below.
> > > >
> > > > Best,
> > > >
> > > > Marvin Humphrey, Report Manager for March, on behalf of the
> > > > Incubator PMC
> > > >
> > > > ---
> > > >
> > > > Dear podling,
> > > >
> > > > This email was sent by an automated system on behalf of the Apache
> > > > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > > > prepare your quarterly board report.
> > > >
> > > > The board meeting is scheduled for Wed, 16 March 2016, 10:30 am PDT.
> > > > The report for your podling will form a part of the Incubator PMC
> > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > > before the board meeting, to allow sufficient time for review and
> > > > submission (Wed, March 2nd).
> > > >
> > > > Please submit your report with sufficient time to allow the Incubator
> > > > PMC, and subsequently board members to review and digest. Again, the
> > > > very latest you should submit your report is 2 weeks prior to the
> board
> > > > meeting.
> > > >
> > > > Thanks,
> > > >
> > > > The Apache Incubator PMC
> > > >
> > > > Submitting your Report
> > > >
> > > > --
> > > >
> > > > Your report should contain the following:
> > > >
> > > > *   Your project name
> > > > *   A brief description of your project, which assumes no knowledge
> of
> > > > the project or necessarily of its field
> > > > *   A list of the three most important issues to address in the move
> > > > towards graduation.
> > > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> > be
> > > > aware of
> > > > *   How has the community developed since the last report
> > > > *   How has the project developed since the last report.
> > > >
> > > > This should be appended to the Incubator Wiki page at:
> > > >
> > > > http://wiki.apache.org/incubator/March2016
> > > >
> > > > Note: This is manually populated. You may need to wait a little
> before
> > > > this page is created from a template.
> > > >
> > > > Mentors
> > > > ---
> > > >
> > > > Mentors should review reports for their project(s) and sign them off
> on
> > > > the Incubator wiki page. Signing off reports shows that you are
> > > > following the project - projects that are not signed may raise alarms
> > > > for the Incubator PMC.
> > > >
> > > > Incubator PMC
> > > >
> > >
> >
>

Re: March 2016 Report

2016-03-01 Thread mina lee 
Can someone update incubator wiki if it's good? I cannot login somehow

On Mon, Feb 29, 2016 at 5:34 PM Mina Lee  wrote:

> Hi developers,
> here is the draft report for march 2016.
> Please review and feel free to add if I missed something.
>
> 
> Zeppelin
>
> A collaborative data analytics and visualization tool for distributed,
> general-purpose data processing systems such as Apache Spark, Apache Flink,
> etc.
>
> Zeppelin has been incubating since 2014-12-23.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Prove PPMC's maturity by handling dispute in community gracefully
>   2. Community growth: more committers from different organizations
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   Updating long term roadmap [1] to embrace community needs is in
> discussion.
>
>   [1]
>
> http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-users/201602.mbox/browser
>
> How has the community developed since the last report?
>
>   Traffic in users@ and dev@ grew: +38 subscribers in @dev, +83
> subscribers
> in users@ since last report.
>   Talks at several conferences are scheduled [2].
>
>   [2] https://cwiki.apache.org/confluence/display/ZEPPELIN/Community
>
> How has the project developed since the last report?
>
>   209 patches have been merged from 42 different contributors since last
> report.
>   Integration to JDBC, Apache HBase, Elasticsearch, Scalding, Tachyon has
> been added.
>   Authentication and notebook authorization have implemented.
>
> Date of last release:
>
>   2016-01-22
>
> When were the last committers or PMC members elected?
>
>   2016-01-16
>
> On Mon, Feb 29, 2016 at 4:20 PM, Alexander Bezzubov 
> wrote:
>
> > Mina, thanks a lot for taking care!
> >
> > Please feel free to post draft here so we can help you with it.
> >
> > --
> > Alex
> >
> > On Mon, Feb 29, 2016 at 1:00 PM, mina lee  wrote:
> >
> > > If there is no one already working on, I'd like to take charge this
> time.
> > >
> > > On Mon, Feb 29, 2016 at 8:50 AM Alexander Bezzubov 
> > wrote:
> > >
> > > > Hi people,
> > > >
> > > > Are there anybody working on March incubator report?
> > > >
> > > > --
> > > > Alex
> > > >
> > > > On Fri, Feb 26, 2016 at 4:16 AM, Marvin Humphrey 
> > > > wrote:
> > > >
> > > > > Greetings, {podling} developers!
> > > > >
> > > > > This is a reminder that your report is due next Wednesday, March
> > > > > 2nd.  Details below.
> > > > >
> > > > > Best,
> > > > >
> > > > > Marvin Humphrey, Report Manager for March, on behalf of the
> > > > > Incubator PMC
> > > > >
> > > > > ---
> > > > >
> > > > > Dear podling,
> > > > >
> > > > > This email was sent by an automated system on behalf of the Apache
> > > > > Incubator PMC. It is an initial reminder to give you plenty of time
> > to
> > > > > prepare your quarterly board report.
> > > > >
> > > > > The board meeting is scheduled for Wed, 16 March 2016, 10:30 am
> PDT.
> > > > > The report for your podling will form a part of the Incubator PMC
> > > > > report. The Incubator PMC requires your report to be submitted 2
> > weeks
> > > > > before the board meeting, to allow sufficient time for review and
> > > > > submission (Wed, March 2nd).
> > > > >
> > > > > Please submit your report with sufficient time to allow the
> Incubator
> > > > > PMC, and subsequently board members to review and digest. Again,
> the
> > > > > very latest you should submit your report is 2 weeks prior to the
> > board
> > > > > meeting.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > The Apache Incubator PMC
> > > > >
> > > > > Submitting your Report
> > > > >
> > > > > --
> > > > >
> > > > > Your report should contain the following:
> > > > >
> > > > > *   Your project name
> > > > > *   A brief description of your project, which assumes no knowledge
> > of
> > > > > the project or necessarily of its field
> > > > > *   A list of the three most important issues to address in the
> move
> > > > > towards graduation.
> > > > > *   Any issues that the Incubator PMC or ASF Board might wish/need
> to
> > > be
> > > > > aware of
> > > > > *   How has the community developed since the last report
> > > > > *   How has the project developed since the last report.
> > > > >
> > > > > This should be appended to the Incubator Wiki page at:
> > > > >
> > > > > http://wiki.apache.org/incubator/March2016
> > > > >
> > > > > Note: This is manually populated. You may need to wait a little
> > before
> > > > > this page is created from a template.
> > > > >
> > > > > Mentors
> > > > > ---
> > > > >
> > > > > Mentors should review reports for their project(s) and sign them
> off
> > on
> > > > > the Incubator wiki page. Signing off reports shows that you are
> > > > > following the project - projects that are not signed may raise
> alarms
> > > > > for the Incubator PMC.
> > > > >
> > > > > Incubator PMC
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Graduate Zeppelin from the Incubator

2016-04-04 Thread mina lee 
+1

On Tue, Apr 5, 2016 at 10:55 AM Hyung Sung Shim  wrote:

> sincerely +1
>
> 2016-04-05 9:39 GMT+09:00 Anthony Corbacho :
>
> > +1
> >
> > On Tuesday, 5 April 2016, Kevin (Sangwoo) Kim 
> wrote:
> >
> > > We've got great commubity and great developers,
> > > +1 for graduation!
> > >
> > >
> > >
> > > 2016년 4월 5일 (화) 오전 9:10, Alexander Bezzubov  > > >님이 작성:
> > >
> > > > Enthusiastic +1 for moving on to a community vote
> > > >
> > > >
> > > >
> > > > On Tue, Apr 5, 2016 at 8:33 AM, Jongyoul Lee  > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, Apr 5, 2016 at 3:50 AM, Luciano Resende <
> > luckbr1...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Note that Graduation has nothing to do with code readiness (e.g
> > > > > enterprise
> > > > > > readiness) as you can see also in the DISCLAIMER.
> > > > > >
> > > > > > Its all about community and The Apache Way of community over
> code.
> > > > > >
> > > > > > On Monday, April 4, 2016, Prabhjyot Singh <
> > prabhjyotsi...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I was expecting this (
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-203680677
> > > > > > > ) to get merged, that or one of R/sparkR interpreter.
> > > > > > > With that a definite +1.
> > > > > > >
> > > > > > > We do need to work more on enterprise readiness like making it
> > more
> > > > > > secure,
> > > > > > > have better authorization.
> > > > > > >
> > > > > > > On 4 April 2016 at 22:04, 강민우  > > 
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > Sent from Outlook Mobile
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 4, 2016 at 8:54 AM -0700, "Bruno Bonnin" <
> > > > > > bbon...@gmail.com 
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > 2016-04-04 17:45 GMT+02:00 DuyHai Doan  > > 
> > > > > > > >:
> > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > On Mon, Apr 4, 2016 at 5:41 PM, Victor Manuel Garcia <
> > > > > > > > > victor.gar...@beeva.com  >
> > wrote:
> > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > 2016-04-04 17:37 GMT+02:00 Ahyoung Ryu <
> > > ahyoungry...@gmail.com 
> > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > > BIG +1 for graduating Zeppelin.
> > > > > > > > > > > There is no more reason to delay this.
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Ahyoung
> > > > > > > > > > >
> > > > > > > > > > > 2016년 4월 5일 (화) 오전 12:08, Luciano Resende <
> > > > > luckbr1...@gmail.com 
> > > > > > > >님이
> > > > > > > > 작성:
> > > > > > > > > > >
> > > > > > > > > > > > +1 on graduating Zeppelin
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Apr 4, 2016 at 4:24 AM, moon soo Lee <
> > > > > m...@apache.org 
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Since last answer from Damien, there hasn't been
> much
> > > > > > > discussions
> > > > > > > > > for
> > > > > > > > > > > > > graduation.
> > > > > > > > > > > > > If all concerns are answered and explained well
> > enough,
> > > > > then
> > > > > > > > shell
> > > > > > > > > we
> > > > > > > > > > > > move
> > > > > > > > > > > > > on to the vote?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > moon
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Wed, Feb 17, 2016 at 10:41 AM Corneau Damien <
> > > > > > > > > > cornead...@gmail.com  >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Jeff,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > You can find the list of PPMC here [1], although
> it
> > > > > doesn't
> > > > > > > > > include
> > > > > > > > > > > the
> > > > > > > > > > > > > > affiliations.
> > > > > > > > > > > > > > We do not currently have commiters only status in
> > the
> > > > > > > project.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Informations about how to become a Committer is
> > > inside
> > > > > the
> > > > > > > > > > > Contributing
> > > > > > > > > > > > > > document of the project [2]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > For the selection, we follow the usual Apache
> > > Process:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > * Discussion on inviting a new member is created
> on
> > > the
> > > > > > > > @private
> > > > > > > > > > > > mailing
> > > > > > > > > > > > > > list (any PPMC can create a discussion)
> > > > > > > > > > > > > > * PPMCs are voting on that thread
> > > > > > > > > > > > > > * If the vote is a success, an invite will be
> sent
> > to
> > > > > that
> > > > > > > > > person,
> > > > > > > > > >

Re: [VOTE] Graduate Zeppelin from the Incubator

2016-04-05 Thread mina lee 
+1

On Tue, Apr 5, 2016 at 4:52 PM Anthony Corbacho 
wrote:

> +1
>
> On Tuesday, 5 April 2016, Kevin (Sangwoo) Kim  wrote:
>
> > +1
> >
> >
> > 2016년 4월 5일 (화) 오후 4:46, Bruno Bonnin  >님이
> > 작성:
> >
> > > +1
> > >
> > > 2016-04-05 9:30 GMT+02:00 moon soo Lee  >:
> > >
> > > > Dear Community,
> > > >
> > > > Based on the positive discussion, I'm calling for the community VOTE
> > > > to graduate Apache Zeppelin (incubating) to top level project (TLP).
> > > >
> > > > Please vote on the resolution pasted below.
> > > >
> > > > [ ] +1 Graduate Apache Zeppelin from the Incubator.
> > > > [ ] +0 Don't care.
> > > > [ ] -1 Don't graduate Apache Zeppelin from the Incubator because…
> > > >
> > > > This is a community vote and everyone is invited to participate. PPMC
> > > > votes should be marked binding.
> > > >
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > If this VOTE succeeds, a similar VOTE will commence on the
> > > > general@incubator mailing list. If that vote also succeeds,
> > > > we will submit the resolution to be included in the agenda
> > > > of the next Apache board meeting.
> > > >
> > > > Many thanks to our mentors and everyone else for the support.
> > > >
> > > > My vote is +1 (binding)
> > > >
> > >
> >
>

Re: [VOTE] Graduate Zeppelin from the Incubator

2016-04-13 Thread mina lee 
+1 (binding)

On Tue, Apr 12, 2016 at 5:51 PM, enzo 
wrote:

> +1
>
> Enzo
> e...@smartinsightsfromdata.com
>
>
>
> > On 11 Apr 2016, at 15:49, Jongyoul Lee  wrote:
> >
> > +1 (binding)
> >
> > On Mon, Apr 11, 2016 at 11:21 PM, Bruno Bonnin 
> wrote:
> >
> >> +1
> >>
> >>
> >> 2016-04-11 15:48 GMT+02:00 moon soo Lee :
> >>
> >>> Dear Community,
> >>>
> >>> Based on the positive discussion, I'm calling for the community VOTE
> >>> to graduate Apache Zeppelin (incubating) to top level project (TLP).
> >>>
> >>> Please vote on the resolution pasted below.
> >>>
> >>> [ ] +1 Graduate Apache Zeppelin from the Incubator.
> >>> [ ] +0 Don't care.
> >>> [ ] -1 Don't graduate Apache Zeppelin from the Incubator because…
> >>>
> >>> This is a community vote and everyone is invited to participate. PPMC
> >>> votes should be marked binding.
> >>>
> >>> This vote will be open for at least 72 hours.
> >>>
> >>> If this VOTE succeeds, a similar VOTE will commence on the
> >>> general@incubator mailing list. If that vote also succeeds,
> >>> we will submit the resolution to be included in the agenda
> >>> of the next Apache board meeting.
> >>>
> >>> Many thanks to our mentors and everyone else for the support.
> >>>
> >>> My vote is +1 (binding)
> >>>
> >>> Apache Zeppelin top-level project resolution:
> >>> 
> >>>
> >>> WHEREAS, the Board of Directors deems it to be in the best
> >>> interests of the Foundation and consistent with the
> >>> Foundation's purpose to establish a Project Management
> >>> Committee charged with the creation and maintenance of
> >>> open-source software, for distribution at no charge to
> >>> the public, related to a collaborative data analytics and
> >>> visualization tool for general-purpose data processing systems.
> >>>
> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>> Committee (PMC), to be known as the "Apache Zeppelin Project",
> >>> be and hereby is established pursuant to Bylaws of the
> >>> Foundation; and be it further
> >>>
> >>> RESOLVED, that the Apache Zeppelin Project be and hereby is
> >>> responsible for the creation and maintenance of software
> >>> related to a collaborative data analytics and
> >>> visualization tool for general-purpose data processing systems; and be
> it
> >>> further
> >>>
> >>> RESOLVED, that the office of "Vice President, Apache Zeppelin" be
> >>> and hereby is created, the person holding such office to
> >>> serve at the direction of the Board of Directors as the chair
> >>> of the Apache Zeppelin Project, and to have primary responsibility
> >>> for management of the projects within the scope of
> >>> responsibility of the Apache Zeppelin Project; and be it further
> >>>
> >>> RESOLVED, that the persons listed immediately below be and
> >>> hereby are appointed to serve as the initial members of the
> >>> Apache Zeppelin Project:
> >>>
> >>> * Alexander Bezzubov 
> >>> * Anthony Corbacho 
> >>> * Damien Corneau 
> >>> * Felix Cheung 
> >>> * Jongyoul Lee 
> >>> * Kevin Sangwoo Kim 
> >>> * Lee Moon Soo 
> >>> * Mina Lee 
> >>> * Prabhjyot Singh 
> >>>
> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lee Moon Soo
> >>> be appointed to the office of Vice President, Apache Zeppelin, to
> >>> serve in accordance with and subject to the direction of the
> >>> Board of Directors and the Bylaws of the Foundation until
> >>> death, resignation, retirement, removal or disqualification,
> >>> or until a successor is appointed; and be it further
> >>>
> >>> RESOLVED, that the initial Apache Zeppelin PMC be and hereby is
> >>> tasked with the creation of a set of bylaws intended to
> >>> encourage open development and increased participation in the
> >>> Apache Zeppelin Project; and be it further
> >>>
> >>> RESOLVED, that the Apache Zeppelin Project be and hereby
> >>> is tasked with the migration and rationalization of the Apache
> >>> Incubator Zeppelin podling; and be it further
> >>>
> >>> RESOLVED, that all responsibilities pertaining to the Apache
> >>> Incubator Zeppelin podling encumbered upon the Apache Incubator
> >>> Project are hereafter discharge.
> >>>
> >>
> >
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
>
>

[jira] [Created] (ZEPPELIN-72) Paragraph status stays pending after restarting interpreter

2015-05-07 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-72:


 Summary: Paragraph status stays pending after restarting 
interpreter
 Key: ZEPPELIN-72
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-72
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee


Paragraph's status stays 'PENDING' after restarting spark interpreter if there 
were paragraphs with PENDING status before restarting interpreter process. It 
should be 'ABORT' instead.



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

[jira] [Created] (ZEPPELIN-309) Redirect to created/cloned notebook page on notebook creation/clone

2015-09-15 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-309:
-

 Summary: Redirect to created/cloned notebook page on notebook 
creation/clone
 Key: ZEPPELIN-309
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-309
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee
Priority: Minor


Currently when user create/clone notebook it stays in same page. It will be 
more user friendly to redirect to create/clone notebook page after this event.



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

[jira] [Created] (ZEPPELIN-329) Notebook copied in file system level should be reflected in notebook list

2015-09-30 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-329:
-

 Summary: Notebook copied in file system level should be reflected 
in notebook list
 Key: ZEPPELIN-329
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-329
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee


When user creates notebook by copying {notebookId}/note.json to 
ZEPPELIN_NOTEBOOK_DIR, this notebook is not reflected to Zeppelin's notebook 
list until user restarts Zeppelin.



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

[jira] [Created] (ZEPPELIN-407) Improv

2015-11-08 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-407:
-

 Summary: Improv
 Key: ZEPPELIN-407
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-407
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Mina Lee






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

[jira] [Created] (ZEPPELIN-420) Improve notebook clone behavior

2015-11-14 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-420:
-

 Summary: Improve notebook clone behavior
 Key: ZEPPELIN-420
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-420
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee
Assignee: Mina Lee


When user clones notebook, it clones all the information of the notebook even 
that shouldn't be copied such as paragraph id, job id, paragraph 
status(running, pending)
Instead of adding clone paragraphs itself, should create new paragraphs and 
copy only the contents(code, result, title) to new paragraph.



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

[jira] [Created] (ZEPPELIN-421) Remove deprecated spark properties from interpreter ui

2015-11-14 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-421:
-

 Summary: Remove deprecated spark properties from interpreter ui
 Key: ZEPPELIN-421
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-421
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee


`spark.home`, `spark.yarn.jar` are deprecated so keeping them makes user 
confusing.



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

[jira] [Created] (ZEPPELIN-495) Cannot run interpreters with distribution package

2015-12-08 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-495:
-

 Summary: Cannot run interpreters with distribution package
 Key: ZEPPELIN-495
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-495
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee
Assignee: Mina Lee


Cannot run interpreters other than SparkInterpreter with distribution package 
after https://github.com/apache/incubator-zeppelin/pull/485

How to reproduce
$ mvn clean package -Pbuild-distr
$ cd 
ZEPPELIN_HOME/zeppelin-distribution/target/zeppelin-0.6.0-incubating-SNAPSHOT/zeppelin-0.6.0-incubating-SNAPSHOT
$ ./bin/interpreter.sh -p 14242 -d interpreter/md
Error: Could not find or load main class 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer



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

[jira] [Created] (ZEPPELIN-537) Improve behavior of reloading notebooks from storage

2015-12-27 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-537:
-

 Summary: Improve behavior of reloading notebooks from storage
 Key: ZEPPELIN-537
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-537
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Mina Lee


When there is a notebook add/modify/delete in storage level, Zeppelin reload 
this changes only when user set ZEPPELIN_NOTEBOOK_RELOAD_FROM_STORAGE to be 
true.

Downside of current behavior are:
- Everytime client requests note list, it reloads notes from storage.
- If user reload the page during the paragraph is in RUNNING status, status of 
the paragraph will change to ABORT even if it's running

Will handle this issue by providing reloading button in home page



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

[jira] [Created] (ZEPPELIN-572) pyspark interpreter doesn't work on yarn-client

2016-01-05 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-572:
-

 Summary: pyspark interpreter doesn't work on yarn-client
 Key: ZEPPELIN-572
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-572
 Project: Zeppelin
  Issue Type: Bug
Reporter: Mina Lee
Assignee: Mina Lee


```
Py4JJavaError: An error occurred while calling 
z:org.apache.spark.api.python.PythonRDD.collectAndServe.
: org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in 
stage 1.0 failed 4 times, most recent failure: Lost task 0.3 in stage 1.0 (TID 
8, 103-42-01.sc1.verticloud.com): org.apache.spark.SparkException: 
Error from python worker:
  /usr/bin/python: No module named pyspark
PYTHONPATH was:
  
/var/storage/sdf1/nm-local/usercache/moon/filecache/35/spark-assembly-1.5.2-hadoop2.7.1.jar
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at 
org.apache.spark.api.python.PythonWorkerFactory.startDaemon(PythonWorkerFactory.scala:163)
at 
org.apache.spark.api.python.PythonWorkerFactory.createThroughDaemon(PythonWorkerFactory.scala:86)
at 
org.apache.spark.api.python.PythonWorkerFactory.create(PythonWorkerFactory.scala:62)
at org.apache.spark.SparkEnv.createPythonWorker(SparkEnv.scala:135)
at org.apache.spark.api.python.PythonRunner.compute(PythonRDD.scala:101)
at org.apache.spark.api.python.PythonRDD.compute(PythonRDD.scala:70)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:300)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:264)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)
at org.apache.spark.scheduler.Task.run(Task.scala:88)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Driver stacktrace:
at 
org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1283)
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1271)
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1270)
at 
scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
at 
org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1270)
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:697)
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:697)
at scala.Option.foreach(Option.scala:236)
at 
org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:697)
at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1496)
at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1458)
at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1447)
at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
at 
org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:567)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1824)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1837)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1850)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1921)
at org.apache.spark.rdd.RDD$$anonfun$collect$1.apply(RDD.scala:909)
at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:147)
at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:108)
at org.apache.spark.rdd.RDD.withScope(RDD.scala:310)
at org.apache.spark.rdd.RDD.collect(RDD.scala:908)
at 
org.apache.spark.api.python.PythonRDD$.collectAndServe(PythonRDD.scala:405)
at 
org.apache.spark.api.python.PythonRDD.collectAndServe(PythonRDD.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:231)
at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:379)
at py4j.Gateway.invoke(Gateway.java:259)
at py4j.commands.AbstractCommand.invokeM

[jira] [Created] (ZEPPELIN-630) Introduce new way of dependency loading to intepreter

2016-01-25 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-630:
-

 Summary: Introduce new way of dependency loading to intepreter
 Key: ZEPPELIN-630
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-630
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Mina Lee


Currently dependency loading feature(%dep) is dedicated to spark interpreter 
dependencies are loaded during Zeppelin runtime.
When user wants to include external libraries to other interpreter than spark, 
user needs to download the library, add this to ZEPPELIN_CLASSPATH by editting 
`bin/zeppelin-daemon.sh` or `bin/interpreter.sh`.

I would like to suggest new way of dependency loading by enabling:
1. Download library via GUI 'interpreter' menu
2. Add downloaded library to interpreter's classpath at process initiation time.

Every interpreter can leverage this feature to load external libraries. For 
exampe, JDBC interpreter can get benefit from it by adding proper 
jdbc-connector in 'interpreter' menu without editing shell script.



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

[jira] [Created] (ZEPPELIN-846) Notebook list in nav bar is not scrollable

2016-05-10 Thread Mina Lee (JIRA) 
Mina Lee created ZEPPELIN-846:
-

 Summary: Notebook list in nav bar is not scrollable
 Key: ZEPPELIN-846
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-846
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Reporter: Mina Lee


Long notebook list in navigation bar is not scrollable after 
https://github.com/apache/incubator-zeppelin/pull/796 merged



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