accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-803) Add Reverse Logical Time as a Time Type
Date Fri, 25 Oct 2013 20:36:33 GMT

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

John Vines commented on ACCUMULO-803:
-------------------------------------

I feel bad about bumping this to 1.7 because it got bumped to 1.6 with a patch. [~alfarris@prodigy.net]
or [~kturner], is it possible for you to do a revised patch for 1.6?

> 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
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-803-3.patch, 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message