Re: Zeppelin Studio Proposal

2019-08-28 Thread Jongyoul Lee 
Sounds great!!

On Tue, Aug 27, 2019 at 1:31 AM ieglonewolf ieglonewolf <
ieglonew...@gmail.com> wrote:

> I would like to add
>
> Our key motive for us to start ZEPPELIN-4138
>  here is to build a
> UI
> system on top of zeppelin service which is intuitive and very much
> functional.
> Moreover doing it the right way is the key to scalability. I would like to
> request each and every member of this community to help us develop this.
>
> Please provide your valuable feedback
>
> Thanks folks!
>
> On Mon, Aug 26, 2019 at 9:24 PM Xun Liu  wrote:
>
> > Zeppelin is very much in need of a front end developed using VUE.js
> > front-end technology.
> > Thank you for your contribution. :-)
> >
> > Xun Liu
> > Best Regards
> >
> > On Aug 26, 2019, at 9:21 PM, Jeff Zhang  wrote:
> >
> > + user mail list
> >
> >
> > Thanks Malay for the proposal. The zeppelin frontend do needs some
> rework.
> >
> > Overall, your proposal make sense to me. User experience and performance
> > are the 2 key things we need to improve in the frontend.
> > I left some comments in the design doc.
> >
> >
> > Malay Majithia  于2019年8月23日周五 下午6:10写道：
> >
> >> Hey Folks,
> >>
> >> Regarding ZEPPELIN-4138
> >> , we have come up
> >> with the design document(draft) and the task list for the same:
> >>
> >>
> >>  Zeppelin Studio - Design Document
> >> <
> https://docs.google.com/document/d/1FCAVgODwYtpXUxtTdB3JVGrVNEqEzpUA6Dcyi6xvpB4/edit?usp=drive_web
> >
> >>
> >>  Zeppelin Studio - Task list
> >> <
> https://docs.google.com/spreadsheets/d/1cPI4t0Wqm0JVxjkLPNpah1I9vW-XmEcd9eDYISTV0iw/edit?usp=drive_web
> >
> >>
> >> POC code is available on GitHub
> >> .
> >>
> >> Sneak peek of the proposed interface:
> >> 
> >>
> >>
> >> Please review it and provide your valuable feedback.
> >>
> >> Best Regards
> >> Malay Majithia
> >>
> >>
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
> >
> >
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: Zeppelin Studio Proposal

2019-08-28 Thread Ivan Shapovalov 
Hey All,

The idea of refactoring UI sounds great!
Ever considered theia (https://github.com/theia-ide/theia)? May save a
couple of ages for community.

Regards,
Ivan

ср, 28 авг. 2019 г. в 11:31, Jongyoul Lee :

> Sounds great!!
>
> On Tue, Aug 27, 2019 at 1:31 AM ieglonewolf ieglonewolf <
> ieglonew...@gmail.com> wrote:
>
>> I would like to add
>>
>> Our key motive for us to start ZEPPELIN-4138
>>  here is to build a
>> UI
>> system on top of zeppelin service which is intuitive and very much
>> functional.
>> Moreover doing it the right way is the key to scalability. I would like to
>> request each and every member of this community to help us develop this.
>>
>> Please provide your valuable feedback
>>
>> Thanks folks!
>>
>> On Mon, Aug 26, 2019 at 9:24 PM Xun Liu  wrote:
>>
>> > Zeppelin is very much in need of a front end developed using VUE.js
>> > front-end technology.
>> > Thank you for your contribution. :-)
>> >
>> > Xun Liu
>> > Best Regards
>> >
>> > On Aug 26, 2019, at 9:21 PM, Jeff Zhang  wrote:
>> >
>> > + user mail list
>> >
>> >
>> > Thanks Malay for the proposal. The zeppelin frontend do needs some
>> rework.
>> >
>> > Overall, your proposal make sense to me. User experience and performance
>> > are the 2 key things we need to improve in the frontend.
>> > I left some comments in the design doc.
>> >
>> >
>> > Malay Majithia  于2019年8月23日周五 下午6:10写道：
>> >
>> >> Hey Folks,
>> >>
>> >> Regarding ZEPPELIN-4138
>> >> , we have come up
>> >> with the design document(draft) and the task list for the same:
>> >>
>> >>
>> >>  Zeppelin Studio - Design Document
>> >> <
>> https://docs.google.com/document/d/1FCAVgODwYtpXUxtTdB3JVGrVNEqEzpUA6Dcyi6xvpB4/edit?usp=drive_web
>> >
>> >>
>> >>  Zeppelin Studio - Task list
>> >> <
>> https://docs.google.com/spreadsheets/d/1cPI4t0Wqm0JVxjkLPNpah1I9vW-XmEcd9eDYISTV0iw/edit?usp=drive_web
>> >
>> >>
>> >> POC code is available on GitHub
>> >> .
>> >>
>> >> Sneak peek of the proposed interface:
>> >> 
>> >>
>> >>
>> >> Please review it and provide your valuable feedback.
>> >>
>> >> Best Regards
>> >> Malay Majithia
>> >>
>> >>
>> >
>> > --
>> > Best Regards
>> >
>> > Jeff Zhang
>> >
>> >
>> >
>>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>


