[
https://issues.apache.org/jira/browse/HIVE-18861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391555#comment-16391555
]
Steve Loughran commented on HIVE-18861:
---------------------------------------
I don't see these tests being related' there's nothing druid or aws related
directly in the stacks. e.g. TestSequenceFileHCatStorer.testWriteChar
{code}
Caused by: org.apache.pig.backend.executionengine.ExecException: ERROR 6017:
JobID: job_local1096640948_0048 Reason: ExitCodeException exitCode=1: chmod:
cannot access
‘/tmp/hadoop/mapred/staging/hiveptest1096640948/.staging/job_local1096640948_0048/job.split’:
No such file or directory
{code}
However, without experience running the Hive tests, I could be utterly wrong.
What to do now?
> druid-hdfs-storage is pulling in hadoop-aws-2.7.x and aws SDK, creating
> classpath problems on hadoop 3.x
> --------------------------------------------------------------------------------------------------------
>
> Key: HIVE-18861
> URL: https://issues.apache.org/jira/browse/HIVE-18861
> Project: Hive
> Issue Type: Sub-task
> Components: Druid integration
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Attachments: HIVE-18861-001.patch, HIVE-18861-001.patch,
> HIVE-18861.patch, HIVE-18861.patch
>
>
> druid-hdfs-storage JAR is transitively pulling in hadoop-aws JAR 2.7.3, which
> creates classpath problems as a set of aws-sdk 1.10.77 JARs get on the CP,
> even with Hadoop 3 & its move to a full aws-sdk-bundle JAR.
> Two options
> # exclude the dependency
> # force it up to whatever ${hadoop.version} is, so make it consistent
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
