I had trouble building zeppelin too. My coworker could get it to build on
his Mac though. However even after it built, when I ran my notebook it was
looking for files in /zeppelin/build/spark*. I moved over the files from
spark-dependencies/target/spark* into that directory, but now get a
NullPo
We were able to build 0.8 in the past without problems. However, when we tried
following the exact same steps on an identical VM last month we ran into the
same issues Darren is facing. Hard to say if it is the exact same problem, but
eventually I chased down this thread which seemed related to
Makes sense
Thank you Jeff !
On Sun, Dec 10, 2017 at 11:24 PM Jeff Zhang wrote:
>
> I am afraid currently there's no way to make ipython as default of
> %pyspark, but you can use %ipyspark to use ipython without this warning
> message.
>
> But making ipython as default is on my plan, for now I
Looks like master branch of Zeppelin still has compatibility issue with
Cloudera dependencies.
When built using
mvn clean package -DskipTests -Pspark-2.2 -Dhadoop.version=2.6.0-cdh5.12.1
-Phadoop-2.6 -Pvendor-repo -pl '!...list of excluded packages' -e
maven fails on jackson convergence error -
