It's a live server with many search queries. I will set up a test server
next week or the week after and index the same amount of documents. I will
get back with the results.
Uwe
On Sat, Oct 4, 2008 at 8:18 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 4, 2008 at 11:55 AM, Uwe Klosa
Hi everybody
still me :)
Little question : How can I stop solr properly. I explain my problem :
I did a full import and put adaptive parameter for mySql to avoid OOM error.
Then I wanted to add to solrconfig postCommit and postOptimize, snapshooter
once full import was done.
And I stopped tomcat.
Hmmm, tricky. I think you've uncovered an algorithmic flaw in DisMax.
Consider 2 fields, f1, f2 and 2 terms foo and bar. For illustration
purposes, here is a query that's structurally equivalent (assuming
mm=100% of terms must match):
+(f1:foo OR f2:foo) +(f1:bar OR f2:bar)
OK, so it says that
: Hmmm, tricky. I think you've uncovered an algorithmic flaw in DisMax.
I would call it a deficency, not a flaw :)
: more restrictive than the first query. It appears that dismax is a
: bit broken when some of the fields have stopwords and some don't.
: Offhand, I don't see an easy fix for thi
: I have a lucene CustomScoreQuery which I am wanting to execute with a lucene
: Filter. However the getDocListAndSet API provided by the SolrIndexSearcher
: doesn't seem to allow Filters to be used along with Queries. Instead it
: seems that the Filters must be first converted to a DocSet. Int
Hi,
Thanks Erik .I am clear.But when I checked with multiValued=true for a
single field ,I gave
positionIncrementGap=100.That time also mismatch. for ex,
author: John Doe
author: Bob Smith
a phrase query of "doe bob" now matched even i specified
positionIncrementGap=100.again I changed
