[
https://issues.apache.org/jira/browse/OAK-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756554#comment-13756554
]
Thomas Mueller commented on OAK-983:
------------------------------------
I forgot, index aggregates can't be supported by the PropertyIndex and
NodeTypeIndex. Is this the reason to disable those indexes?
What about changing the query engine instead (as opposed to the indexes), so
for such queries the query engine doesn't even _ask_ indexes that don't support
aggregation? That is, if aggregation is used and a full-text index is
available? I would prefer that over the PropertyIndex/NodeTypeIndex checking
for full-text constraints.
> Non full-text indices should ignore queries that have full-text constraints
> ---------------------------------------------------------------------------
>
> Key: OAK-983
> URL: https://issues.apache.org/jira/browse/OAK-983
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, query
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Minor
> Fix For: 0.9
>
>
> The PropertyIndex and the NodeTypeIndex don't take into account existing
> full-text constraints on a query and can return a smaller cost, making the
> query engine incorrectly choose the wrong index for a full-text query.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
