hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Holstad (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1249) Rearchitecting of server, client, API, key format, etc for 0.20
Date Tue, 28 Apr 2009 17:07:30 GMT

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

Erik Holstad commented on HBASE-1249:
-------------------------------------

Extra comment on Jonathan's  comment:
About deletes.
So when you enter a new file and walking down the lists doing the sorted merge between the
data in the store, the gets and the previous deletes. When finding a delete in the current
file this is just added to the newDelete list. Since all data is sorted the inserts in the
newDeletes list will be sorted too. When the current store is done and if you need to go to
the next one you first merge the oldDeletes with the new and use these for checking in the
next storefile.

Same thing is done for the gets, in the case of a GetRow/GetFamilies call.

Versions are just a different list that sits in the GetXServer. This list is handled differently
depending on what kind of call it is. In case of a GetColumns call this list is getting smaller
and smaller and for the other cases it gets bigger and bigger. This is because columns are
removed from the column list in the case of a GetColumns call, so the versions list has to
match.

> 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
>
>         Attachments: HBASE-1249-Example-v1.pdf, HBASE-1249-Example-v2.pdf, HBASE-1249-GetQuery-v1.pdf,
HBASE-1249-GetQuery-v2.pdf, HBASE-1249-GetQuery-v3.pdf, HBASE-1249-GetQuery-v4.pdf, HBASE-1249-StoreFile-v1.pdf,
HBASE-1249-StoreFile-v4.pdf
>
>
> 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,
etc...

-- 
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