[
https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798548#comment-16798548
]
Hadoop QA commented on PHOENIX-5156:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12963313/PHOENIX-5156.master.002.patch
against master branch at commit c06bb592ca489e41b7df11cab248135ad534416d.
ATTACHMENT ID: 12963313
{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: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:
+ assertEquals("Expected data table row count to match
expected:<2> but was:<1>", e.getMessage());
+ new HashJoinRegionScanner(innerScanner, scan, p, j,
ScanUtil.getTenantId(scan),
+ theScanner = new HashJoinRegionScanner(theScanner, scan, p, j,
ScanUtil.getTenantId(scan), env, useQualifierAsIndex,
useNewValueColumnQualifier);
+ List<Pair<Mutation, byte[]>> indexUpdatesForDeletes = new
ArrayList<>(indexUpdates.size());
+ "preBatchMutateWithExceptions: indexMetaData is not an
instance of PhoenixIndexMetaData " +
+
c.getEnvironment().getRegion().getRegionInfo().getTable().getNameAsString());
+ List<IndexMaintainer> maintainers =
((PhoenixIndexMetaData)indexMetaData).getIndexMaintainers();
+ IndexMaintainer indexMaintainer =
getIndexMaintainer(maintainers, next.getSecond());
+
c.getEnvironment().getRegion().getRegionInfo().getTable().getNameAsString());
+ // For a delete mutation, first unverify the exiting
row in the index table and then delete
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureWithNamespaceIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.TableDDLPermissionsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexSplitReverseScanIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.PartialIndexRebuilderIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.rpc.PhoenixServerRpcIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ConcurrentMutationsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.join.SortMergeJoinNoSpoolingIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.hbase.index.FailForUnsupportedHBaseVersionsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ChangePermissionsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexSplitForwardScanIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2451//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2451//console
This message is automatically generated.
> Consistent Global Indexes for Non-Transactional Tables
> ------------------------------------------------------
>
> Key: PHOENIX-5156
> URL: https://issues.apache.org/jira/browse/PHOENIX-5156
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5156.master.001.patch,
> PHOENIX-5156.master.002.patch, PHOENIX-5156.master.003.patch
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> Without transactional tables, the global indexes can get easily out of sync
> with their data tables in Phoenix. Transactional tables require a separate
> transaction manager, have some restrictions and performance penalties. This
> issue is to have consistent global indexes without the need for using
> transactional tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
