Re: Possible bug in Solr SpellCheckComponent if more than one QueryConverter class is present

2013-01-14 Thread Jack Krupansky
I just tried, and it causes an NPE, kind of as I had expected. I’ll file the Jira. -- Jack Krupansky From: Dyer, James Sent: Monday, January 14, 2013 10:50 AM To: dev@lucene.apache.org Subject: RE: Possible bug in Solr SpellCheckComponent if more than one QueryConverter class is present

RE: Possible bug in Solr SpellCheckComponent if more than one QueryConverter class is present

2013-01-14 Thread Dyer, James
James Dyer E-Commerce Systems Ingram Content Group (615) 213-4311 From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Sunday, January 13, 2013 1:24 PM To: Lucene/Solr Dev Subject: Possible bug in Solr SpellCheckComponent if more than one QueryConverter class is present Reading through the

Possible bug in Solr SpellCheckComponent if more than one QueryConverter class is present

2013-01-13 Thread Jack Krupansky
Reading through the code for Solr SpellCheckComponent.java for 4.1, it looks like it neither complains nor defaults reasonably if more than on QueryConverter class is present in the Solr lib directories: Map queryConverters = new HashMap(); core.initPlugins(queryConverters,QueryConverter.class);