On Mar 7, 2007, at 11:34 AM, Chris Hostetter wrote:
: back in just now. Here's an example trying to warm using a sort on
: field name "subject". I tried query of
: "allMessageContent:trying;subject+asc" as well as
: "allMessageContent:trying;subject" (without "+asc") - either way
when expressin
On Mar 6, 2007, at 9:50 PM, Yonik Seeley wrote:
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
From what I can see in the logs, these are both invoked after the
commit. However, the query times after a commit are still slow
(around 20 seconds).
Your warming script didn't d
On Mar 6, 2007, at 1:55 PM, Yonik Seeley wrote:
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
I'm looking for some tips / suggestions around reducing the query
time for Solr after I've post'ed a commit request. My Lucene index
contains around 2,000,000 documents,
hello,
I'm looking for some tips / suggestions around reducing the query
time for Solr after I've post'ed a commit request. My Lucene index
contains around 2,000,000 documents, and I have a job that
periodically removes artibrary documents from Lucene and replaces
them with fresh copies f
I'm glad I asked. I probably wouldn't have discovered that on my
own... :)
This worked great:
curl http://localhost:8983/solr/update --data-binary ''
thanks,
Kaan
On Nov 29, 2006, at 12:31 AM, Mike Klaas wrote:
On 11/28/06, Kaan Erdener <[EMAIL PROTECTED]
hello,
I'm pulling data into Lucene several times an hour, approaching a
total document count of ~2 million. Sometimes I pull in brand new
data, other times I replace an existing document with an updated
copy. The number of documents that I update in Lucene will pretty
much never be more
