[
https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2609:
-------------------------
Assignee: stack
Release Note: Align Delete class with Get class. Change all delete* method
names to add* instead. For example, change deleteColumn to addColumn (as in
add-this-column to the Delete specification). Deprecate the old.
Status: Patch Available (was: Open)
> 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
> Assignee: stack
> Fix For: 0.99.2
>
> Attachments: 2609.txt, 2609v2.txt
>
>
> 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)
