Would it be appropriate in this situation to adopt Oak indices and use queries instead of "listChildren"?
On 7/31/14 4:56 AM, "Thomas Mueller" <muel...@adobe.com> wrote: >Hi, > >This might be a XY problem: >http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem > >What problem do you want to solve? > >I don't think it's a good idea to have a list of 20000 orderable children, >also because neither Jackrabbit 2.x nor Jackrabbit Oak can deal with this >efficiently. > >Regards, >Thomas > > > >On 31/07/14 09:12, "Bertrand De Coatpont" <lebes...@adobe.com> wrote: > >>Hello, >> >>In the JCR world, is there a specific API to obtain (for reading) a >>specific range of child nodes within a large list of orderable child >>nodes >>(e.g. Nodes 490-500 out of 20000), and is OAK helping/changing anything >>in >>this area compared to previous versions? >> >>Thanks! >> >>Bertrand >> >>Bertrand de Coatpont >>Group Product Manager, Adobe Experience Management >>Adobe >>512.284.4195 (tel), /bertranddecoatpont >>lebes...@adobe.com >>www.adobe.com >> >> >>> >> >
