[
https://issues.apache.org/jira/browse/PHOENIX-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050948#comment-17050948
]
Hadoop QA commented on PHOENIX-5718:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12995520/PHOENIX-5718.master.v2.patch
against master branch at commit 3013c3e954ebdbec7274cb950e3583bc08975135.
ATTACHMENT ID: 12995520
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{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:
+ props.setProperty(PhoenixRuntime.CURRENT_SCN_ATTRIB,
Long.toString(table.getTimeStamp()));
+ // Force update the cache and check if V3 is present in
the returned table result
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.AlterMultiTenantTableWithViewsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.DropMetadataIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3535//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3535//console
This message is automatically generated.
> GetTable builds a table excluding the given clientTimeStamp
> -----------------------------------------------------------
>
> Key: PHOENIX-5718
> URL: https://issues.apache.org/jira/browse/PHOENIX-5718
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.16.0
> Reporter: Sandeep Guggilam
> Assignee: Sandeep Guggilam
> Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-5718.4.x-HBase-1.3.v1.patch,
> PHOENIX-5718.4.x-HBase-1.3.v2.patch, PHOENIX-5718.master.v1.patch,
> PHOENIX-5718.master.v2.patch
>
>
> Here is the scenario tested:
> # Brought up a server with 4.16 where new columns are added but not added as
> part of upgrade path
> # Connect with 4.14 client
> # Connect with a 4.16 client - this will throw an exception as the new
> columns added as part of 4.16 were not added as part of upgrade path
> # Now the code will force update the cache in
> PhoenixStatement#executeQuery() method
> # Now the buildTable is removing even the columns added as part of 4.15 ,
> the reason being we are passing the clientTimeStamp to build table ( say 29
> is the timestamp for column added for 4.15) but the table is scanning rows
> EXCLUDING the passed clientTimeSTamp as the Scan#setTimeRange method excludes
> the end time stamp
> The passing of clientTimeStamp to build table is in
> MetaDataEndPointImpl#doGetTable method
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
