[
https://issues.apache.org/jira/browse/PHOENIX-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872200#comment-15872200
]
Hadoop QA commented on PHOENIX-3346:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847427/PHOENIX-3346-1.patch
against master branch at commit c3b16cef5de15df059b5c979a1b54110e5b0ca00.
ATTACHMENT ID: 12847427
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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
43 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:
+ "VALUES (10, \"foodesc\", \"2013-01-05 01:01:01\",
200,2.0,-1);" + HiveTestUtil.CRLF);
+ sb.append("INSERT INTO TABLE phoenix_MultiKey VALUES (10,
\"part2\",\"foodesc\",200,2.0,-1);" +
+ * Test that hive is able to access Phoenix data during MR job (creating
two tables and perform join on it)
+ sb.append("INSERT INTO TABLE joinTable1 VALUES (5,
\"part2\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
+ sb.append("INSERT INTO TABLE joinTable1 VALUES (10,
\"part2\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
+ sb.append("INSERT INTO TABLE joinTable2 VALUES (5,
\"part2\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
+ sb.append("INSERT INTO TABLE joinTable2 VALUES (10,
\"part2\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
+ * Test that hive is able to access Phoenix data during MR job (creating
two tables and perform join on it)
+ sb.append("INSERT INTO TABLE joinTable3 VALUES (5,
\"part1\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
+ sb.append("INSERT INTO TABLE joinTable3 VALUES (10,
\"part1\",\"foodesc\",200,2.0,-1);" + HiveTestUtil.CRLF);
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/773//testReport/
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/773//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/773//console
This message is automatically generated.
> Hive PhoenixStorageHandler doesn't work well with column mapping
> ----------------------------------------------------------------
>
> Key: PHOENIX-3346
> URL: https://issues.apache.org/jira/browse/PHOENIX-3346
> Project: Phoenix
> Issue Type: Bug
> Reporter: Sergey Soldatov
> Assignee: Sergey Soldatov
> Labels: HivePhoenix
> Attachments: PHOENIX-3346-1.patch
>
>
> If column mapping is used during table creation, the hive table becomes
> unusable and throws UnknownColumn exception.
> There are several issues in the current implementation:
> 1. During table creation mapping doesn't applies to primary keys
> 2. During select query building no mapping happen
> 3. PhoenixRow should have backward mapping from phoenix column names to hive
> names.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
