I haven't experienced any such problems; it's just a query-parser plugin that adds some behavior on top of the normal query parsing. In any case, even if I use a custom request handler with my custom parser, can I get facet-queries to use this custom parser by default as well?
-Stephen On Thu, Sep 10, 2009 at 11:30 PM, Lance Norskog <goks...@gmail.com> wrote: > Changing basic defaults like this makes it very confusing to work with > successive solr releases, to read the wiki, etc. > > You can make custom search requesthandlers - an example: > > <requestHandler name="/custom" class="solr.SearchHandler" > > <lst name="invariants"> > <str name="defType">customparser</str> > > http://localhost:8983/solr/custom?q=string_in_my_custom_language > > On 9/10/09, Stephen Duncan Jr <stephen.dun...@gmail.com> wrote: > > If using {!type=customparser} is the only way now, should I file an issue > to > > make the default configurable? > > > > -- > > Stephen Duncan Jr > > www.stephenduncanjr.com > > > > On Thu, Sep 3, 2009 at 11:23 AM, Stephen Duncan Jr < > stephen.dun...@gmail.com > > > wrote: > > > > > We have a custom query parser plugin registered as the default for > > > searches, and we'd like to have the same parser used for facet.query. > > > > > > Is there a way to register it as the default for FacetComponent in > > > solrconfig.xml? > > > > > > I know I can add {!type=customparser} to each query as a workaround, > but > > > I'd rather register it in the config that make my code send that and > strip > > > it off on every facet query. > > > > > > -- > > > Stephen Duncan Jr > > > www.stephenduncanjr.com > > > > > > > > > -- > Lance Norskog > goks...@gmail.com >
