[
https://issues.apache.org/jira/browse/BIGTOP-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633639#comment-13633639
]
Konstantin Boudnik commented on BIGTOP-873:
-------------------------------------------
This patch has a pretty nasty side effect: an attempt to build stack on top of
Hadoop bits that aren't published to the snapshots.apache.org - which is the
case with many releases off Hadoop's branch-2 - you won't be able to build Hive
because it won't resolve freshly installed artifacts in the ~/.m2/repository.
Another problem of this patch is conceptual - {{~/.ivy2/cache}} is shared by
multiple components in the stack, e.g. Pig, and proposed change makes Hive a
non well-behaved player of the Bigtop game - cleaning shared resources, etc.
I'd say this needs to be rolled back.
> Hive needs Ivy cache cleared
> ----------------------------
>
> Key: BIGTOP-873
> URL: https://issues.apache.org/jira/browse/BIGTOP-873
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Fix For: 0.6.0
>
> Attachments: BIGTOP-873.1.patch, BIGTOP-873.patch
>
>
> Some Hive builds started failing after the upgrade to Hive 0.10.0:
> http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Hive/306/
> I have tried unsuccessfully to reproduce the problem on a couple of the
> affected operating systems - I believe the problem is a stale ivy cache. We
> could try invoking the relevant ant target in do-component-build, or perhaps
> we can just do it manually on each of the affected Jenkins slaves.
--
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
