[
https://issues.apache.org/jira/browse/OAK-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615193#comment-13615193
]
Jukka Zitting commented on OAK-721:
-----------------------------------
bq. Could the index could be the "same name sibling index"?
Yes, that's the case here.
This looks like a regression from my recent change to make the "fake SNS" nodes
under /jcr:system/jcr:nodeTypes use the real SNS index syntax like
"jcr:propertyDefinition[2]" instead of dummy names like
"jcr:propertyDefinition2".
I'll update the JcrPathParser code to cope better with such path elements.
> NamePathMapperImpl: weird error message "index > 1"
> ---------------------------------------------------
>
> Key: OAK-721
> URL: https://issues.apache.org/jira/browse/OAK-721
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Thomas Mueller
> Priority: Minor
>
> I sometimes get the error with the message "index > 1" in NamePathMapperImpl.
> I have no idea what it means and why I get it.
--
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
