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

Jean-Daniel Cryans commented on HBASE-631:
------------------------------------------

{quote}
+ So, if a user adds a cell at row/columnfamily name - i.e. if row is x and 
column family is y:, at x/y: - they can use get to extract that explicit cell 
but if they use x/y: with getFull/getRow, the behavior will be different; 
instead they will get the explicit x/y: cell AND all other cells that might on 
the 'y:' column family such y:1, y:2, etc. I think this is OK.
{quote}

I think that mixing cells in row/columnfamily and row/columnfamily:key in a 
same family is bad design choice but yes, getRow would fetch everything. In 
fact, I didn't think about this situation so thanks for pointing out! I guess I 
will update the comments.

Regards the code snippet, there may be more than one family specified (I know, 
only one was asked but it was easier permitting many families) so I guess I 
will leave it like that.

Thanks for the review stack!

> HTable.getRow() for only a column family
> ----------------------------------------
>
>                 Key: HBASE-631
>                 URL: https://issues.apache.org/jira/browse/HBASE-631
>             Project: Hadoop HBase
>          Issue Type: New Feature
>    Affects Versions: 0.1.2
>            Reporter: Ryan Lynch
>            Assignee: Jean-Daniel Cryans
>         Attachments: hbase-631-v1.patch
>
>
> I have a use case in which we want to access all the columns for a supplied 
> column family while also avoiding the overhead of reading any other column 
> families.  There seems to be no method for doing this but doing a quick dive 
> into the code it "seems" like this should be relatively easy to allow. This 
> seems desirable since the architecture describes column families being stored 
> together so reading only a single column family should be a lighter operation.

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

Reply via email to