[
https://issues.apache.org/jira/browse/OAK-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667051#comment-15667051
]
Vikas Saurabh commented on OAK-5091:
------------------------------------
Yes, that's the direction I was thinking... Not sure of the exact
implementation issue that we might hit (which, of course, should be solvable).
It's just that, it seemed to me that our document structures are getting too
complicated now to justify a parallel JS based impl.
> 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
> Priority: Minor
> Fix For: 1.8
>
>
> 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)
