jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5587) Node counter index estimates must not be used before first async index cycle
Date Tue, 07 Feb 2017 11:36:41 GMT

    [ https://issues.apache.org/jira/browse/OAK-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855806#comment-15855806
] 

Thomas Mueller commented on OAK-5587:
-------------------------------------

Still working on this, as the change breaks some tests (for good, because the tests assume
the counter index is up-to-date, without verifying it): oak-jcr QueryPlanTest.nodeType and
QueryTest.approxCount.

> 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)

Mime
View raw message