[
https://issues.apache.org/jira/browse/OAK-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042896#comment-18042896
]
Julian Reschke commented on OAK-11731:
--------------------------------------
trunk:
[56b282dd7c|https://github.com/apache/jackrabbit-oak/commit/56b282dd7c6bfc8c5dddd88fc1510a4ab07a61b1]
[edfda40603|https://github.com/apache/jackrabbit-oak/commit/edfda40603233e0fc24408cb0d3fdbb6d8ca9380]
> expose NodeCounter (getEstimatedChildNodeCounts) in JackrabbitNode
> ------------------------------------------------------------------
>
> Key: OAK-11731
> URL: https://issues.apache.org/jira/browse/OAK-11731
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: api, core, jcr
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Fix For: 1.90.0
>
>
> For components attempting to move/copy/delete hierarchies, it would be useful
> for get an estimated child node count either in order to estimate the cost of
> the operation, or by using it to report once the operation is done.
> EDIT: open questions:
> - -how useful is that if we only count for one level? A move or delete will
> actually affect the whole tree-
> - -how do we test on the oak-jcr level? do we need to?-
> - -for now, there's a new (internal) package export from oak-core. can we do
> better?-
> (1) indeed counts in the hierarchy, (2) not pretty, but tested, (3) yes, by
> moving the interface into oak-commons, and just "inherit" in oak-core,
> registering the counter twice.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
