Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 24 Feb 2013 04:50:14 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12615206.1352312396224.329484.1361681414082@arcas>
In-Reply-To: <JIRA.12615206.1352312396224@arcas>
References: <JIRA.12615206.1352312396224@arcas>
Subject: [jira] [Updated] (HBASE-7114) Increment does not extend Mutation
 but probably should
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-7114:
-------------------------

    Priority: Critical  (was: Minor)

Marking critical so we don't forget.  The setWriteToWAL stuff here I don't see in current implementation of Increment.  Was it removed?  Meantime, hbase-7900 is making Increment implement Mutation so it 'fixes' this issue?

(Ted brought this up over in rb on 7900 patch)
                
> Increment does not extend Mutation but probably should
> ------------------------------------------------------
>
>                 Key: HBASE-7114
>                 URL: https://issues.apache.org/jira/browse/HBASE-7114
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.96.0
>            Reporter: Andrew Purtell
>            Priority: Critical
>
> Increment is the only operation in the class of mutators that does not extend Mutation. It mostly duplicates what Mutation provides, but not quite. The signatures for setWriteToWAL and getFamilyMap are slightly different. This can be inconvenient because it requires special case code and therefore could be considered an API design nit. Unfortunately it is not a simple change: The interface is marked stable and the internals of the family map are different from other mutation types. The latter is why I suspect this was not addressed when Mutation was introduced.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira