Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CCCDFEF9E for ; Wed, 13 Feb 2013 16:52:12 +0000 (UTC) Received: (qmail 98507 invoked by uid 500); 13 Feb 2013 16:52:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 98476 invoked by uid 500); 13 Feb 2013 16:52:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 98466 invoked by uid 99); 13 Feb 2013 16:52:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 16:52:12 +0000 Date: Wed, 13 Feb 2013 16:52:12 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Turner updated ACCUMULO-803: ---------------------------------- Attachment: RLTest.java > 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