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

Hadoop QA commented on PHOENIX-5749:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12996880/PHOENIX-5749.4.x-HBase-1.5.v1.patch
  against 4.x-HBase-1.5 branch at commit 
981aa7bbd1ca01cb5607aa74b541403c3dd89135.
  ATTACHMENT ID: 12996880

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 14 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:
    +    private long verifyIndexTable(String tableName, String indexName, 
Connection conn) throws Exception {
+        // Now we rebuild the entire index table and expect that it is still 
good after the full rebuild
+                + "(k1 INTEGER NOT NULL, k2 INTEGER NOT NULL, a.v1 INTEGER, 
b.v2 INTEGER, c.v3 INTEGER, d.v4 INTEGER," +
+        conn.createStatement().execute("CREATE INDEX " + indexName + " ON " + 
tableName + "(v1) INCLUDE(v2, v3)");
+                                            + (RAND.nextBoolean() ? null : 
(RAND.nextInt() % nIndexValues)) + ", "
+    @Ignore ("It is not possible to assign the same timestamp two separately 
committed mutations in the current model\n" +
+            " except when the server time goes backward. In that case, the 
behavior is not deterministic")
+            // Since all the rows are in the index table, running the index 
tool with the "-v BEFORE" option should not
+            populateTable(dataTableName); // with two rows ('a', 'ab', 'abc', 
'abcd') and ('b', 'bc', 'bcd', 'bcde')
+            populateTable(dataTableName); // with two rows ('a', 'ab', 'abc', 
'abcd') and ('b', 'bc', 'bcd', 'bcde')

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

Test results: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3597//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3597//console

This message is automatically generated.

> Add unit tests for verifySingleIndexRow() of IndexRebuildRegionScanner
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-5749
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5749
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Kadir OZDEMIR
>            Assignee: Swaroopa Kadam
>            Priority: Major
>         Attachments: PHOENIX-5749.4.x-HBase-1.5.v1.patch
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> This unit test should test the correctness of verifySingleIndexRow method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to