[
https://issues.apache.org/jira/browse/HCATALOG-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451351#comment-13451351
]
Travis Crawford commented on HCATALOG-495:
------------------------------------------
{quote}
Have we removed any jars lately that we would expect to cause this?
{quote}
I used to get asked this same question a LOT for another project with many
dependencies, and the solution I came up with works really well. As part of the
build stage that resolves dependencies, the actual resolved jars are compared
with a checked-in file containing expected jars. If you want to change deps you
also change the list of expected jars. Its sort of like a unit test for
dependencies. Now we can just look at the SCM history and see what changed
when. If this sounds like something we'd like to do I can set it up for HCat
too.
Regarding this issue, does running in verbose mode show the classpath being
used? That might give us a clue to figure out what's going on here.
> HCat MR jobs failing in trunk
> -----------------------------
>
> Key: HCATALOG-495
> URL: https://issues.apache.org/jira/browse/HCATALOG-495
> Project: HCatalog
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.5
> Reporter: Alan Gates
> Priority: Critical
>
> All MR jobs run by the e2e tests fail with:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/google/common/cache/RemovalListener
> at org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:533)
> at
> org.apache.hcatalog.mapreduce.InitializeInput.getInputJobInfo(InitializeInput.java:96)
> at
> org.apache.hcatalog.mapreduce.InitializeInput.setInput(InitializeInput.java:77)
> at
> org.apache.hcatalog.mapreduce.HCatInputFormat.setInput(HCatInputFormat.java:40)
> at org.apache.hcatalog.utils.SimpleRead.run(SimpleRead.java:89)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79)
> at org.apache.hcatalog.utils.SimpleRead.main(SimpleRead.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
> {code}
> Have we removed any jars lately that we would expect to cause this?
--
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
