One key thing I forgot to mention is that I changed the avro version to 1.7.7 to get AVRO-1476.
I took a closer look at the jars, and what I noticed is that the assembly jars that work do not have the org.apache.avro.mapreduce package packaged into the assembly. For spark-1.0.1, org.apache.avro.mapreduce is always found. When creating an assembly from an older download of Spark 1.0.0, this package doesn't exist. In a recent download of Spark 1.0.0, the generated assembly with any HDP version also has org.apache.avro.mapreduce. I recompiled against the new download, and it also has the same problems even with an older version of HDP. So I think the bottom line issue here is that the generated assemblies that include org.apache.avro.mapreduce seems to cause this issue. If I use the older Spark 1.0.0 version, I am able to create assemblies that work. I noticed that assemblies generated from the newer versions are indeed bigger so it seems a bug was perhaps fixed to ensure that all dependencies are pulled into the final assembly, but is now causing this symptom that I have reported... Thanks, Ron On Monday, August 4, 2014 10:39 AM, Steve Nunez <snu...@hortonworks.com> wrote: Hmm. Fair enough. I hadn¹t given that answer much thought and on reflection think you¹re right in that a profile would just be a bad hack. On 8/4/14, 10:35, "Sean Owen" <so...@cloudera.com> wrote: >What would such a profile do though? In general building for a >specific vendor version means setting hadoop.verison and/or >yarn.version. Any hard-coded value is unlikely to match what a >particular user needs. Setting protobuf versions and so on is already >done by the generic profiles. > >In a similar vein, I am not clear on why there's a mapr profile in the >build. Its versions are about to be out of date and won't work with >upcoming Hbase changes for example. > >(Elsewhere in the build I think it wouldn't hurt to clear out >cloudera-specific profiles and releases too -- they're not in the pom >but are in the distribution script. It's the vendor's problem.) > >This isn't any argument about being purist but just that I am not sure >these are things that the project can meaningfully bother with. > >It makes sense to set vendor repos in the pom for convenience, and >makes sense to run smoke tests in Jenkins against particular versions. > >$0.02 >Sean > >On Mon, Aug 4, 2014 at 6:21 PM, Steve Nunez <snu...@hortonworks.com> >wrote: >> I don¹t think there is an hwx profile, but there probably should be. >> -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
