[
https://issues.apache.org/jira/browse/PHOENIX-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1298:
----------------------------------
Attachment: PHOENIX-1298.patch
That test passed fine with my fix, but there was a test in QueryIT that was
failing. I've adjusted the patch, as those lines I remove are required. I
commented more to explain why.
> Queries on fixed width type columns that have an index declared on them don't
> use that index
> --------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1298
> URL: https://issues.apache.org/jira/browse/PHOENIX-1298
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.2, 3.2
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 5.0.0, 4.2, 3.2
>
> Attachments: PHOENIX-1298.patch, PHOENIX-1298.patch
>
>
> Happens when the index is on a column whose data type is fixed width. If V1
> is made of type VARCHAR, then the test passes.
> {code}
> @Test
> public void testRVCUsingPkColsReturnedByPlanShouldUseIndex() throws
> Exception {
> Connection conn = DriverManager.getConnection(getUrl());
> conn.createStatement().execute("CREATE TABLE T (k VARCHAR NOT NULL
> PRIMARY KEY, v1 CHAR(15), v2 VARCHAR)");
> conn.createStatement().execute("CREATE INDEX IDX ON T(v1)");
> PhoenixStatement stmt =
> conn.createStatement().unwrap(PhoenixStatement.class);
> String query = "select * from t where v1 = '1'";
> QueryPlan plan = stmt.optimizeQuery(query);
> assertEquals("IDX",
> plan.getTableRef().getTable().getTableName().getString());
> }
>
> {code}
> Instead of going through the index table, the query ends up using the data
> table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
