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-1249) Rearchitecting of server, client, API, key format, etc for 0.20
Date Tue, 10 Mar 2009 22:43:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680669#action_12680669

Jonathan Gray commented on HBASE-1249:

To be more clear about the API, above is a pseudo-api that doesn't make sense.  In the first
method with byte [][] columns, that would have to include families.  There's no such thing
as a column w/o a family.

My thought for a new API is to try and mirror the new key format.  Basically, for gets you'd
have a row, and then a set of keys that represented what you wanted to filter by.  If it's
columns, then you'd have keys that had both the family and the column.  If it's families,
you'd have the family in the key but an empty column value.  Do we support empty column values?
 if so, we might also make use of the extra type bits to add more info...

> Rearchitecting of server, client, API, key format, etc for 0.20
> ---------------------------------------------------------------
>                 Key: HBASE-1249
>                 URL: https://issues.apache.org/jira/browse/HBASE-1249
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Jonathan Gray
>            Priority: Blocker
>             Fix For: 0.20.0
> To discuss all the new and potential issues coming out of the change in key format (HBASE-1234):
zero-copy reads, client binary protocol, update of API (HBASE-880), server optimizations,

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

View raw message