[jira] [Updated] (JCR-3695) Jcr2spi same name siblings: Path not provided along with unique id in NodeId when calling org.apache.jackrabbit.spi.RepositoryService.getItemInfos(SessionInfo, NodeId). Path needed to maintain SNS index

["Abhinav Atul (JIRA)" <ji...@apache.org>]

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

Abhinav Atul updated JCR-3695:
------------------------------

    Summary: Jcr2spi same name siblings: Path not provided along with unique id in NodeId when calling org.apache.jackrabbit.spi.RepositoryService.getItemInfos(SessionInfo, NodeId). Path needed to maintain SNS index  (was: Jcr2spi same name siblings: Path not provided along with unique id in NodeId when retrieving child node)

> Jcr2spi same name siblings: Path not provided along with unique id in NodeId when calling org.apache.jackrabbit.spi.RepositoryService.getItemInfos(SessionInfo, NodeId). Path needed to maintain SNS index
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-3695
>                 URL: https://issues.apache.org/jira/browse/JCR-3695
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 2.1
>            Reporter: Abhinav Atul
>         Attachments: diff.diff
>
>
>  the path index set up when populating the parent folder with child node info(unique id + path with index for same name sibling) is needed to maintain the indexing order during previous iteration.
> For example, a folder node ‘F’ has been populated with two child entries 
> C(uid:”abcd”,path:/F/C) and C[2](uid:”mnop”,path:/F/C[2])
> When retrieving child nodes of F, NodeId only contains uid(“mnop”) and no path which is needed to setup path for the entry



--
This message was sent by Atlassian JIRA
(v6.1#6144)