[
https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043578#comment-16043578
]
Hadoop QA commented on PHOENIX-3817:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12872140/PHOENIX-3817.v2.patch
against master branch at commit 9b402043896fdeb78a236542bddf88e4a7f300e7.
ATTACHMENT ID: 12872140
{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 javadoc{color}. The javadoc tool appears to have generated
49 warning messages.
{color:red}-1 release audit{color}. The applied patch generated 6 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:
+ PreparedStatement sourceStmt =
conn.prepareStatement(String.format(UPSERT_USER, sourceTableName));
+ PreparedStatement targetStmt =
conn.prepareStatement(String.format(UPSERT_USER, targetTableName));
+ private void upsertData(PreparedStatement stmt, String tenantId, String
userId, int age) throws SQLException {
+ Path outputDir = new
Path(job.getConfiguration().get("mapreduce.output.fileoutputformat.outputdir"));
+ public RecordReader<ImmutableBytesWritable, MultiTableResults>
createRecordReader(InputSplit inputSplit,
+ GOODROWS, BADROWS, ONLY_IN_SOURCE_TABLE_ROWS,
ONLY_IN_TARGET_TABLE_ROWS, CONTENT_DIFFERENT_ROWS
+ throw new IllegalArgumentException("Unexpected extra parameters: "
+ cmdLine.getArgList());
+ final String currentScnValue =
configuration.get(PhoenixConfigurationUtil.CURRENT_SCN_VALUE);
+ // since we can't set a scn on connections with txn set TX_SCN
attribute so that the max time range is set by BaseScannerRegionObserver
+ scan.setAttribute(BaseScannerRegionObserver.TX_SCN,
Bytes.toBytes(Long.valueOf(txnScnValue)));
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.mapreduce.VerifyReplicationToolIT
{color:red}-1 core zombie tests{color}. There are 4 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1048//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1048//artifact/patchprocess/patchReleaseAuditWarnings.txt
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1048//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1048//console
This message is automatically generated.
> VerifyReplication using SQL
> ---------------------------
>
> Key: PHOENIX-3817
> URL: https://issues.apache.org/jira/browse/PHOENIX-3817
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Alex Araujo
> Assignee: Alex Araujo
> Priority: Minor
> Attachments: PHOENIX-3817.v1.patch, PHOENIX-3817.v2.patch
>
>
> Certain use cases may copy or replicate a subset of a table to a different
> table or cluster. For example, application topologies may map data for
> specific tenants to different peer clusters.
> It would be useful to have a Phoenix VerifyReplication tool that accepts an
> SQL query, a target table, and an optional target cluster. The tool would
> compare data returned by the query on the different tables and update various
> result counters (similar to HBase's VerifyReplication).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
