hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Gray (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1619) Change the familyMap<byte[], List<KeyValue>> in put to familyMap<ImmutableBytesWritable, List<KeyValue>>
Date Tue, 07 Jul 2009 07:58:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727973#action_12727973
] 

Jonathan Gray commented on HBASE-1619:
--------------------------------------

Doesn't this raise the instantiable Bytes vs continuing down the unpleasant road of IBW question?
 See, I can't even write it out!

> Change the familyMap<byte[], List<KeyValue>> in put to  familyMap<ImmutableBytesWritable,
List<KeyValue>>
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1619
>                 URL: https://issues.apache.org/jira/browse/HBASE-1619
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.0
>            Reporter: Erik Holstad
>            Priority: Minor
>             Fix For: 0.20.0
>
>
> While working on the HBase tap and scheme for Cascading I came across a situation where
you want to add a bunch of KeyValues to a Put object.
> Looking at the code for putting KeyValues in put we copy the family from the KeyValue
and use that as a key. So I was thinking that it might be a good idea to just "point"
> into the KV by using a ImmutableBytesWritable and use that as the key instead. This is
going to be good when working with MR jobs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message