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

Hadoop QA commented on PHOENIX-4872:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12945840/PHOENIX-4872-4.x-HBase-1.4.patch
  against 4.x-HBase-1.4 branch at commit 
9f224a18b59fdcc323d661af3b307411c84c4a4c.
  ATTACHMENT ID: 12945840

    {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:
    +        stmt.execute("CREATE IMMUTABLE TABLE S.TABLE10 (ID INTEGER NOT 
NULL PRIMARY KEY, NAME VARCHAR, T DATE, CF1.T2 DATE, CF2.T3 DATE) 
IMMUTABLE_STORAGE_SCHEME=SINGLE_CELL_ARRAY_WITH_OFFSETS");
+            byte[] cfn = Bytes.add(emptyColumnFamily, 
QueryConstants.NAMESPACE_SEPARATOR_BYTES, emptyKeyValue);

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.monitoring.PhoenixMetricsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.MigrateSystemTablesToSystemNamespaceIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.SystemCatalogCreationOnConnectionIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.SplitIT

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

This message is automatically generated.

> BulkLoad has bug when loading on single-cell-array-with-offsets table.
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-4872
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4872
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0, 4.12.0, 4.13.0, 4.14.0
>            Reporter: JeongMin Ju
>            Assignee: Swaroopa Kadam
>            Priority: Critical
>         Attachments: PHOENIX-4872-4.x-HBase-1.4.patch, 
> PHOENIX-4872-master.patch
>
>
> CsvBulkLoadTool creates incorrect data for the 
> SCAWO(SingleCellArrayWithOffsets) table.
> Every phoenix table needs a marker (empty) column, but CsvBulkLoadTool does 
> not create that column for SCAWO tables.
> If you check the data through HBase Shell, you can see that there is no 
> corresponding column.
>  If created by Upsert Query, it is created normally.
> {code:java}
> column=0:\x00\x00\x00\x00, timestamp=1535420036372, value=x
> {code}
> Since there is no upper column, the result of all Group By queries is zero.
> This is because "families":
> {"0": ["\\ x00 \\ x00 \\ x00 \\ x00"]}
> is added to the column of the Scan object.
> Because the CsvBulkLoadTool has not created the column, the result of the 
> scan is empty.
>  
> This problem applies only to tables with multiple column families. The 
> single-column family table works luckily.
> "Families": \{"0": ["ALL"]} is added to the column of the Scan object in the 
> single column family table. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to