[
https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615393#comment-15615393
]
Thomas Mueller commented on OAK-4887:
-------------------------------------
Thanks a lot!
I believe the Lucene index implementation only returns one plan right now, so
the query engine can't decide which Lucene index to use (damAssetLuceneCreated
or damAssetLucene). It would probably be best if the Lucene index returns one
plan per index, so that the query engine can decide which one to use best. I
don't think internal API changes are needed. After that, there are probably
some smaller changes needed in the query engine, to account for the limit (if
set).
> Query cost estimation: ordering by an unindexed property not reflected
> ----------------------------------------------------------------------
>
> Key: OAK-4887
> URL: https://issues.apache.org/jira/browse/OAK-4887
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Affects Versions: 1.4.2
> Reporter: Alexander Klimetschek
> Assignee: Thomas Mueller
> Fix For: 1.6
>
>
> A query that orders by an unindexed property seems to have no effect on the
> cost estimation, compared to the same query without the order by, although it
> has a big impact on the execution performance for larger results/indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
