Re: Query time de-boost

2016-02-28 Thread shamik
")^99* or *ContenGroup-local:Developer^-99* But, both cannot be used in conjunction with other bq parameters. *bq=Source:simplecontent^10 Source:Help^20 ContenGroup-local:Developer^-99* doesn't work, which I thought would be. -- View this message in context: http://lucene.47

Re: Query time de-boost

2016-02-28 Thread Jack Krupansky
multiplicative, >>>> not >>>> additive, so term^0.1 reduces the term by 90%. >>>> >>>> -- Jack Krupansky >>>> >>>> On Wed, Feb 24, 2016 at 11:29 AM, shamik wrote: >>>> >>>> Binoy, 0.1 is still a positiv

Re: Query time de-boost

2016-02-28 Thread Emir Arnautovic
Binoy, 0.1 is still a positive boost. With title getting the highest weight, this won't make any difference. I've tried this as well. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259552.html Sent from the Solr - User mai

Re: Query time de-boost

2016-02-26 Thread shamik
his is not going to work. I'm working on the functional query side to see if this can be done. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4260077.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Query time de-boost

2016-02-26 Thread Jack Krupansky
t; On Wed, Feb 24, 2016 at 11:29 AM, shamik wrote: >> >> Binoy, 0.1 is still a positive boost. With title getting the highest >>> weight, >>> this won't make any difference. I've tried this as well. >>> >>> >>> >>> -- &g

Re: Query time de-boost

2016-02-26 Thread Emir Arnautovic
, shamik wrote: Binoy, 0.1 is still a positive boost. With title getting the highest weight, this won't make any difference. I've tried this as well. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259552.html Sent from the Solr - User ma

Re: Query time de-boost

2016-02-25 Thread Jack Krupansky
x27;t make any difference. I've tried this as well. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259552.html > Sent from the Solr - User mailing list archive at Nabble.com. >

Re: Query time de-boost

2016-02-25 Thread Walter Underwood
loper's Documentation")^99 >> >> Are you sure something like *bq=ContenGroup-local:Developer^-99* worked for >> you? >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259879.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > -- > Regards, > Binoy Dalal

Re: Query time de-boost

2016-02-25 Thread Binoy Dalal
ContetGroup:"Developer's Documentation")^99 > > Are you sure something like *bq=ContenGroup-local:Developer^-99* worked for > you? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259879.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Binoy Dalal

Re: Query time de-boost

2016-02-25 Thread shamik
Source:Help^20 (*:* -ContetGroup:"Developer's Documentation")^99 Are you sure something like *bq=ContenGroup-local:Developer^-99* worked for you? -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259879.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Query time de-boost

2016-02-25 Thread Emir Arnautovic
-- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259551.html Sent from the Solr - User mailing list archive at Nabble.com. -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/

Re: Query time de-boost

2016-02-24 Thread shamik
Binoy, 0.1 is still a positive boost. With title getting the highest weight, this won't make any difference. I've tried this as well. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259552.html Sent from the Solr - User mailing list

Re: Query time de-boost

2016-02-24 Thread shamik
up-local:("Developer"))^99* will implicitly boost the rest, but that didn't happen. I'm using edismax. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-time-de-boost-tp4259309p4259551.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Query time de-boost

2016-02-24 Thread Binoy Dalal
If you were to apply a boost of less than 1, so something like 0.1, that would reduce the score of the docs you want to de-boost. On Wed, 24 Feb 2016, 15:17 Emir Arnautovic wrote: > Hi Shamik, > Is boosting others acceptable option to you, e.g. > ContentGroup:"NonDeveloper"^100. > Which query pa

Re: Query time de-boost

2016-02-24 Thread Emir Arnautovic
Hi Shamik, Is boosting others acceptable option to you, e.g. ContentGroup:"NonDeveloper"^100. Which query parser do you use? Regards, Emir -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On 23.02.2016 23:42, Shami

Query time de-boost

2016-02-23 Thread Shamik Bandopadhyay
Hi, I'm looking into the possibility of de-boosting a set of documents during query time. In my application, when I search for e.g. "preferences", I want to de-boost content tagged with ContentGroup:"Developer" or in other words, push those content back in the order. Here's the catch. I've the f