Github user benmccann commented on the issue: https://github.com/apache/spark/pull/13986 >At least run the script that updates the deps/ files to see that impact Can you point me to the script you're referring to? > Figure out what the upside is in updating to 1.8 The reason I'm proposing this change is that Avro 1.8 makes the generated classes serializable so that you can create RDDs containing Avro objects. > Note any potential incompatibilities here Here's the list of incompatible changes from the [changelog](https://github.com/apache/avro/blob/master/CHANGES.txt): * AVRO-1334. Java: Update versions of many dependencies. (scottcarey, cutting) * AVRO-997. Java: For enum values, no longer sometimes permit any Object whose toString() names an enum symbol, but rather always require use of distinct enum types. (Sean Busbey via cutting) * AVRO-1602. Java: Remove Dapper-style RPC trace facility. This seems unused and has been a source of build problems. (cutting) * AVRO-1586. Build against Hadoop 2. With this change the avro-mapred and trevni-avro JARs without a hadoop1 or hadoop2 Maven classifier are Hadoop 2 artifacts. To use with Hadoop 1, set the classifier to hadoop1. (tomwhite) * AVRO-1502. Java: Generated classes now implement Serializable. Generated classes need to be regenerated to use this release. (cutting)
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org