-- 
Ivan Shapovalov
Kharkov, Ukraine

Re: Zeppelin Studio Proposal

2019-08-28 Thread CHALLA 
👏 great.

On Wed, Aug 28, 2019 at 4:04 PM Ivan Shapovalov 
wrote:

> Hey All,
>
> The idea of refactoring UI sounds great!
> Ever considered theia (https://github.com/theia-ide/theia)? May save a
> couple of ages for community.
>
> Regards,
> Ivan
>
> ср, 28 авг. 2019 г. в 11:31, Jongyoul Lee :
>
>> Sounds great!!
>>
>> On Tue, Aug 27, 2019 at 1:31 AM ieglonewolf ieglonewolf <
>> ieglonew...@gmail.com> wrote:
>>
>>> I would like to add
>>>
>>> Our key motive for us to start ZEPPELIN-4138
>>>  here is to build
>>> a UI
>>> system on top of zeppelin service which is intuitive and very much
>>> functional.
>>> Moreover doing it the right way is the key to scalability. I would like
>>> to
>>> request each and every member of this community to help us develop this.
>>>
>>> Please provide your valuable feedback
>>>
>>> Thanks folks!
>>>
>>> On Mon, Aug 26, 2019 at 9:24 PM Xun Liu  wrote:
>>>
>>> > Zeppelin is very much in need of a front end developed using VUE.js
>>> > front-end technology.
>>> > Thank you for your contribution. :-)
>>> >
>>> > Xun Liu
>>> > Best Regards
>>> >
>>> > On Aug 26, 2019, at 9:21 PM, Jeff Zhang  wrote:
>>> >
>>> > + user mail list
>>> >
>>> >
>>> > Thanks Malay for the proposal. The zeppelin frontend do needs some
>>> rework.
>>> >
>>> > Overall, your proposal make sense to me. User experience and
>>> performance
>>> > are the 2 key things we need to improve in the frontend.
>>> > I left some comments in the design doc.
>>> >
>>> >
>>> > Malay Majithia  于2019年8月23日周五 下午6:10写道：
>>> >
>>> >> Hey Folks,
>>> >>
>>> >> Regarding ZEPPELIN-4138
>>> >> , we have come
>>> up
>>> >> with the design document(draft) and the task list for the same:
>>> >>
>>> >>
>>> >>  Zeppelin Studio - Design Document
>>> >> <
>>> https://docs.google.com/document/d/1FCAVgODwYtpXUxtTdB3JVGrVNEqEzpUA6Dcyi6xvpB4/edit?usp=drive_web
>>> >
>>> >>
>>> >>  Zeppelin Studio - Task list
>>> >> <
>>> https://docs.google.com/spreadsheets/d/1cPI4t0Wqm0JVxjkLPNpah1I9vW-XmEcd9eDYISTV0iw/edit?usp=drive_web
>>> >
>>> >>
>>> >> POC code is available on GitHub
>>> >> .
>>> >>
>>> >> Sneak peek of the proposed interface:
>>> >> 
>>> >>
>>> >>
>>> >> Please review it and provide your valuable feedback.
>>> >>
>>> >> Best Regards
>>> >> Malay Majithia
>>> >>
>>> >>
>>> >
>>> > --
>>> > Best Regards
>>> >
>>> > Jeff Zhang
>>> >
>>> >
>>> >
>>>
>>
>>
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>>
>
>
> --
> Ivan Shapovalov
> Kharkov, Ukraine
>
>

