[
https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272131#comment-16272131
]
Hadoop QA commented on PHOENIX-4288:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12899924/PHOENIX-4288.patch
against master branch at commit 355ee522c1d4ff07cf9fbb0a9a01e43e3f702730.
ATTACHMENT ID: 12899924
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 release audit{color}. The applied patch generated 3 release
audit warnings (more than the master's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ conn.createStatement().execute("CREATE LOCAL INDEX " +
tableName + "_idx ON " + tableName + " (c1)");
+ String query = "SELECT rowkey, c1, c2 FROM " + tableName + " where
c1 LIKE 'X0%' ORDER BY rowkey";
+ PreparedStatement stmt = conn.prepareStatement("UPSERT INTO " +
tableName + " (rowkey, c1, c2) VALUES (?, ?, ?)");
+ conn.createStatement().execute("CREATE LOCAL INDEX " + tableName +
"_idx ON " + tableName + " (c1)");
+ String query = "SELECT rowkey, max(c1), max(c2) FROM " + tableName
+ " where c1 LIKE 'X%' GROUP BY rowkey";
+ PreparedStatement stmt = conn.prepareStatement("UPSERT INTO " +
tableName + " (rowkey, c1, c2) VALUES (?, ?, ?)");
+ conn.createStatement().execute("CREATE LOCAL INDEX " + tableName +
"_idx1 ON " + tableName + " (c1) INCLUDE (c2, c3)");
+ conn.createStatement().execute("CREATE LOCAL INDEX " + tableName +
"_idx2 ON " + tableName + " (c2, c3) INCLUDE (c1)");
+ String query = "SELECT * FROM " + tableName + " where c1 BETWEEN
10 AND 20 AND c2 < 9000 AND C3 < 5000";
+ " SERVER FILTER BY ((\"C1\" >= 10 AND \"C1\" <= 20) AND
TO_INTEGER(\"C3\") < 5000)\n" +
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.IndexToolIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1643//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1643//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1643//console
This message is automatically generated.
> 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
> Labels: CostBasedOptimization
> Attachments: PHOENIX-4288.patch
>
>
> We have a table
> CREATE TABLE t (
> rowkey VARCHAR PRIMARY KEY,
> 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
(v6.4.14#64029)
