[
https://issues.apache.org/jira/browse/OAK-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653526#comment-15653526
]
Vikas Saurabh commented on OAK-5091:
------------------------------------
Actually, thinking further, the plan currently with bundling was for whole
sub-trees (that is bundled structures would have un-bundled children) e.g.
nt:file->nt:resource (and nothing further). So, reducing priority.
> Support bundled documents in oak-mongo.js
> -----------------------------------------
>
> Key: OAK-5091
> URL: https://issues.apache.org/jira/browse/OAK-5091
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 1.5.13
> Reporter: Vikas Saurabh
> Assignee: Chetan Mehrotra
> Fix For: 1.6
>
>
> With document bundling (OAK-1312) repository can have holes in document
> hierarchy (this
> [comment|https://issues.apache.org/jira/browse/OAK-1312?focusedCommentId=15434914&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15434914])
> {quote}
> Just a quick note: with the implementation, we can have potential holes in
> documents - say we have {{/a, /a/b and /a/b/c}} and {{/a/b}} is bundled with
> {{/a}}. Then we'd only have documents - {{0:/, 1:/a, 3:/a/b/c}}.
> While that, of course, is ok, but we would need to factor this at least in
> oak-mongo.js (I can't recall any place else right now) which loops
> recursively at quite a few places with breaking the loop if no docs are found
> at a given depth.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
