You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Venkat Sambath (JIRA)" <ji...@apache.org> on 2016/07/05 09:03:11 UTC

[jira] [Commented] (HIVE-13825) Using JOIN in 2 tables that has same path locations, but different colum names fail wtih an error exception

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

Venkat Sambath commented on HIVE-13825:
---------------------------------------

For some use cases this workaround wouldn't work. 
For example.
If the usecase involves mapping multiple tables on the same file.

CREATE TABLE t1 ( a string, b string) location '/user/hive/warehouse/test1'; 
CREATE TABLE t2 ( d string, e string) location '/user/hive/warehouse/test1';

t1 and t2 maps to different columns on the same table. In this case, creating view t3 on t2 and joining t3 with t1 will result in the same error as provided in the case description. 

> Using JOIN in 2 tables that has same path locations, but different colum names fail wtih an error exception
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13825
>                 URL: https://issues.apache.org/jira/browse/HIVE-13825
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergio Peña
>            Assignee: Vihang Karajgaonkar
>
> The following scenario of 2 tables with same locations cannot be used on a JOIN query:
> {noformat}
> hive> create table t1 (a string, b string) location '/user/hive/warehouse/test1';
> OK
> hive> create table t2 (c string, d string) location '/user/hive/warehouse/test1';
> OK
> hive> select t1.a from t1 join t2 on t1.a = t2.c;
> ...
> 2016-05-23 16:39:57     Starting to launch local task to process map join;      maximum memory = 477102080
> Execution failed with exit status: 2
> Obtaining error information
> Task failed!
> Task ID:
>   Stage-4
> Logs:
> FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask
> {noformat}
> The logs contain this error exception:
> {noformat}
> 2016-05-23T16:39:58,163 ERROR [main]: mr.MapredLocalTask (:()) - Hive Runtime Error: Map local work failed
> java.lang.RuntimeException: cannot find field a from [0:c, 1:d]
>         at org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorUtils.getStandardStructFieldRef(ObjectInspectorUtils.java:485)
>         at org.apache.hadoop.hive.serde2.BaseStructObjectInspector.getStructFieldRef(BaseStructObjectInspector.java:133)
>         at org.apache.hadoop.hive.ql.exec.ExprNodeColumnEvaluator.initialize(ExprNodeColumnEvaluator.java:55)
>         at org.apache.hadoop.hive.ql.exec.Operator.initEvaluators(Operator.java:973)
>         at org.apache.hadoop.hive.ql.exec.Operator.initEvaluatorsAndReturnStruct(Operator.java:999)
>         at org.apache.hadoop.hive.ql.exec.SelectOperator.initializeOp(SelectOperator.java:75)
>         at org.apache.hadoop.hive.ql.exec.Operator.initialize(Operator.java:355)
>         at org.apache.hadoop.hive.ql.exec.Operator.initialize(Operator.java:504)
>         at org.apache.hadoop.hive.ql.exec.Operator.initializeChildren(Operator.java:457)
>         at org.apache.hadoop.hive.ql.exec.Operator.initialize(Operator.java:365)
>         at org.apache.hadoop.hive.ql.exec.Operator.initialize(Operator.java:504)
>         at org.apache.hadoop.hive.ql.exec.Operator.initializeChildren(Operator.java:457)
>         at org.apache.hadoop.hive.ql.exec.Operator.initialize(Operator.java:365)
>         at org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.initializeOperators(MapredLocalTask.java:499)
>         at org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.startForward(MapredLocalTask.java:403)
>         at org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask.executeInProcess(MapredLocalTask.java:383)
>         at org.apache.hadoop.hive.ql.exec.mr.ExecDriver.main(ExecDriver.java:751)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)