[
https://issues.apache.org/jira/browse/OAK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996392#comment-13996392
]
Marcel Reutegger commented on OAK-1589:
---------------------------------------
I now also see TCK test failures. E.g.
{noformat}
Running org.apache.jackrabbit.oak.jcr.tck.ApiIT
Tests run: 1410, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 97.902 sec
<<< FAILURE!
testAddNonExisting(org.apache.jackrabbit.test.api.NodeAddMixinTest) Time
elapsed: 0.016 sec <<< ERROR!
com.google.common.util.concurrent.UncheckedExecutionException:
java.lang.IllegalArgumentException: Node name is too long:
/jcr:system/jcr:nodeTypes/XmixcreatedmixetagmixlanguagemixlastModifiedmixlifecyclemixlockablemixmimeTypemixreferenceablemixshareablemixsimpleVersionablemixtitlemixversionablerepAccessControllablerepImpersonatablerepMergeConflictrepRepoAccessControllablerepRetentionManageablerepVersionReferencerepVersionablePathstestmimeType
{noformat}
Also seen on travis: https://travis-ci.org/apache/jackrabbit-oak/builds/25052775
I think the implementation should not fail with an exception when an attempt is
made to read an item with a too long name.
> 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
> Fix For: 1.1
>
>
> 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)
