Hi folks,
Alyssa (cc’ed) and I manage the mango build on the AMPLab Jenkins. I will start
to look into this to see what the connection between the mango builds and the
failing Spark builds are.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
>
some of the Jenkins executors (things
like the JAVA_HOME getting changed), but we haven’t been able to root cause
those issues.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
> On Nov 4, 2017, at 10:50 PM, Frank A Nothaft wrote:
>
&g
rk/commit/0077bfcb93832d93009f73f4b80f2e3d98fd2fa4>,
which masks this issue in the unit tests. With this error, you can’t use the
ParquetAvroOutputFormat from a application running on Spark 2.2.0.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
> On May
, which causes the no
such method exception to occur.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
> On May 1, 2017, at 11:31 AM, Ryan Blue wrote:
>
> Frank,
>
> The issue you're running into is caused by using parquet-avro wit
and 1.8.0.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
> On May 1, 2017, at 12:00 PM, Ryan Blue wrote:
>
> Thanks for the extra context, Frank. I agree that it sounds like your problem
> comes from the conflict between your Jars an
, because the
MethodNotFoundError is thrown from the internals of the
ParquetAvroOutputFormat, not from code in our project.
Regards,
Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466
> On May 1, 2017, at 12:33 PM, Ryan Blue wrote:
>
> Michael, I t
