It's coming from somewhere else then. I think you'd want to examine the rest of the classpaths. You do not need to put Lucene jars in the classpath yourself. It will just cause issues. You will need to make sure you're looking at the remote cluster's classpath, if it's remote.
On Fri, Apr 6, 2012 at 3:42 PM, Tristan Slominski <[email protected]> wrote: > Thanks Sean, > > I tried to wrap my mind around where an incompatible version of Lucene > could be coming from. I'm assuming that this happens during the Hadoop job > execution based on the output below:
