[
https://issues.apache.org/jira/browse/OAK-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-6579:
-------------------------------
Attachment: OAK-6579-3.patch
[~tmueller], thanks for the feedback. In the third version of the patch:
[^OAK-6579-3.patch] there's a new {{oak.index.useCounterOld}} property. Setting
it to true has following effect:
* use the NodeCounterEditorOld in the NodeCounterEditorProvider,
* register the NodeCounterOld in Oak as the NodeCounterMBean,
* redirect to the NodeCounterOld implementation in the
NodeCounter#getEstimatedNodeCount (so the old logic is used if the NodeCounter
class is used directly, eg. in ContentMirrorStoreStrategy or
NodeCounterMBeanEstimator).
> Define how the counter index works in a composite setup
> -------------------------------------------------------
>
> Key: OAK-6579
> URL: https://issues.apache.org/jira/browse/OAK-6579
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: composite, indexing
> Reporter: Robert Munteanu
> Assignee: Tomek Rękawek
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6579-2.patch, OAK-6579-3.patch, OAK-6579.patch
>
>
> We need to see if this index can or should be adjusted to work in a composite
> environment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
