Re: KeyRange in the CoumnFamilyInputFormat

2011-09-05 Thread Mick Semb Wever
On Mon, 2011-09-05 at 19:02 +0200, Mick Semb Wever wrote: > > ConfigHelper.setInputRange( > jobConf, > > partitioner.getTokenFactory().toString(partitioner.getToken(myKey)), > > partitioner.getTokenFactory().toString(partitioner.getToken(my

Re: KeyRange in the CoumnFamilyInputFormat

2011-09-05 Thread Mick Semb Wever
On Mon, 2011-09-05 at 18:18 +0300, Vitaly Vengrov wrote: > See these rows in the ColumnFamilyInputFormat.getSplits method : > > assert jobKeyRange.start_key == null : "only start_token supported"; > > assert jobKeyRange.end_key == null : "only end_token supported"; > > So, the

KeyRange in the CoumnFamilyInputFormat

2011-09-05 Thread Vitaly Vengrov
Hi guys. See these rows in the ColumnFamilyInputFormat.getSplits method : assert jobKeyRange.start_key == null : "only start_token supported"; assert jobKeyRange.end_key == null : "only end_token supported"; So, the question is why start_key and end_key aren't sup