Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 26 Oct 2014 04:00:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12465264.1274697246000.339924.1414296034348@Atlassian.JIRA>
In-Reply-To: <JIRA.12465264.1274697246000@Atlassian.JIRA>
References: <JIRA.12465264.1274697246000@Atlassian.JIRA>
 <JIRA.12465264.1274697246965@arcas>
Subject: [jira] [Updated] (HBASE-2609) Harmonize the Get and Delete
 operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-2609:
-------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks for reviews.  Committed to branch-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
>            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
(v6.3.4#6332)