Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17163
> AVRO-1502 requires recompilation of some generated classes.
This sounds bad, because it basically means it's not backwards compatible
(which is the concern @steveloughran raised). Spark also has modules that
depend on Flume, which is called out explicitly in AVRO-1502 as being affected.
So at this point, let me ask: is this upgrade *necessary* for parquet, as in,
what breaks if we don't upgrade?
The Spark bug talks about a new feature in avro that would be nice for
Spark, but there are known workarounds for it, or one can use the spark-avro
library. So if it breaks backwards compatibility, I'm not so sure it's worth
the upgrade.
If parquet really needs the new avro, it might be possible to hack things -
relocating the new avro classes just for the parquet dependencies, but that
would be pretty nasty.
---
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]
