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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/03/26 10:55:15 UTC

[jira] [Resolved] (OAK-1602) 512 byte shard key limit in MongoMK

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

Thomas Mueller resolved OAK-1602.
---------------------------------

    Resolution: Fixed

Revision 1581772 (doc)

> 512 byte shard key limit in MongoMK
> -----------------------------------
>
>                 Key: OAK-1602
>                 URL: https://issues.apache.org/jira/browse/OAK-1602
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 0.20
>
>
> OAK-333 solves the 1000 byte path limit in MongoMK, however there is an even lower limit for shard keys: 512 bytes, according to the MongoDB documentation http://docs.mongodb.org/manual/reference/limits/#shard-key-limitations
> It looks like the only change we need to do is change the default settings to the lower values. I don't think this will affect most applications, as the longest paths are still lower than that.
> While we do that, we should also improve the documentation for the DocumentNodeStore (explicitly document the limits).



--
This message was sent by Atlassian JIRA
(v6.2#6252)