[
https://issues.apache.org/jira/browse/OAK-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664772#comment-15664772
]
Vikas Saurabh commented on OAK-5091:
------------------------------------
I was thinking about this a bit and parsing bundling information, which afair
is rev-versioned data, seems getting too much to do in javascript. May be, as
an orthogonal approach, we do a parallel oak-run-console-command which uses
oak's classes as far as possible and goes down to impl specific class to do
some stuff optimally (break usual DocumentNodeStore abstraction and talk to
mongo or rdb directly - of course through helper classes). If that sounds
reasonable, we can then deprecate oak-mongo.js.
As an added (minor??) advantage we get RDB maintenance at par with that of
mongo.
[~mreutegg], [~chetanm], [~reschke], thoughts??
> 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)