Compile error

2019-08-28 Thread afancy 
Dear all,

I use the following command to compile the source code on Ubuntu 16.04, but
got the following error. Could you help? thanks
mvn -e clean package -DskipTests -Pspark-2.3 -Phadoop-2.6 -Pr -Pscala-2.11
-Pr

/ afancy


[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ... SUCCESS [
16.782 s]
[INFO] Zeppelin: Interpreter .. SUCCESS [
15.618 s]
[INFO] Zeppelin: Interpreter API .. SUCCESS [
48.745 s]
[INFO] Zeppelin: Interpreter Parent ... SUCCESS [
 1.562 s]
[INFO] Zeppelin: Zengine .. SUCCESS [
13.692 s]
[INFO] Zeppelin: Display system apis .. SUCCESS [
13.278 s]
[INFO] Zeppelin: Groovy interpreter ... SUCCESS [
 3.623 s]
[INFO] Zeppelin: Spark Parent . SUCCESS [
 3.073 s]
[INFO] Zeppelin: Spark Shims .. SUCCESS [
 2.808 s]
[INFO] Zeppelin: Spark1 Shims . SUCCESS [
10.583 s]
[INFO] Zeppelin: Spark2 Shims . SUCCESS [
 9.562 s]
[INFO] Zeppelin: Python interpreter ... SUCCESS [
 8.850 s]
[INFO] Zeppelin: Spark Interpreter  SUCCESS [
27.756 s]
[INFO] Zeppelin: Spark Scala Parent ... SUCCESS [
 6.425 s]
[INFO] Zeppelin: Spark Interpreter Scala_2.10 . SUCCESS [
10.443 s]
[INFO] Zeppelin: Spark Interpreter Scala_2.11 . SUCCESS [
 9.480 s]
[INFO] Zeppelin: Spark Interpreter Scala_2.12 . SUCCESS [
10.540 s]
[INFO] Zeppelin: Spark dependencies ... SUCCESS [
32.757 s]
[INFO] Zeppelin: Shell interpreter  SUCCESS [
 7.767 s]
[INFO] Zeppelin: Submarine interpreter  SUCCESS [
 7.759 s]
[INFO] Zeppelin: Markdown interpreter . SUCCESS [
 1.920 s]
[INFO] Zeppelin: Angular interpreter .. SUCCESS [
 1.130 s]
[INFO] Zeppelin: Livy interpreter . SUCCESS [
 7.521 s]
[INFO] Zeppelin: HBase interpreter  SUCCESS [
11.602 s]
[INFO] Zeppelin: Apache Pig Interpreter ... SUCCESS [
20.028 s]
[INFO] Zeppelin: JDBC interpreter . SUCCESS [
 2.921 s]
[INFO] Zeppelin: File System Interpreters . SUCCESS [
 2.375 s]
[INFO] Zeppelin: Flink  SUCCESS [
22.011 s]
[INFO] Zeppelin: Apache Ignite interpreter  SUCCESS [
 7.318 s]
[INFO] Zeppelin: Kylin interpreter  SUCCESS [
 1.477 s]
[INFO] Zeppelin: Lens interpreter . SUCCESS [
 8.949 s]
[INFO] Zeppelin: Apache Cassandra interpreter . SUCCESS [
39.572 s]
[INFO] Zeppelin: Elasticsearch interpreter  SUCCESS [
 6.692 s]
[INFO] Zeppelin: BigQuery interpreter . SUCCESS [
 2.479 s]
[INFO] Zeppelin: Alluxio interpreter .. SUCCESS [
 7.018 s]
[INFO] Zeppelin: Scio . SUCCESS [
30.180 s]
[INFO] Zeppelin: Neo4j interpreter  SUCCESS [
 8.619 s]
[INFO] Zeppelin: Sap .. SUCCESS [
 1.423 s]
[INFO] Zeppelin: Scalding interpreter . SUCCESS [01:12
min]
[INFO] Zeppelin: Java interpreter . SUCCESS [
 1.267 s]
[INFO] Zeppelin: Beam interpreter . FAILURE [
 9.666 s]
[INFO] Zeppelin: Hazelcast Jet interpreter  SKIPPED
[INFO] Zeppelin: Apache Geode interpreter . SKIPPED
[INFO] Zeppelin: web Application .. SKIPPED
[INFO] Zeppelin: Server ... SKIPPED
[INFO] Zeppelin: Jupyter Support .. SKIPPED
[INFO] Zeppelin: Plugins Parent ... SKIPPED
[INFO] Zeppelin: Plugin S3NotebookRepo  SKIPPED
[INFO] Zeppelin: Plugin GitHubNotebookRepo  SKIPPED
[INFO] Zeppelin: Plugin AzureNotebookRepo . SKIPPED
[INFO] Zeppelin: Plugin GCSNotebookRepo ... SKIPPED
[INFO] Zeppelin: Plugin ZeppelinHubRepo ... SKIPPED
[INFO] Zeppelin: Plugin FileSystemNotebookRepo  SKIPPED
[INFO] Zeppelin: Plugin StandardLauncher .. SKIPPED
[INFO] Zeppelin: Plugin Kubernetes StandardLauncher ... SKIPPED
[INFO] Zeppelin: Plugin SparkInterpreterLauncher .. SKIPPED
[INFO] Zeppelin: Plugin Docker Launcher ... SKIPPED
[INFO] Zeppelin: Plugin Cluster Launcher .. SKIPPED
[INFO] Zeppelin: Packaging distribution ... SKIPPED
[INFO] Zeppelin: R Interpreter  SKIPPED
[INFO]

[INFO] BUI

Spark Job URLs are http even though zeppelin and spark are configured with https

2019-08-28 Thread Tony Primerano 


Currently I have zeppelin and spark configured to run on https.

My notebook urls look like https://notebook.example.com:8443/ and my spark UI 
runs at https://notebook.example.com:4440/.

If I go to the http version of the spark ui I am redirected to the https 
version.  For example http://notebook.example.com:4040/ will redirect to 
https://notebook.example.com:4440/.

My problem is that when viewing a zeppelin notebook all the "SPARK JOB" URLs 
are http and not https.  You would think this wouldn't be a problem because 
SPARK JOB url http://notebook.example.com:4040/jobs/job?id=0 will just redirect 
to https://notebook.example.com:4440/jobs/job?id=0.  This redirect works fine 
when using curl or entering it directly into the address bar.

But when the SPARK JOB URL is clicked inside of zeppelin it does not redirect 
to the https:8443 url.   Because my zeppelin is configured with https it sends 
the Strict-Transport-Security HTTP header and Firefox changes the protocol and 
sends the user to https://notebook.example.com:4040/jobs/job?id=0 instead of 
https://notebook.example.com:4440/jobs/job?id=0.  4040 is the http port so this 
fails.

Can Zeppelin build the spark UI URLs using https instead of relying on a 
redirect from the spark UI?

My zeppelin-site.xml file has the zeppelin.server.strict.transport section 
commented out but I the Strict-Transport-Security HTTP header is sent by 
default when SSL is configured.  Setting the max-age=0 works around the issue 
but the correct path would be to build the Spark UI urls with https so we can 
use Strict-Transport-Security.

Is it possible to have Zeppelin build the spark UI URLs with https?  Maybe I am 
missing a configuration option?

Thanks in advance for any pointers or fixes!
Tony

Exception in thread "main" java.lang.IncompatibleClassChangeError: Implementing class

2019-08-28 Thread Krishnanand Khambadkone 
I am trying to buld zeppelin-0.8 on mac from source,  also tried the binary 
distribution but no matter how I build it,  I am not able to start the zeppelin 
daemon.  I always see this exception in the log file.

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Exception in thread "main" java.lang.IncompatibleClassChangeError: Implementing 
class

        at java.lang.ClassLoader.defineClass1(Native Method)

        at java.lang.ClassLoader.defineClass(ClassLoader.java:763)

        at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

        at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)

        at java.net.URLClassLoader.access$100(URLClassLoader.java:74)

        at java.net.URLClassLoader$1.run(URLClassLoader.java:369)

        at java.net.URLClassLoader$1.run(URLClassLoader.java:363)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.net.URLClassLoader.findClass(URLClassLoader.java:362)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

        at java.lang.ClassLoader.defineClass1(Native Method)

        at java.lang.ClassLoader.defineClass(ClassLoader.java:763)

        at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

        at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)

        at java.net.URLClassLoader.access$100(URLClassLoader.java:74)

        at java.net.URLClassLoader$1.run(URLClassLoader.java:369)

        at java.net.URLClassLoader$1.run(URLClassLoader.java:363)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.net.URLClassLoader.findClass(URLClassLoader.java:362)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

        at 
