> ok, thanks. very strange then that i can run hive 1.2.1 and hive 2.0.0 >m/r jobs against the same hadoop cluster w/o issue > (different HS2, different MetaStore, but same hdfs data) but yet once i >switch to the HS2/2.0.0 tez chokes out - but works fine with the >HS2/1.2.1.
It is not particularly strange considering no development for MRv2 has happened in the mean-time - there's no difference in version dependencies between 2.0 & 1.2 for MRv2. Not so for Tez. > I'm thinking this is because the tez jars on hdfs have been built (bound >to) hive 1.2.1? I suspect the tez jars inside hive's classpath rather than the ones on HDFS. 0.8.2 is effectively a super-set of APIs in 0.7.4, so ending up with 0.7.x jars in the local classpath would work fine for hive-1.2.1, while when you run the same classpath with hive-2.0, it wouldn't work. Saw a PermGen error reported in a later email - the solution to all permgen issues was to leave JDK7 behind (End-of-Life April 2015) & use the Metaspace impl in JDK8, along with the G1GC to unload the garbage classes very fast. Cheers, Gopal
