There are many ways to do this, Prasi. You have a lot of thinking to do on the
subject.
You could decide to publish your content to database, and then index that
database in Solr.
You could publish XML or CSV files of your content for Solr to read and index.
You could use nutch or some other t
Hi, Igor,
I also set forceElevation to true for my elevate results.
Cheers,
Chris
- Original Message -
From: Igor Salma
To: solr-user@lucene.apache.org
Cc:
Sent: Thursday, July 5, 2012 4:47 AM
Subject: Problems with elevation component configuration
Hi to all,
we are using solr in
Thanks to those who responded. A more thorough reading of the wiki and I see
the need for forceElevation=true in the elevate query.
Cheers,
Chris
- Original Message -
From: Otis Gospodnetic
To: "solr-user@lucene.apache.org" ; Chris Warner
Cc:
Sent: Wednesday, April 18,
?
That is not a useful test. Users don't look for *:*.
Test with real queries.
wunder
On Apr 18, 2012, at 10:27 AM, Chris Warner wrote:
> Thanks, Jeevanandam and Otis,
>
> I'll take another look at Elevate. My first attempts did not yield success,
> as I was not able to
eevanandam Madanagopal
To: solr-user@lucene.apache.org; Chris Warner
Cc:
Sent: Wednesday, April 18, 2012 10:21 AM
Subject: Re: Can you suggest a method or pattern to consistently promote a
document with any query?
Chris -
Take a look - QueryElevationComponent
http://wiki.apach
Hi, folks,
Perhaps I'm overlooking an obvious solution to a common desire... I'd like to
return a specific document with every query, as the first result. As well, I'd
like to have that document be the first result in a *:* query.
I'm looking into index time boosting using the boost attribute o
