Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 13 Feb 2013 19:24:14 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12611345.1349962202918.285744.1360783454258@arcas>
In-Reply-To: <JIRA.12611345.1349962202918@arcas>
References: <JIRA.12611345.1349962202918@arcas>
Subject: [jira] [Commented] (ACCUMULO-803) Add Reverse Logical Time as a
 Time Type
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577846#comment-13577846 ] 

Josh Elser commented on ACCUMULO-803:
-------------------------------------

bq. As far as 1.5, this patch was in way before 1.5 feature freeze date. I would kinda like to see it go in 1.5, but this is partially because I feel guilty for dropping the ball on this. On the other hand, I do want to see work on 1.5 really start to settle and focus solely on bug fixes.

I agree that it would be a shame to not include a feature that we had code sitting around for such a long time.
                
> Add Reverse Logical Time as a Time Type
> ---------------------------------------
>
>                 Key: ACCUMULO-803
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-803
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.5.0
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>         Attachments: ACCUMULO-803.patch, ACCUMULO-803.patch, RLTest.java
>
>
> In a context where we are doing aggregation/combination of multiple values for a given key it may be useful to iterate over the values associated with that key in the order in which the mutations were applied (FIFO), instead of the FILO order that seems to occur when using {{TimeType.LOGICAL}}. 
> I encountered when implemeting a checkAndPut operation that would ensure that the previous value was expected before putting a new value. In this case, if the previous value was not as expected, the mutation would be ignored. 
> Perhaps it is useful in a general case?

--
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