jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <mreut...@adobe.com>
Subject Re: OAK and large list of orderable child nodes
Date Tue, 19 Aug 2014 06:39:35 GMT

I think it depends on the use case. e.g. how frequently do you
modify the list? how many 'producers' (sessions adding nodes) and
'consumers' (sessions removing nodes) do you have? is it OK if the
query result is slightly out of date? etc.

an async ordered index is probably a good choice if you have multiple
'producers' and 'consumers' and your application is OK with results
that are not always up to date.


On 31/07/14 16:56, "Laurie Byrum" <lbyrum@adobe.com> wrote:

>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" <mueller@adobe.com> wrote:
>>This might be a 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
>>also because neither Jackrabbit 2.x nor Jackrabbit Oak can deal with this
>>On 31/07/14 09:12, "Bertrand De Coatpont" <lebescon@adobe.com> wrote:
>>>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
>>>(e.g. Nodes 490-500 out of 20000), and is OAK helping/changing anything
>>>this area compared to previous versions?
>>>Bertrand de Coatpont
>>>Group Product Manager, Adobe Experience Management
>>>512.284.4195 (tel), /bertranddecoatpont

View raw message