Maryann Xue commented on PHOENIX-4288:

Thank you, [~rajeshbabu], for reminding me. 5.x branch has now caught up with 
all my recent check-ins.

> Indexes not used when ordering by primary key
> ---------------------------------------------
>                 Key: PHOENIX-4288
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4288
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Marcin Januszkiewicz
>            Assignee: Maryann Xue
>            Priority: Major
>              Labels: CostBasedOptimization
>             Fix For: 4.14.0
>         Attachments: PHOENIX-4288.patch
> We have a table
>   c1 VARCHAR,
>   c2 VARCHAR
> )
> which we want to query by doing partial matches on c1, and keep the ordering 
> of the source table:
> SELECT rowkey, c1, c2 FROM t where c1 LIKE 'X0%' ORDER BY rowkey;
> We expect most queries to select a small subset of the table, so we create an 
> index to speed up searches:
> CREATE LOCAL INDEX t_c1_ix ON t (c1);
> However, this index will not be used since Phoenix will always choose not to 
> resort the data.
> In our actual use case, adding index hints is not a practical solution.
> See also discussion at:
> https://lists.apache.org/thread.html/26ab58288eb811d2f074c3f89067163d341e5531fb581f3b2486cf43@%3Cuser.phoenix.apache.org%3E

This message was sent by Atlassian JIRA

Reply via email to