You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2015/08/24 14:44:50 UTC

[jira] [Closed] (OAK-3189) CLONE - MissingLastRevSeeker non MongoDS may fail with OOM

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

Davide Giannella closed OAK-3189.
---------------------------------

Bulk close for 1.0.19

> CLONE - MissingLastRevSeeker non MongoDS may fail with OOM
> ----------------------------------------------------------
>
>                 Key: OAK-3189
>                 URL: https://issues.apache.org/jira/browse/OAK-3189
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, rdbmk
>    Affects Versions: 1.0.18
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.0.19
>
>
> (This clones OAK-2208 as that never made it into the 1.0 branch)
> This code currently has a hardwired optimization for MongoDB (returning an Iterable over a DBCursor). For all other persistences, a java List of all matching NodeDocuments will be built.
> I see two ways to address this:
> 1) Generalize the Mongo approach, where a query to the persistence can return a live iterator, or
> 2) Stick with the public DS API, but leverage paging (get N nodes at once, and then keep calling query() again with the right starting ID).
> 2) sounds simpler, but is not transactional; [~mreutegg] would that be sufficient?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)