[
https://issues.apache.org/jira/browse/OAK-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955089#comment-13955089
]
Chetan Mehrotra commented on OAK-1557:
--------------------------------------
After discussion with [~mreutegg] defering the issue to 1.0. For now with
Version GC (OAK-1341) implemented in normal usage case such deleted documents
would be garbage collected and hence should not pose much problem. So urgency
of this feature is reduce and can be addressed in later 1.0 release
> Mark documents as deleted
> -------------------------
>
> Key: OAK-1557
> URL: https://issues.apache.org/jira/browse/OAK-1557
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Marcel Reutegger
> Assignee: Chetan Mehrotra
> Priority: Blocker
> Fix For: 1.0
>
>
> This is an improvement to make a certain use case more efficient. When there
> is a parent node with frequently added and removed child nodes, the reading
> of the current list of child nodes becomes inefficient because the decision
> whether a node exists at a certain revision is done in the DocumentNodeStore
> and no filtering is done on the MongoDB side.
> So far we figured this would be solved automatically by the MVCC garbage
> collection, when documents for deleted nodes are removed. However for
> locations in the repository where nodes are added and deleted again
> frequently (think of a temp folder), the issue pops up before the GC had a
> chance to clean up.
> The Document should have an additional field, which is set when the node is
> deleted in the most recent revision. Based on this field the
> DocumentNodeStore can limit the query to MongoDB to documents that are not
> deleted.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
