You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2018/10/09 11:06:00 UTC
[jira] [Comment Edited] (OAK-7795) Log a debug message when two or
more indices have same or very close cost amounts
[ https://issues.apache.org/jira/browse/OAK-7795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643120#comment-16643120 ]
Tommaso Teofili edited comment on OAK-7795 at 10/9/18 11:05 AM:
----------------------------------------------------------------
attached patch, which records "almost" best cost / index and log a debug message when they that and the selected index cost differ by or less than 0.1.
/cc [~edivad] [~tmueller]
was (Author: teofili):
attached patch, which records "almost" best cost / index and log a debug message when they that and the selected index cost differ by or less than 0.1.
> Log a debug message when two or more indices have same or very close cost amounts
> ---------------------------------------------------------------------------------
>
> Key: OAK-7795
> URL: https://issues.apache.org/jira/browse/OAK-7795
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: query
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7795.0.patch, OAK-7795.1.patch
>
>
> The index selection mechanism in {{QueryImpl}} may lead to the wrong index to be picked up in case different indexes return same (or very close) costs.
> As a remedy we can set cost overrides, change queries or index definitions.
> However to speed up identification of such problematics situations it'd be good to have a line in the (debug) logs reporting when for a particular query a number of indexes have same or very close costs (in the order of 10^-1). This would give a first pointer to such possible problematic situations to be inspected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)