[
https://issues.apache.org/jira/browse/OAK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986449#comment-13986449
]
Marcel Reutegger commented on OAK-1589:
---------------------------------------
bq. There is a check in the getIdFromPath method that should prevent such long
ids.
This does not seem to work. I added a test on the NodeStore level in revision
http://svn.apache.org/r1591559
The long id is not prevented and with MongoDB 2.4.x the merge succeeds even
though the document could not be added. As noted earlier by Julian, MongoDB 2.6
fixes this and now correctly fails the insert/update.
> MongoDocumentStore fails to report error for keys that are too long
> -------------------------------------------------------------------
>
> Key: OAK-1589
> URL: https://issues.apache.org/jira/browse/OAK-1589
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Julian Reschke
> Priority: Minor
>
> The MongoDocumentStore fails to report an error when the key length exceeds
> the allowable width in MongoDB.
> This can be fixed by using a newer version of MongoDB (mongodb 2.5.5 -- see
> https://jira.mongodb.org/browse/SERVER-5290)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
