hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2609) Harmonize the Get and Delete operations
Date Sun, 26 Oct 2014 05:34:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184409#comment-14184409

Hudson commented on HBASE-2609:

SUCCESS: Integrated in HBase-TRUNK #5703 (See [https://builds.apache.org/job/HBase-TRUNK/5703/])
HBASE-2609 Harmonize the Get and Delete operations (stack: rev 1d6c4678bb7964af34fb42a6c8bbf0553880bba3)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java

> 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: 2.0.0, 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

View raw message