[
https://issues.apache.org/jira/browse/OAK-7795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638205#comment-16638205
]
Davide Giannella commented on OAK-7795:
---------------------------------------
you're right. Probably we should be doing this only after the index selection.
maybe storing close to cost indexes and costs in a Map and then later on if the
elected index is one in the map we output the message. I expect the memory
impact to be trivial.
> 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
>
>
> 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)