org.apache.zeppelin.server.ZeppelinServer.setupJettyServer(ZeppelinServer.java:312)

        at 
org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:222)

   
   -

   
   -

   -

   -

   
   -

Re: Exception in thread "main" java.lang.IncompatibleClassChangeError: Implementing class

2019-08-28 Thread Jeff Zhang 
Could you describe how you build zeppelin ? What is the maven command and
what is your jdk version ?

Krishnanand Khambadkone  于2019年8月29日周四 上午4:00写道：

> I am trying to buld zeppelin-0.8 on mac from source,  also tried the
> binary distribution but no matter how I build it,  I am not able to start
> the zeppelin daemon.  I always see this exception in the log file.
>
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
>
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
>
> Exception in thread "main" java.lang.IncompatibleClassChangeError:
> Implementing class
>
> at java.lang.ClassLoader.defineClass1(Native Method)
>
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
>
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
>
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
>
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
>
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
> at java.lang.ClassLoader.defineClass1(Native Method)
>
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
>
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
>
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
>
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
>
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
> at
> org.apache.zeppelin.server.ZeppelinServer.setupJettyServer(ZeppelinServer.java:312)
>
> at
> org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:222)
>
>
>-
>
>
>-
>-
>-
>
>
>-
>--
>
>
>

-- 
Best Regards

