phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4288) Indexes not used when ordering by primary key
Date Tue, 28 Nov 2017 06:29:00 GMT


ASF GitHub Bot commented on PHOENIX-4288:

Github user maryannxue commented on a diff in the pull request:
    --- Diff: phoenix-core/src/it/java/org/apache/phoenix/end2end/
    @@ -0,0 +1,176 @@
    +package org.apache.phoenix.end2end;
    +import static org.apache.phoenix.util.TestUtil.TEST_PROPERTIES;
    +import static org.junit.Assert.assertTrue;
    +import java.sql.Connection;
    +import java.sql.DriverManager;
    +import java.sql.PreparedStatement;
    +import java.sql.ResultSet;
    +import java.util.Map;
    +import java.util.Properties;
    +import org.apache.phoenix.query.BaseTest;
    +import org.apache.phoenix.query.QueryServices;
    +import org.apache.phoenix.util.PropertiesUtil;
    +import org.apache.phoenix.util.QueryUtil;
    +import org.apache.phoenix.util.ReadOnlyProps;
    +import org.junit.AfterClass;
    +import org.junit.BeforeClass;
    +import org.junit.Test;
    +public class CostBasedDecisionIT extends BaseTest {
    --- End diff --
    Thanks for pointing this out, @JamesRTaylor! Changed in my latest CI as suggested.

> Indexes not used when ordering by primary key
> ---------------------------------------------
>                 Key: PHOENIX-4288
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Marcin Januszkiewicz
>            Assignee: Maryann Xue
>              Labels: CostBasedOptimization
> 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
> 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
> In our actual use case, adding index hints is not a practical solution.
> See also discussion at:

This message was sent by Atlassian JIRA

View raw message