[jira] [Closed] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

["Chinmay Kulkarni (Jira)" <ji...@apache.org>]

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

Chinmay Kulkarni closed PHOENIX-4964.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> 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
>             Fix For: 4.15.0, 4.14.1, 5.1.0
>
>         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
(v8.3.4#803005)