Jeff Zhang

Re: Spark Job URLs are http even though zeppelin and spark are configured with https

2019-08-28 Thread Jeff Zhang 
Could you create a ticket for this issue ?

Tony Primerano  于2019年8月29日周四 上午12:08写道：

>
> Currently I have zeppelin and spark configured to run on https.
>
> My notebook urls look like https://notebook.example.com:8443/ and my
> spark UI runs at https://notebook.example.com:4440/.
>
> If I go to the http version of the spark ui I am redirected to the https
> version.  For example http://notebook.example.com:4040/ will redirect to
> https://notebook.example.com:4440/.
>
> My problem is that when viewing a zeppelin notebook all the "SPARK JOB"
> URLs are http and not https.  You would think this wouldn't be a problem
> because SPARK JOB url http://notebook.example.com:4040/jobs/job?id=0 will
> just redirect to https://notebook.example.com:4440/jobs/job?id=0.  This
> redirect works fine when using curl or entering it directly into the
> address bar.
>
> But when the SPARK JOB URL is clicked inside of zeppelin it does not
> redirect to the https:8443 url.   Because my zeppelin is configured with
> https it sends the Strict-Transport-Security HTTP header and Firefox
> changes the protocol and sends the user to
> https://notebook.example.com:4040/jobs/job?id=0 instead of
> https://notebook.example.com:4440/jobs/job?id=0.  4040 is the http port
> so this fails.
>
> Can Zeppelin build the spark UI URLs using https instead of relying on a
> redirect from the spark UI?
>
> My zeppelin-site.xml file has the zeppelin.server.strict.transport section
> commented out but I the Strict-Transport-Security HTTP header is sent by
> default when SSL is configured.  Setting the max-age=0 works around the
> issue but the correct path would be to build the Spark UI urls with https
> so we can use Strict-Transport-Security.
>
> Is it possible to have Zeppelin build the spark UI URLs with https?  Maybe
> I am missing a configuration option?
>
> Thanks in advance for any pointers or fixes!
> Tony
>
>
>
>

