Thanks for the advice. I've moved this query rewriting logic (not really
business logic) to a SearchComponent and will leave the custom query parser
to deal with the keyword (q=) related aspects of the query. In my case, the
latter is mostly dealing with the presence of wildcard characters.
Peter
: It's for an optimization. If the keyword is 'match all docs', I want to
: remove a custom PostFilter from the query and change the sort parameters
: (so the app doesn't have to do it). It looks like the responseHeader is
: displaying the 'originalParams', which are immutable.
that is in fact t
I meant to say: If the keyword is *:* (MachAllDocsQuery)...
On Wed, Oct 22, 2014 at 2:17 PM, Peter Keegan
wrote:
> It's for an optimization. If the keyword is 'match all docs', I want to
> remove a custom PostFilter from the query and change the sort parameters
> (so the app doesn't have to do i
It's for an optimization. If the keyword is 'match all docs', I want to
remove a custom PostFilter from the query and change the sort parameters
(so the app doesn't have to do it). It looks like the responseHeader is
displaying the 'originalParams', which are immutable.
On Wed, Oct 22, 2014 at 2:
I don't know why you need to change it ? you can use &omitHeader=true on the
URL to remove header if you want.
--
View this message in context:
http://lucene.472066.n3.nabble.com/QParserPlugin-question-tp4165368p4165373.html
Sent from the Solr - User mailing list archive at Nabble.com.
