[
https://issues.apache.org/jira/browse/HIVE-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581110#comment-13581110
]
Amareshwari Sriramadasu commented on HIVE-4018:
-----------------------------------------------
bq. this is a existing bug. Do you really think we should fix this now ? I
mean, it is a pretty big and fundamental change.
I would say this should be fixed. Because earlier we are able to run the same
multi join query using 2 MR jobs with mapjoin hint passed in nested structure
for each join as described in HIVE-3652. Now there is no way to do mapjoin for
this multiway join, as the same query fails with this error, after changes to
HIVE-3784.
It becomes more trouble because there are no more mapjoin hints and will have
to explicitly turn off autojoin for such queries.
> MapJoin failing with Distributed Cache error
> --------------------------------------------
>
> Key: HIVE-4018
> URL: https://issues.apache.org/jira/browse/HIVE-4018
> Project: Hive
> Issue Type: Bug
> Components: SQL
> Affects Versions: 0.11.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Namit Jain
> Fix For: 0.11.0
>
> Attachments: hive.4018.test.2.patch, HIVE-4018-test.patch
>
>
> When I'm a running a star join query after HIVE-3784, it is failing with
> following error:
> 2013-02-13 08:36:04,584 ERROR org.apache.hadoop.hive.ql.exec.MapJoinOperator:
> Load Distributed Cache Error
> 2013-02-13 08:36:04,585 FATAL ExecMapper:
> org.apache.hadoop.hive.ql.metadata.HiveException: java.io.EOFException
> at
> org.apache.hadoop.hive.ql.exec.MapJoinOperator.loadHashTable(MapJoinOperator.java:189)
> at
> org.apache.hadoop.hive.ql.exec.MapJoinOperator.cleanUpInputFileChangedOp(MapJoinOperator.java:203)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1421)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1425)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:614)
> at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:144)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:50)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:391)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:325)
> at org.apache.hadoop.mapred.Child$4.run(Child.java:266)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:416)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1278)
> at org.apache.hadoop.mapred.Child.main(Child.java:260)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