-- 
Best Regards

Jeff Zhang

Re: Compile error

2019-08-28 Thread Jeff Zhang 
The problem is that there's no beam-runners-flink 2.0.0 for scala 2.10

https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink

There's several approach for it .

1. exclude beam module when building.  Add -pl !beam
2. Use -Pscala-2.10 -Pspark-1.6
3. Upgrade beam version to 2.5.0 which support scala 2.11


And please create a ticket for it.


afancy  于2019年8月28日周三 下午11:31写道：

> Dear all,
>
> I use the following command to compile the source code on Ubuntu 16.04,
> but got the following error. Could you help? thanks
> mvn -e clean package -DskipTests -Pspark-2.3 -Phadoop-2.6 -Pr -Pscala-2.11
> -Pr
>
> / afancy
>
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Zeppelin ... SUCCESS [
> 16.782 s]
> [INFO] Zeppelin: Interpreter .. SUCCESS [
> 15.618 s]
> [INFO] Zeppelin: Interpreter API .. SUCCESS [
> 48.745 s]
> [INFO] Zeppelin: Interpreter Parent ... SUCCESS [
>  1.562 s]
> [INFO] Zeppelin: Zengine .. SUCCESS [
> 13.692 s]
> [INFO] Zeppelin: Display system apis .. SUCCESS [
> 13.278 s]
> [INFO] Zeppelin: Groovy interpreter ... SUCCESS [
>  3.623 s]
> [INFO] Zeppelin: Spark Parent . SUCCESS [
>  3.073 s]
> [INFO] Zeppelin: Spark Shims .. SUCCESS [
>  2.808 s]
> [INFO] Zeppelin: Spark1 Shims . SUCCESS [
> 10.583 s]
> [INFO] Zeppelin: Spark2 Shims . SUCCESS [
>  9.562 s]
> [INFO] Zeppelin: Python interpreter ... SUCCESS [
>  8.850 s]
> [INFO] Zeppelin: Spark Interpreter  SUCCESS [
> 27.756 s]
> [INFO] Zeppelin: Spark Scala Parent ... SUCCESS [
>  6.425 s]
> [INFO] Zeppelin: Spark Interpreter Scala_2.10 . SUCCESS [
> 10.443 s]
> [INFO] Zeppelin: Spark Interpreter Scala_2.11 . SUCCESS [
>  9.480 s]
> [INFO] Zeppelin: Spark Interpreter Scala_2.12 . SUCCESS [
> 10.540 s]
> [INFO] Zeppelin: Spark dependencies ... SUCCESS [
> 32.757 s]
> [INFO] Zeppelin: Shell interpreter  SUCCESS [
>  7.767 s]
> [INFO] Zeppelin: Submarine interpreter  SUCCESS [
>  7.759 s]
> [INFO] Zeppelin: Markdown interpreter . SUCCESS [
>  1.920 s]
> [INFO] Zeppelin: Angular interpreter .. SUCCESS [
>  1.130 s]
> [INFO] Zeppelin: Livy interpreter . SUCCESS [
>  7.521 s]
> [INFO] Zeppelin: HBase interpreter  SUCCESS [
> 11.602 s]
> [INFO] Zeppelin: Apache Pig Interpreter ... SUCCESS [
> 20.028 s]
> [INFO] Zeppelin: JDBC interpreter . SUCCESS [
>  2.921 s]
> [INFO] Zeppelin: File System Interpreters . SUCCESS [
>  2.375 s]
> [INFO] Zeppelin: Flink  SUCCESS [
> 22.011 s]
> [INFO] Zeppelin: Apache Ignite interpreter  SUCCESS [
>  7.318 s]
> [INFO] Zeppelin: Kylin interpreter  SUCCESS [
>  1.477 s]
> [INFO] Zeppelin: Lens interpreter . SUCCESS [
>  8.949 s]
> [INFO] Zeppelin: Apache Cassandra interpreter . SUCCESS [
> 39.572 s]
> [INFO] Zeppelin: Elasticsearch interpreter  SUCCESS [
>  6.692 s]
> [INFO] Zeppelin: BigQuery interpreter . SUCCESS [
>  2.479 s]
> [INFO] Zeppelin: Alluxio interpreter .. SUCCESS [
>  7.018 s]
> [INFO] Zeppelin: Scio . SUCCESS [
> 30.180 s]
> [INFO] Zeppelin: Neo4j interpreter  SUCCESS [
>  8.619 s]
> [INFO] Zeppelin: Sap .. SUCCESS [
>  1.423 s]
> [INFO] Zeppelin: Scalding interpreter . SUCCESS [01:12
> min]
> [INFO] Zeppelin: Java interpreter . SUCCESS [
>  1.267 s]
> [INFO] Zeppelin: Beam interpreter . FAILURE [
>  9.666 s]
> [INFO] Zeppelin: Hazelcast Jet interpreter  SKIPPED
> [INFO] Zeppelin: Apache Geode interpreter . SKIPPED
> [INFO] Zeppelin: web Application .. SKIPPED
> [INFO] Zeppelin: Server ... SKIPPED
> [INFO] Zeppelin: Jupyter Support .. SKIPPED
> [INFO] Zeppelin: Plugins Parent ... SKIPPED
> [INFO] Zeppelin: Plugin S3NotebookRepo  SKIPPED
> [INFO] Zeppelin: Plugin GitHubNotebookRepo  SKIPPED
> [INFO] Zeppelin: Plugin AzureNotebookRepo . SKIPPED
> [INFO] Zeppelin: Plugin GCSNotebookRepo ... SKIPPED
> [INFO] Zeppelin: Plugin ZeppelinHubRepo ... SKIPPED
> [INFO] Zeppelin: Plugin File

