[
https://issues.apache.org/jira/browse/HBASE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710183#action_12710183
]
ryan rawson commented on HBASE-1304:
------------------------------------
I'm just thinking about what the usage scenario for deletes are - ultimately if
you want a different value instead of the original, you are better off to just
insert over, rather than to delete then put again.
Deleting immediately from the memcache is fine with me.
So the question is, do we want the complexity of deletes in the scan/get, or do
we want to take the higher hit on compactions - potentially. I don't think
compaction & deletion at the same time is overly complex, and if it makes the
scan/get simpler, then perhaps it would be best.
So far I don't think the scan delete tracker works - can you confirm/deny?
> New client server implementation of how gets and puts are handled.
> -------------------------------------------------------------------
>
> Key: HBASE-1304
> URL: https://issues.apache.org/jira/browse/HBASE-1304
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Erik Holstad
> Assignee: Jonathan Gray
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: hbase-1304-v1.patch, HBASE-1304-v2.patch,
> HBASE-1304-v3.patch, HBASE-1304-v4.patch, HBASE-1304-v5.patch,
> HBASE-1304-v6.patch, HBASE-1304-v7.patch
>
>
> Creating an issue where the implementation of the new client and server will
> go. Leaving HBASE-1249 as a discussion forum and will put code and patches
> here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
