[
https://issues.apache.org/jira/browse/PHOENIX-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131461#comment-16131461
]
Hadoop QA commented on PHOENIX-4095:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882459/PHOENIX-4095_v2.patch
against master branch at commit ce6b891fd658f6593845d1155509d0f8a599336f.
ATTACHMENT ID: 12882459
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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 javadoc{color}. The javadoc tool appears to have generated
56 warning messages.
{color:red}-1 release audit{color}. The applied patch generated 2 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:
+
serverProps.put(QueryServices.INDEX_FAILURE_HANDLING_REBUILD_OVERLAP_FORWARD_TIME_ATTRIB,
Long.toString(2000));
+ private static boolean mutateRandomly(Connection conn, String
fullTableName, int nRows) throws Exception {
+ private static boolean hasInactiveIndex(PMetaData metaCache, PTableKey
key) throws TableNotFoundException {
+ private static boolean isAllActiveIndex(PMetaData metaCache, PTableKey
key) throws TableNotFoundException {
+ private static boolean mutateRandomly(Connection conn, String
fullTableName, int nRows, boolean checkForInactive) throws SQLException,
InterruptedException {
+ conn.createStatement().execute("UPSERT INTO " + fullTableName + "
VALUES(" + pk + "," + v1 + "," + v2 + ")");
+ conn.createStatement().execute("UPSERT INTO " + fullTableName + "
VALUES(" + pk + "," + v1 + "," + v2 + ")");
+ conn.createStatement().execute("CREATE TABLE " + fullTableName +
"(k INTEGER PRIMARY KEY, v1 INTEGER, v2 INTEGER) COLUMN_ENCODED_BYTES = 0,
STORE_NULLS=true");
+ conn.createStatement().execute("CREATE INDEX " + indexName + " ON
" + fullTableName + " (v1) INCLUDE (v2)");
+ HTableInterface metaTable =
conn.unwrap(PhoenixConnection.class).getQueryServices().getTable(PhoenixDatabaseMetaData.SYSTEM_CATALOG_NAME_BYTES);
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.phoenix.util.TestUtilIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1274//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1274//artifact/patchprocess/patchReleaseAuditWarnings.txt
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1274//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1274//console
This message is automatically generated.
> Prevent index from getting out of sync with data table during partial rebuild
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-4095
> URL: https://issues.apache.org/jira/browse/PHOENIX-4095
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4095_v1.patch, PHOENIX-4095_v2.patch
>
>
> When there are many versions of a row, the partial index rebuilder is not
> correctly updating the index.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
