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.
Scott > -----Original Message----- > From: Chris Hostetter [mailto:hossman_luc...@fucit.org] > Sent: Wednesday, September 25, 2013 9:49 AM > To: solr-user@lucene.apache.org > Subject: RE: Problem loading my codec sometimes > > > : I still wonder why it can create a new index using my codec, but not > : load an index previously created with my codec. In solrconfig.xml, I > : specify the CodecFactory along with the package name, whereas the > codec > : name that is read from the index file has no package name. Could > that > : be the problem? I think that's the way it's supposed to be. Could > it > : be that Solr has my jar in the classpath, but SPI is not registering > my > : codec class from the jar? I'm not familiar with SPI. > > it's very possible that there is a classloader / SPI runtime race > condition in looking up the codec names found in segment files. This > sort > of classpath related runtime issue is extremely hard to write tests > for. > > Could you please file a bug and include... > > * the source of your codec (or a simple sample codec that you can > also use to reproduce the problem) > * a ziped up copy of your entire solr home directory, including > the jar file containing your codec so we can verify the SPI files > are in their properly > - no need to include an actual index here > * some simple sample docments in xml or json taht we can index > with the schema you are using > > > > -Hoss
