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, 30 Mar 2009 00:46:50 GMT

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

Erik Holstad commented on HBASE-1249:

I agree with most of the things that you are saying about letting the user setting the timestamp
in some places but not in others and I think that it is a good point. 
But the reason that I brought this up is because I would like to keep the code as simple as
possible and not have to deal with all these special cases, which DeleteFamily with the ability
of setting the timestamp in the past brings, not to make it more complicated. But I guess
we can do the same way as with the settable timestamps for the inserts, put a red warning
label on there and try to explain in there what will actually happen when making a delete
like that, because as a new user I think it is hard to fully understand all the details of
your actions even though they make perfect sense.
So I guess that leaves us with number 2 where we have 2 different cases to take care of, one
with DeleteFamily and one without.

> 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-StoreFile-v1.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,

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

View raw message