: Ah, I fixed it. I wasn't properly including the : org.apache.lucene.codecs.Codec file in my jar. I wasn't sure if it was : necessary in Solr, since I specify my factory in solrconfig.xml. I : think that's why I could create a new index, but not load an existing : one.
Ah.... interesting. yes, you definitely need the SPI registration in the jar file so that it can resolve codec files found on disk when opening them -- the configuration in solrconfig.xml tells solr hch codec to use when writing new segments, but it must respect the codec information in segements found on disk when opening them (that's how the index backcompat works), and those are looked up via SPI. Can you do me a favor please and still file an issue with these details. the attachments i asked about before would still be handy, but probably not neccessary -- at a minimum could you show us the "jar tf" output of your plugin jar when you were having the problem. Even if the codec factory code can find the configured codec on startup, we should probably throw a very load error write away if that same codec can't be found by name using SPI to prevent people from running into confusing problems when making mistakes like this. -Hoss
