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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.15.0, 4.14.1, 5.1.0
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 10/Oct/18 20:44
• Updated: 21/Dec/19 00:55
• Resolved: 12/Oct/18 05:49

Description

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.

Issue Links

• relates to: PHOENIX-4972 ORDER BY should use a GLOBAL index even if the query is not fully covered