Also, if both are defined , the framework will use RawComparator . I hope you have registered the comparator in a static block as follows
static { WritableComparator.define(PairOfInts.class, new Comparator()); } Regards Ravi Magham On Sat, Aug 31, 2013 at 1:23 PM, Ravi Kiran <ravikiranmag...@gmail.com>wrote: > Hi Adeel, > > The RawComparator is the fastest between the two as you avoid the need > to convert the byte stream to Writable objects for comparison . > > Regards > Ravi Magham > > > On Fri, Aug 30, 2013 at 11:16 PM, Adeel Qureshi <adeelmahm...@gmail.com>wrote: > >> For secondary sort I am implementing a RawComparator and providing that >> as sortComparator .. is that the faster way or using a WritableComparable >> as mapper output and defining a compareTo method on the key itself >> >> also what happens if both are defined, is one ignored >> > >