You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/09/09 00:58:28 UTC
[jira] [Updated] (HBASE-2609) Harmonize the Get and Delete
operations
[ https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HBASE-2609:
---------------------------------
Fix Version/s: (was: 1.0.0)
(was: 0.99.0)
0.99.1
> Harmonize the Get and Delete operations
> ---------------------------------------
>
> Key: HBASE-2609
> URL: https://issues.apache.org/jira/browse/HBASE-2609
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Jeff Hammerbacher
> Fix For: 0.99.1
>
>
> In my work on HBASE-2400, implementing deletes for the Avro server felt quite awkward. Rather than the clean API of the Get object, which allows restrictions on the result set from a row to be expressed with addColumn, addFamily, setTimeStamp, setTimeRange, setMaxVersions, and setFilters, the Delete object hides these semantics behind various constructors to deleteColumn[s] an deleteFamily. From my naive vantage point, I see no reason why it would be a bad idea to mimic the Get API exactly, though I could quite possibly be missing something. Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)