thanks that was it
Joel
On Dec 3, 2009, at 11:06 AM, Yonik Seeley wrote:
The schemas probably aren't the same. Looks like one has position
increments enabled for the stopword filter in the field type, and one
doesn't.
-Yonik
http://www.lucidimagination.com
On Thu, Dec 3, 2009 at 11:00 AM,
The schemas probably aren't the same. Looks like one has position
increments enabled for the stopword filter in the field type, and one
doesn't.
-Yonik
http://www.lucidimagination.com
On Thu, Dec 3, 2009 at 11:00 AM, Joel Nylund wrote:
> same client, here are the debug results, something inter
same client, here are the debug results, something interesting is
going on, I dont understand solr/lucene well enough to understand, see
below
not working env (linux)
−
0
2
−
true
countryName:"Bosnia and Herzegovina"
−
countryName:"Bosnia and Herzegovina"
countryName:"Bosnia and Herze
Are you querying both systems from the same browser / client?
Try adding debugQuery=true and see of the query parses the same for
both (could be the browser/client doing extra escaping or something).
-Yonik
http://www.lucidimagination.com
On Thu, Dec 3, 2009 at 10:14 AM, Joel Nylund wrote:
> I
I have 2 environments one works great for this query:
my osx environment:
http://localhost:8983/solr/select?q=countryName:%22Bosnia%20and%20Herzegovina%22
- returns 2 results
my linux environment:
http://localhost:8983/solr/select?q=countryName:%22Bosnia%20and%20Herzegovina%22
- returns
