Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17163
oh, this sucks. Find anyone who experienced "The great protobuf update of
2012" and ask them if they want to do it again.
Looking at the issues, AVRO-997 catches out "wrong" use of an API: if that
can be identified at compile time, it could be corrected in uses of Spark's
dependencies, then that sounds like something they should do pre-emptively.
Returning to Hadoop, it's use is in in bits of the YARN API, as far as I
Can see.
1. Bumping up to a later avro version for Hadoop 3 will help sync things
up, at the cost of "yet another piece of pain for everyone who upgrades".
2. Somehow shading that stuff, separate story.
Classpaths are the enemy of my life. If I had to split my working life
between "classpath hell", "interesting code" and "wondering why my tests are
all broken", I think CP may have the edge
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
