[
https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184388#comment-14184388
]
stack commented on HBASE-2609:
------------------------------
Across Scan, Get, and Delete addFamily/addColumn/setTimestamp, there is not
enough coherency to make an Interface -- what to cal it? Delete has addColumns
vs addColumn and sometimes on addColumn it takes a timestamp, sometimes not.
I always thought Get and Delete should be the same since about specifying
coordinates. Could work on this in another issue.
Let me commit this for now.
> 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)
