Thanks Hitesh for your inputs. I've not come across any issues yet. So, I can safely assume that putting Tez jars in Hadoop class path will not cause the map reduce programs to use Tez framework unless it is enabled. Let me know if my understanding it not correct.
--Bala G. On Mon, Jul 7, 2014 at 4:10 PM, Hitesh Shah <[email protected]> wrote: > Hi > > For the most part, there should be no issues as most dependencies that Tez > pulls in are compatible with the hadoop version that it is compiled with ( > 2.2 or higher ). The major issue to be aware of is that you should compile > Tez against the same version of hadoop/mapreduce that is deployed on your > cluster. The tez dependency jars contain both 3rd party deps as well as > hadoop jars ( hdfs, common, yarn client-side and mapreduce client-side ) - > if there is a version mismatch, this may cause a problem when the tez > directory is added to the hadoop classpath. > > Have you seen any issues? If yes, could you provide more details? > > thanks > — Hitesh > > > On Jul 7, 2014, at 3:44 PM, Bala Krishna Gangisetty <[email protected]> > wrote: > > > I'm wondering, from operational point of view, are there any specifics > that need special attention to make MRv2 and Tez frameworks coexist in > harmony? I heard that putting Tez jars in Hadoop class path would impact > the mapred behavior, even when Tez is not enabled (either through > mapred-site.xml, or Hive). Could someone throw more light and share > thoughts on it? > > > > --Bala G. > >
