[
https://issues.apache.org/jira/browse/PHOENIX-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034082#comment-16034082
]
Hadoop QA commented on PHOENIX-3904:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12870911/PHOENIX-3904_v3.patch
against master branch at commit 5fe660537ff28de1738c3e82b65f9a2aac8fc80b.
ATTACHMENT ID: 12870911
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
45 warning messages.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ + " (id integer not null primary key, cf.col1
varchar, cf.col2 varchar, cf2.col3 varchar, cf2.col4 varchar)";
+ private static void setQualifierRanges(boolean keyOnlyFilter, PTable
table, Scan scan, StatementContext context)
+ int hbaseServerVersion =
context.getConnection().getQueryServices().getLowestClusterHBaseVersion();
+ // When only a single column family is referenced, there are
no hints, and HBase server version
+ // is less than when the fix for HBASE-13109 went in
(0.98.12), then we prevent seeking to a
+ preventSeekToColumn = referencedCfCount == 1 &&
hbaseServerVersion < MIN_SEEK_TO_COLUMN_VERSION;
+ trackedColumnsBitset != null ? new
EncodedQualifiersColumnProjectionFilter(SchemaUtil.getEmptyColumnFamily(table),
trackedColumnsBitset, conditionOnlyCfs, table.getEncodingScheme()) : new
ColumnProjectionFilter(SchemaUtil.getEmptyColumnFamily(table),
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.phoenix.compile.QueryOptimizerTest
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/970//testReport/
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/970//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/970//console
This message is automatically generated.
> Queries with LIKE and LIMIT OFFSET fail for mutable tables with column
> mapping enabled
> --------------------------------------------------------------------------------------
>
> Key: PHOENIX-3904
> URL: https://issues.apache.org/jira/browse/PHOENIX-3904
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 4.11.0
>
> Attachments: PHOENIX-3904.patch, PHOENIX-3904_v2.patch,
> PHOENIX-3904_v3.patch
>
>
> Details:
> https://stackoverflow.com/questions/44214659/qualifier-out-of-valid-range-error-in-apache-phoenix-select-with-where-and-of
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
