You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/09/19 11:50:51 UTC

[jira] [Updated] (OAK-1025) Keep value histories in NavigableMap

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

Marcel Reutegger updated OAK-1025:
----------------------------------

    Description: The revision/value maps are currently exposed as simple {{Maps}} only. This requires to look at all entries to find out, which one is the most recent valid value. The implementation should be changed to implement {{NavigableMap}} and preferably use {{Revision}} as key instead of the string representation. This avoids the rather frequent parsing and string formating of revisions.  (was: The revision/value maps are currently exposed as simple {{Map}}s only. This requires to look at all entries to find out, which one is the most recent valid value. The implementation should be changed to implement {{NavigableMap}} and preferably use {{Revision}} as key instead of the string representation. This avoids the rather frequent parsing and string formating of revisions.)
    
> Keep value histories in NavigableMap
> ------------------------------------
>
>                 Key: OAK-1025
>                 URL: https://issues.apache.org/jira/browse/OAK-1025
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>
> The revision/value maps are currently exposed as simple {{Maps}} only. This requires to look at all entries to find out, which one is the most recent valid value. The implementation should be changed to implement {{NavigableMap}} and preferably use {{Revision}} as key instead of the string representation. This avoids the rather frequent parsing and string formating of revisions.

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