[
https://issues.apache.org/jira/browse/OAK-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855801#comment-15855801
]
Vikas Saurabh commented on OAK-5587:
------------------------------------
[~tmueller], fix lgtm. I've a bit of concern about the length of test though
(as it's creating a lot of nodes to hit counter probabilities). Would it be
possible to increase the chances of updating counter in test instead of putting
in a lot of nodes?
> Node counter index estimates must not be used before first async index cycle
> ----------------------------------------------------------------------------
>
> Key: OAK-5587
> URL: https://issues.apache.org/jira/browse/OAK-5587
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.6.1
>
>
> Oak traversing index returns a very low estimate when first async index cycle
> hasn't completed yet, so that the wrong index can be used on first startup.
> NodeCounter#getCombinedCost() should treat non-existing
> /oak:index/counter/:index same as /oak:index/counter not existing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
