unsubscribe
On Mon, May 11, 2015 at 6:58 PM, Upayavira wrote:
> attaching them to each request, then just add qf= as a param to the URL,
> easy.
>
> On Mon, May 11, 2015, at 12:17 PM, nutchsolruser wrote:
> > These boosting parameters will be configured outside Solr and there is
> > seperate mod
attaching them to each request, then just add qf= as a param to the URL,
easy.
On Mon, May 11, 2015, at 12:17 PM, nutchsolruser wrote:
> These boosting parameters will be configured outside Solr and there is
> seperate module from which these values get populated , I am reading
> those
> values fr
These boosting parameters will be configured outside Solr and there is
seperate module from which these values get populated , I am reading those
values from external datasource and I want to attach them to each request .
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-
On Mon, May 11, 2015, at 10:30 AM, nutchsolruser wrote:
> I can not set qf in solrconfig.xml file because my qf and boost values
> will
> be changing frequently . I am reading those values from external source.
>
> Can we not set qf value from searchComponent? Or is there any other way
> to
> d
I can not set qf in solrconfig.xml file because my qf and boost values will
be changing frequently . I am reading those values from external source.
Can we not set qf value from searchComponent? Or is there any other way to
do this?
--
View this message in context:
http://lucene.472066.n3.nab
If all you want to do is to hardwire a qf, you can do that in your
requestHandler config in solrconfig.xml.
If you want to extend how the edismax query parser works, you may well
be better off subclassing the edismax query parser, and passing in
modified request parameters, but I'd explore getting
Thanks Upayavira,
I tried it by changing it to first-component in solrconfig.xml but no luck .
Am I missing something here ? Here I want to add my own qf fields with boost
in query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-custom-component-issue-tp4204799p420
You are adding a "search component", and adding it as a
"last-component", meaning, it will come after the Query component which
actually does the work.
Given the parameters you have set, you will be using the default Lucene
query parser which doesn't honour the qf parameter, so it isn't
surprising
