That is a regression of upgrading Zeppelin to spark 2.0/Scala 2.11. as it
broke existing functionality, hopefully whoever did the upgrade will fix...
Please report to Zeppelin, thanks and good find!
On Aug 26, 2016 8:39 AM, "Frank Dekervel" wrote:
> Hello,
>
> i added this to my Dockerfile to en
Hello,
i added this to my Dockerfile to end up with a working setup:
RUN cp /opt/zeppelin/interpreter/ignite/scala*jar
/opt/zeppelin/interpreter/flink/
which would copy:
scala-compiler-2.11.7.jar
scala-library-2.11.7.jar
scala-parser-combinators_2.11-1.0.4.jar
scala-reflect-2.11.7.jar
scala-xml
I'm glad you were able to work it out!
Your setup is somewhat unique, and as Zeppelin is the result of multiple
drive-by commits, interesting and unexpected things happen in the tail
cases.
Could you please report your problem and solution on the Zeppelin user
list? What you've discovered may in
Hello,
Sorry for the spam, but i got it working after copying all scala libraries
from another interpreter to the interpreter/flink directory. so i think the
error is the scala libraries are missing from the binary release in the
zeppelin/interpreters/flink/ directory. For now i'm adding the copy
Hello,
For reference, below is the dockerfile i used to build the zeppelin image
(basically just openjdk 8 with the latest binary release of zeppelin)
the "docker-entrypoint.sh" script is just starting zeppelin.sh (oneliner)
FROM openjdk:alpine
RUN apk add --no-cache bash snappy
ARG ZEPPELIN_VE
Hello Trevor,
Thanks for your suggestion. The log does not explain a lot: on the flink
side i don't see anything at all, on the zeppelin side i see this:
Your suggestion sounds plausible, as i always start zeppelin, and then
change the configuration from local to remote.. however, port 6123 locall
Frank,
can you post the zeppelin flink log please?
You can probably find it in zeppelin_dir/logs/*flink*.log
You've got a few moving pieces here. I've never run zeppelin against Flink
in a docker container. But I think the Zeppelin-Flink log is the first
place to look.
You say you can't get
Hey Frank,
Saw your post on the Zeppelin list yesterday. I can look at it later this
morning, but my gut feeling is a ghost Zeppelin daemon is running in the
background and it's local Flink is holding the port 6123. This is fairly
common and would explain the issue.
Idk if you're on linux or win
Hi!
There are some people familiar with the Zeppelin integration. CCing
Till and Trevor. Otherwise, you could also send this to the Zeppelin
community.
Cheers,
Max
On Wed, Aug 24, 2016 at 12:58 PM, Frank Dekervel wrote:
> Hello,
>
> for reference:
>
> i already found out that "connect to existi
Hello,
for reference:
i already found out that "connect to existing process" was my error here:
it means connecting to an existing zeppelin interpreter, not an existing
flink cluster. After fixing my error, i'm now in the same situation as
described here:
https://stackoverflow.com/questions/3868
Hello,
I try to set up apache zeppelin with a flink cluster (one jobmanager, one
task manager).
What i did was using the dockerfiles in flink-contrib/docker-flink + the
latest binary release of apache zeppelin with all interpreters:
https://github.com/apache/flink/blob/master/flink-contrib/docke
11 matches
Mail list logo
