[
https://issues.apache.org/jira/browse/OAK-8628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931469#comment-16931469
]
Vikas Saurabh commented on OAK-8628:
------------------------------------
[~reschke], while indeed it seems that {{TraversingCursor}} for
{{ALL_CHILDREN}} and {{PARENT}} path restrictions is preparing
{{MemoryNodeState}} with name to be path to node. But, then I think that
{code}
currentPath = PathUtils.concat(parentPath, name);
{code}
should've thrown an {{IllegalArgumentException}}. Could you point me to a test
that showed the stack mentioned in description.
> NodeStateUtils.isHidden expects names but get's called with paths
> -----------------------------------------------------------------
>
> Key: OAK-8628
> URL: https://issues.apache.org/jira/browse/OAK-8628
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: store-spi
> Reporter: Julian Reschke
> Priority: Major
>
> For instance with "/test" from
> {noformat}
> 10:30:12.983 ERROR [main] NodeStateUtils.java:50 /test
> java.lang.Exception: call stack
> at
> org.apache.jackrabbit.oak.spi.state.NodeStateUtils.isHidden(NodeStateUtils.java:50)
> at
> org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor.fetchNext(Cursors.java:348)
> at
> org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor.hasNext(Cursors.java:327)
> at
> org.apache.jackrabbit.oak.query.ast.SelectorImpl.nextInternal(SelectorImpl.java:515)
> at
> org.apache.jackrabbit.oak.query.ast.SelectorImpl.next(SelectorImpl.java:508)
> {noformat}
> We should either change doc and impl to handle paths, or enforce the contract
> and chagne other code to use {{isHiddenPath()}} instead.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
