Indeed! Perhaps the germane part is this, before the failure to instantiate notice:
Caused by: java.lang.ClassCastException: class org.apache.solr.update.DirectUpda teHandler2 at java.lang.Class.asSubclass(Unknown Source) at org.apache.solr.core.SolrResourceLoader.findClass(SolrResourceLoader. java:432) at org.apache.solr.core.SolrCore.createInstance(SolrCore.java:507) This suggests that I might be doing something wrong elsewhere in solrconfig.xml. The possibly relevant parts (my contributions) are these: <updateRequestProcessorChain name="partial" default="true"> <processor class="solr.RunUpdateProcessorFactory"/> <processor class="solr.LogUpdateProcessorFactory"/> </updateRequestProcessorChain> <updateRequestProcessorChain name="harvest" default="true"> <processor class="solr.RunUpdateProcessorFactory"/> <processor class="org.apache.solr.update.TopicQuestsDocumentProcessFactory"> <str name="inputField">hello</str> </processor> <processor class="solr.LogUpdateProcessorFactory"/> </updateRequestProcessorChain> <requestHandler name="/update/harvest" class="solr.DirectUpdateHandler2"> <lst name="defaults"> <str name="update.chain">harvest</str> </lst> </requestHandler> <requestHandler name="/update/partial" class="solr.DirectUpdateHandler2"> <lst name="defaults"> <str name="update.chain">partial</str> </lst> </requestHandler> Thanks Jack On Tue, Mar 12, 2013 at 12:16 PM, Mark Miller <markrmil...@gmail.com> wrote: > There should be a stack trace - also, you shouldn't have to do anything > special to use this class. It's the default and only truly supported > implementation… > > - Mark > > On Mar 12, 2013, at 2:53 PM, Jack Park <jackp...@topicquests.org> wrote: > >> That messages gives great, but terrible google. Zillions of hits, >> mostly filled with very long log traces, and zero messages (that I >> could find) about what to do about it. >> >> I switched over to using that handler since it has an update log >> specified, and that's the only place I've found how to use update log. >> But, can't boot now. >> >> All the jars are in place; I'm able to import that class in my code. >> >> Is there any news on that issue? >> >> Many thanks >> Jack >