Thanks Erick !
As I re-checked the configuration files, it turns out someone had
modified the /solr/conf/*stopwords.txt* on the production server,
and now we know what problem we're dealing with, which seems to be
related to:
-
http://lucene.472066.n3.nabble.com/Dismax-Minimum-Match-Stopwords
What happens if you copy the index from one machine to the other? Probably from
prod to test. If your results stay the same, that'd eliminate index
differences as
the culprit.
What do you get by attaching &debugQuery=on the the queries that differ?
Is the parsed query any different? I'm wondering
Thanks for the hint :)
We ruled that out after having tested special characters, and if it was
an applicative bug, it wouldn't work consistently like it currently does
for the majority of queries.
The only difference we noticed was in the HTTP headers in the SOLR
response: occasionnally, the "C
Could it be something in the transmission of the query?
Or is it also identical?
paul
Le 11 mai 2011 à 17:19, Paul Michalet a écrit :
> Hello everyone
>
> We have succesfully installed SOLR on 2 servers (developpement and
> production), using the same configuration files and paths.
> Both SOL
Hello everyone
We have succesfully installed SOLR on 2 servers (developpement and
production), using the same configuration files and paths.
Both SOLR instances have indexed the same contents and most queries give
identical results, but there's a few exceptions where the production
instance re
