[
https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183482#comment-14183482
]
Andrew Purtell edited comment on HBASE-2609 at 10/24/14 9:03 PM:
-----------------------------------------------------------------
Looks fine but if you put it in 0.98 the javadoc needs a small update to the
@deprecated text.
was (Author: apurtell):
Looks fine but if you put it in 0.98 the javadoc needs a small update to
@since.
> 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)