Re: Compile error

2019-08-28 Thread xiufeng liu 
Dear Jeff,

Thanks a lot!
I have excluded the beam module, but I got another compile error. Could you
help to take a look? Thanks

/afancy

-
[WARNING] The requested profile "hadoop-2.6" could not be activated because
it does not exist.
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.6:npm (npm build) on project
zeppelin-web: Failed to run task: 'npm run build:dist' failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 3
(Exit value: 3) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.github.eirslett:frontend-maven-plugin:1.6:npm (npm build) on
project zeppelin-web: Failed to run task
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run task
at
com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:100)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by:
com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm
run build:dist' failed.
at
com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:63)
at
com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:62)
at
com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:94)
... 22 more
Caused by:
com.github.eirslett.maven.plugins.frontend.lib.ProcessExecutionException:
org.apache.commons.exec.ExecuteException: Process exited with an error: 3
(Exit value: 3)
at
com.github.eirslett.maven.plugins.frontend.lib.ProcessExecutor.execute(ProcessExecutor.java:82)
at
com.github.eirslett.maven.plugins.frontend.lib.ProcessExecutor.executeAndRedirectOutput(ProcessExecutor.java:64)
at
com.github.eirslett.maven.plugins.frontend.lib.NodeExecutor.executeAndRedirectOutput(NodeExecutor.java:29)
at
com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:58)
... 24 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
error: 3 (Exit value: 3)
at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:166)
at
com.github.eirslett.maven.plugins.frontend.lib.ProcessExecutor.execute(ProcessExecutor.java:74)
... 27 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

On Thu, Aug 29, 2019 at 3:25 AM Jeff Zhang  wrote:

> The problem is that there's no beam-runners-flink 2.0.0 for scala 2.10
>
> https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink
>
> There's several approach for it .
>
> 1. exclude beam module when building.  Add -pl !beam
> 2. Use -Pscala-2.10 -Pspark-1.6
> 3. Upgrade beam version to 2.5.0 which support scala 2.11
>
>
> And please create a ticket for it.
>
>
> afancy  于2019年8月28日周三 下午11:31写道：
>
>> Dear all,
>>
>> I use the following command to compile the source code on Ubuntu 16.04,
>> b