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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/10/01 12:41:07 UTC

[jira] [Resolved] (OAK-342) [MongoMK] Revision id type inconsistency

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

Jukka Zitting resolved OAK-342.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6
         Assignee: Jukka Zitting

Patch committed in revision 1392271. Thanks!
                
> [MongoMK] Revision id type inconsistency
> ----------------------------------------
>
>                 Key: OAK-342
>                 URL: https://issues.apache.org/jira/browse/OAK-342
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mk
>    Affects Versions: 0.6
>            Reporter: Mete Atamel
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: OAK-342.patch
>
>
> RevisionId in MicroKernel API is String but it's (along with baseRevId) stored as long in MongoMK. This is fine but MongoMK implementation is currently inconsistent with revisionId type. Sometimes it uses String and sometimes it uses long for revisionId and this results in a lot of String->long conversions throughout the code. 
> I think as soon as revisonId hits MongoMK, it should be converted to long and long should be the only type for revisionId throughout MongoMK code.

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