I would probably try the SearchComponent route first, translating input into DisMax speak. But if you have a completely different query language, a QParserPlugin could be the way to go.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 24. feb. 2011, at 06.26, Michael Moores wrote: > Trying to answer my own question.. seems like it would be a good idea to > create a SearchComponent and add this to the list of existing components. > My component just converts query parameters to something that the solr > QueryComponent understands. > One good way of doing it? > > > > On Feb 23, 2011, at 8:12 PM, Michael Moores wrote: > >> I'm required to provide a handler with some specialized query string inputs. >> >> I'd like to translate the query inputs to a lucene/solr query and delegate >> the request to the existing lucene/dismax handler. >> >> What's the best way to do this? >> Do I implement SolrRequestHandler, or a QParser? Do I extend the existing >> StandardRequestHandler? >> >> thanks, >> --Michael >> >> >> >> >> >> >
