I'm just getting a hibernate search set up, and during the indexing phase at runtime the software throws an error:

java.lang.NoSuchFieldError: ANALYZED
at org.hibernate.search.engine.DocumentBuilderContainedEntity.getIndex(DocumentBuilderContainedEntity.java:538)

Does anyone know what this is all about? I found some postings saying that it might have to do with apache-solr-*.jar being in my lib folder, but I don't have those .jars in there. Any ideas? Thanks.

Sol

See the below:



You need to check your classpath and see if you have an old version of lucene in there. If you're using maven then you can do a dependency:analyze (something similar).

Hope that helps.

I checked my classpath, and the only thing I could find that shouldn't have been there was the lucene-core-2.9.jar. No apache-solr-*.jar or anything.

Now the only lucene-related libraries in my classpath are

lucene-core-2.4-dev.jar
lucene-analyzers-2.4-dev.jar
lucene-highlighter-2.4-dev.jar
lucene-memory-2.4-dev.jar
lucene-queries-2.4-dev.jar
lucene-snowball-2.4-dev.jar
lucene-spellchecker-2.4-dev.jar

Luckily getting rid of the 2.9 core got rid of the error I was having, but I now see a (almost identical) new error:

java.lang.NoSuchFieldError: NOT_ANALYZED at org.hibernate.search.engine.DocumentBuilderIndexedEntity.getDocument(DocumentBuilderIndexedEntity.java:361)

Any thoughts? Thanks much for your help.

Sol

Are you using maven? I could send you my pom file that I am using. Looking at what's in your classpath you shouldn't get the exception. Also I can send you a sample web app (maven) if you want to check the differences. My mail is aminmc@gmail.com.

I'm not using maven, unfortunately. What's doubly weird is the fact that getting rid of the lucene-2.9-core.jar fixed the original error but still gave me this new one...Any other ideas are appreciated.

Thanks,

Sol

Strange. The only thing I can think of is looking at your app and check. It does seem like an old version of lucene which being loaded first. Is it possible to have at look at what you're trying to do?

Hello sol,
each version o Hibernate Search is tightly coupled (compiled with) a specific version of Lucene, you can replace the Lucene version as long as the public api didn't change.

The error you're seeing is most likely due to the fact that in earlier versions of Lucene the Field.Index.NOT_ANALYZED and Field.Index.ANALYZED had a very unfortunate typo. This was fixed in recent versions, but breaks compatibility, so this is now for me an indication that you're not loading the correct version of Lucene;
It appears that other projects have the bad habit to "copy-paste" Lucene inside another jar keeping the same package names, so I'd recommend you to use some classpath scanning tool like JBoss Tattletale. It's a command line tool wich produces some reports and is able to tell if you're having duplicate classes in different JARs.

An alternative is you check all your other jars (looking inside too) to not contain another copy of Lucene.


Which version is that? shouldn't it be healthier to use lucene-core-2.4.1.jar ?

Switching to 2.4.1 from 2.4.dev fixed the problem. Thanks all.

Sol