phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered
Date Fri, 12 Oct 2018 05:50:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Hofhansl resolved PHOENIX-4964.
------------------------------------
    Resolution: Fixed

Committed to master and 4.x*(1.4, 1.3, 1.2)

> ORDER BY should use a LOCAL index even if the query is not fully covered
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-4964
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4964
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Minor
>         Attachments: PHOENIX-4964-4.x-HBase-1.4.txt, PHOENIX-4964-4.x-HBase-1.4.v2.txt,
PHOENIX-4964-4.x-HBase-1.4.v3.txt, PHOENIX-4964-4.x-HBase-1.4.v4.txt
>
>
> I just noticed that a query like
> {{SELECT <column1> FROM <table> ORDER BY <column2> LIMIT <n>}}
> Does not use an index on <column2> if it does not also include <column1>.
That seems too limited.
> I can see the code in QueryOptimizer.addPlan that rewrites the plan only when there's
a WHERE clause, and then only for the WHERE clause. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message