You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2012/10/16 15:37:02 UTC

[jira] [Commented] (ACCUMULO-803) Add Reverse Logical Time as a Time Type

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

Keith Turner commented on ACCUMULO-803:
---------------------------------------

looks good a few comments.

   * can you make this patch against trunk/1.5 instead of 1.4?  I do not think this is something we would want to add to 1.4.
   * the user manual would need some mention of this new feature, in docs/src/user_manual/chapters/table_configuration.tex I think
   * in MockTable I think you should subtract from Long.MAX_VALUE instead of Integer.MAX_VALUE for consistency, even though its an int is being subtracted
                
> 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.4.2
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>         Attachments: ACCUMULO-803.patch
>
>
> 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