Hello list,
as Hoss suggests, I'll try to be more detailed.
I wish to use http parameters in my requests that define the precise semantic
of an advanced search.
For example, if I can see from sessions, that a given user is requesting, that
not only public resources but resources private-to-him
.
From: Paul Libbrecht [p...@hoplahup.net]
Sent: Saturday, February 19, 2011 11:01 AM
To: solr-user@lucene.apache.org
Subject: Re: Best way for a query-expander?
Hello list,
as Hoss suggests, I'll try to be more detailed.
I wish to use http parameters in my requests
Hi Paul,
what do you understand by saying extra parameters?
Regards
Paul Libbrecht-4 wrote:
Hello Solr-friends,
I want to implement a query-expander, one that enriches the input by the
usage of extra parameters that, for example, a form may provide.
Is the right way to subclass
Erm... extra web-request-parameters simply.
paul
Le 18 févr. 2011 à 19:37, Em a écrit :
Hi Paul,
what do you understand by saying extra parameters?
Regards
Paul Libbrecht-4 wrote:
Hello Solr-friends,
I want to implement a query-expander, one that enriches the input by the
Hi Paul,
me and a colleague worked on a QParserPlugin to expand alias field names
to many existing field names
ex: q=mockfield:val == q=actualfield1:val OR actualfield2:val
but if you want to be able to use other params that come from the HTTP
request you should use a custom RequestHandler I
using rb.req.getParams().get(blip) inside prepare(ResponseBuilder)'s subclass
of QueryComponent I could easily get the extra http request param.
However, how would I change the query?
using rb.setQuery(xxx) within that same prepare method seems to have no effect.
paul
Le 18 févr. 2011 à
it does work!
Le 18 févr. 2011 à 20:48, Paul Libbrecht a écrit :
using rb.req.getParams().get(blip) inside prepare(ResponseBuilder)'s
subclass of QueryComponent I could easily get the extra http request param.
However, how would I change the query?
using rb.setQuery(xxx) within that same
: I want to implement a query-expander, one that enriches the input by the
: usage of extra parameters that, for example, a form may provide.
:
: Is the right way to subclass SearchHandler?
: Or rather to subclass QueryComponent?
This smells like the poster child for an X/Y problem
(or maybe
