SPI with name Lucene50 does not exist
See original GitHub issueWon’t run :
An SPI class of type org.apache.lucene.codecs.PostingsFormat with name 'Lucene50' does not exist. You need to add the corresponding JAR file supporting this SPI to your classpath. The current classpath supports the following names [es090, completion090, XBloomFilter]
config type: misc.direction: em
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Maven packaging fail Lucene, SPI does not exist Exception
IllegalArgumentException : An SPI class of type org.apache.lucene.codecs.PostingsFormat with name 'Lucene50' does not exist.
Read more >[LDEV-762] Lucene 5.2.1 initialization failed - Lucee
Message: An SPI class of type org.apache.lucene.codecs.Codec with name 'Lucene50' does not exist. You need to add the corresponding JAR file supporting this ......
Read more >Plugin issue with SPI and classpath - Elastic Discuss
PostingsFormat with name 'Siren10AFor' does not exist. You need to add the corresponding JAR file supporting this SPI to your classpath.
Read more >An SPI class of type org.apache.lucene.codecs ... - 博客园
PostingsFormat with name 'Lucene50' does not exist. You need to add the corresponding JAR file supporting this SPI to your classpath.
Read more >"java.lang.IllegalArgumentException\: Could not load codec ...
IllegalArgumentException: An SPI class of type > org.apache.lucene.codecs.Codec with name 'Lucene60' does not exist. You > need to add the corresponding JAR ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ozlerhakan You may need to add
<transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
The Lucene codecs are in META-INF/services, and if you look at the Maven Shade docs:
This allows it to combine the codecs from conflicting JARs instead of clobbering them.
Note: I did not run into this issue with Mongolastic, but I did on another project using ES. Possibly a difference in ES 2.3.1 and 2.3.3 JARs?
Hi @jmmk ,
Thank you for informing me about it. I can probably add this option for the next release but I don’t remember whether I encountered such an error before ES 2.3.1, there are possibly slightly differences between two versions.