Absolutely right. Patch attached to
https://issues.apache.org/jira/browse/CASSANDRA-3449
On Wed, Nov 2, 2011 at 2:09 PM, Erik Forkalsrud wrote:
> On 11/01/2011 09:02 PM, Jonathan Ellis wrote:
>>
>> That doesn't make sense to me. CS:147 is
>>
>> columnFamilyKeyMap.put(row.key, row.cf
On 11/01/2011 09:02 PM, Jonathan Ellis wrote:
That doesn't make sense to me. CS:147 is
columnFamilyKeyMap.put(row.key, row.cf);
where cFKM is
Map columnFamilyKeyMap = new
HashMap();
So cFKM can't be null, and HashMap accomodates both null key and null
value, so I'm not
Are we doing anything wrong here? or can this be a bug in cassandra?
thanks
Ramesh
On Tue, Nov 1, 2011 at 11:02 PM, Jonathan Ellis wrote:
> That doesn't make sense to me. CS:147 is
>
> columnFamilyKeyMap.put(row.key, row.cf);
>
> where cFKM is
>
> Map columnFamilyKeyMap = new
That doesn't make sense to me. CS:147 is
columnFamilyKeyMap.put(row.key, row.cf);
where cFKM is
Map columnFamilyKeyMap = new
HashMap();
So cFKM can't be null, and HashMap accomodates both null key and null
value, so I'm not sure what there is to thorw NPE.
On Tue, Nov 1, 2