: 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 expressing params in XML (either as init params for a request
handler,
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
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, and I have a job that
periodically removes artibrary documents from Lucene
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, and I have a job that
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 do any sorts.
Why don't you also show the part of the log with the
str name=qallMessageContent:test;subject+asc/str
there should be a space between subject and asc,
try: http://host/select?q=allMessageContent:test;subject%20asc
+ is supposed to become a space, but it looks like it is staying +
