How does the exclude="true" option in elevate.xml perform with large number of excludes? Then you could have a separate elevate config for that client.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 3. nov. 2010, at 20.11, Yonik Seeley wrote: > On Wed, Nov 3, 2010 at 3:05 PM, Erick Erickson <erickerick...@gmail.com> > wrote: >> How dynamic is this list? Is it feasable to add a field to your docs like >> blacklisteddocs, and at editorial's discretion add values to that field >> like "app1", "app2"? >> >> At that point you can just filter them out via a filter query... > > Right, or a combination of the two approaches. > For a realtime approach, add the newest filters (say any filters added > that day) to a filter query, and roll those into a nightly reindex. > > -Yonik > http://www.lucidimagination.com > > >> Best >> Erick >> >> On Wed, Nov 3, 2010 at 2:40 PM, Ravi Kiran <ravi.bhas...@gmail.com> wrote: >> >>> Hello, >>> I have a single core servicing 3 different applications, one of the >>> application doesnt want some specific docs to show up (driven by Editorial >>> decision). Over a period of time the amount of blacklisted docs could grow, >>> hence I do not want to restrict them in a query as it the query could get >>> extremely large. Is there a configuration option where we can blacklist ids >>> (uniqueKey) from showing up in results. >>> >>> Is there anything similar to EvelationComponent that demotes docs ? This >>> could be ideal. I tried to look up and see if there was a boosting option >>> in >>> elevation component so that I could negatively boost certain docs but could >>> not find any. >>> >>> Can anybody kindly point me in the right direction. >>> >>> Thanks >>> >>> Ravi Kiran Bhaskar >>> >>
