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 Mon, 16 Mar 2009 22:43:50 GMT

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

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

With the new KeyValue format puts and deletes are put in the same format, KeyValue. We have
for delete types:
Delete
DeleteColumn
DeleteFamily
DeleteRow
The difference between Delete and DeleteColumn one would think is that DeleteColumn deletes
all versions and for a delete
you specify a version ts to delete.
But KeyValue only holds one ts, so the way I see it we have 3 options:
1. Not store the time of the delete and only use it in case of a Delete, 

2. Set ts to the time of the delete and not support delete explicit versions, but just delete
all versions.

3. Have an extra field to store the extra ts, so we have 2.

I think that nr 1 is the best way to go and if we remove all puts in memcache underneath a
delete we are not going to lose any functionality.
I'm not totally against nr 2 either, but would have made more sense if we didn't allow users
to set the timestamp.
Don't like nr. 3 since it requires and extra layer or something like that to keep the extra
ts.
 

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