[infinispan-issues] [JBoss JIRA] (ISPN-6504) Try to use the index even if the query matches all entries

[Adrian Nistor (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Nistor updated ISPN-6504:
--------------------------------
    Description: 
A DSL query with no filter clauses will match all entries. In this case we currently run a non-indexed query even if the cache is indexed. This is ok for queries that do not use sorting or pprojections. In that case we do not get any benefit from involving the index.

Performance can be improved by using the index if the query has sorting or projections so this should be treated as a special case.

  was:
A DSL query with no filter clauses will match all entries. In this case we currently run a non-indexed query even if the cache is indexed. This is ok for queries that do not use sorting or pprojections. In that case we do not get any benefit from involving the index.

Performance could be improved a bit by using the index if the query has sorting or projections so this should be treated as a special case.



> Try to use the index even if the query matches all entries
> ----------------------------------------------------------
>
>                 Key: ISPN-6504
>                 URL: https://issues.jboss.org/browse/ISPN-6504
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Embedded Querying, Remote Querying
>    Affects Versions: 8.2.1.Final, 9.0.0.Alpha1
>            Reporter: Adrian Nistor
>            Assignee: Adrian Nistor
>             Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
>
> A DSL query with no filter clauses will match all entries. In this case we currently run a non-indexed query even if the cache is indexed. This is ok for queries that do not use sorting or pprojections. In that case we do not get any benefit from involving the index.
> Performance can be improved by using the index if the query has sorting or projections so this should be treated as a special case.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)