[ 
https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022504#comment-16022504
 ] 

Hadoop QA commented on PHOENIX-3734:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12869587/PHOENIX-3734.v4.patch
  against master branch at commit a2f4d7eebec621b58204a9eb78d552f18dcbcf24.
  ATTACHMENT ID: 12869587

    {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 
47 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:
    +               
optionBuilder.append(",IMMUTABLE_STORAGE_SCHEME="+PTableImpl.ImmutableStorageScheme.ONE_CELL_PER_COLUMN);
+                { false, false, false }, { false, false, true }, { false, 
true, false }, { false, true, true },
+                { true, false, false }, { true, false, true }, { true, true, 
false }, { true, true, true }
+        conn.createStatement().execute("CREATE TABLE " + fullTableName + "(pk 
INTEGER PRIMARY KEY, val INTEGER)"+tableDDLOptions);
+            stmt.execute("CREATE TABLE " + fullTableName + "(k VARCHAR PRIMARY 
KEY, v1 VARCHAR, v2 VARCHAR)"+tableDDLOptions);
+                       stmt.execute("CREATE TABLE " + fullTableName + "(ID 
BIGINT NOT NULL PRIMARY KEY, v1 VARCHAR, v2 VARCHAR)"
+                       stmt.execute("CREATE TABLE " + fullTableName + "1(ID1 
BIGINT NOT NULL PRIMARY KEY, FK1A INTEGER, FK1B INTEGER)"
+            assertEquals(PhoenixVisibilityLevel.SNAPSHOT_EXCLUDE_CURRENT, 
state.getVisibilityLevel());
+                dataRegion, indexMaintainer, viewConstants, null, null, 
projector, ptr, useQualiferAsListIndex);
+                            
delete.setAttribute(PhoenixTransactionContext.TX_ROLLBACK_ATTRIBUTE_KEY, new 
byte[0]);

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/897//testReport/
Javadoc warnings: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/897//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/897//console

This message is automatically generated.

> Refactor Phoenix to use TAL instead of direct calls to Tephra
> -------------------------------------------------------------
>
>                 Key: PHOENIX-3734
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3734
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
>         Attachments: PHOENIX-3734.v4.patch
>
>
> Refactor Phoenix to use the new transaction abstraction layer instead of 
> direct calls to Tephra. Once this task will be committed, Phoenix will 
> continue working with Tephra but will have the option for fast integration of 
> new transaction processing engines.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to