[
https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647501#comment-16647501
]
Lars Hofhansl edited comment on PHOENIX-4964 at 10/12/18 5:39 AM:
------------------------------------------------------------------
Updated -v4 to also test reverse scans. Going to commit.
(Note I found a general bug with reverse scans along local indexes - not
related to this one, will file a separate issue on this)
was (Author: lhofhansl):
Updated -v4 to also test reverse scans.
(Note I found a general bug with reverse scans along local indexes - not
related to this one, will file a separate issue on this)
> 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)
