It works! :)
@Jonathan: Indeed, I'm using Solr1.4.1 example schema.
I have now added:
in schema.xml
changed relevant fields in schema.xml from "integer" to "int"
Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Range-query-not-working-tp1570324p1572605.html
Sent
On Thu, Sep 23, 2010 at 5:44 PM, Jonathan Rochkind wrote:
> The field type in a standard schema.xml that's defined as "integer" is NOT
> sortable.
Right - before 1.4. There is no "integer" field type in 1.4 and
beyond in the example schema.
> You can not sort on this and get what you want. (Wha
Are you using Solr 1.4.1? Are you using the example default schema
from Solr 1.4.1? "int", which I recommended, is not the same as
"integer", which you report. In Solr 1.4.1.
Different field types have a somewhat confusing history in Solr. With
Solr 1.4, there are new types based on the T
This is the field in my schema.xml:
Also in the response it clearly shows:
0
What else can I do?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Range-query-not-working-tp1570324p1570580.html
Sent from the Solr - User mailing list archive at Nabble.com.
You need to use a field type that will sort integers properly. You are,
I'm pretty sure, using a field type that ends up doing string byte order
comparison. And as a string, "2" is not in between "0" and "100". (In
fact, pretty much only strings begininng with "0" like say "0234" are.).
In
Forgot to mention..I tried that too already.
So when I have:
location_rating_total:[0 TO 100]
It shows only the location for which the location_rating_total is EXACTLY
0...locations that have location_rating_total value of 2 are NOT included.
Any other suggestions?
--
View this message in cont
On Thu, Sep 23, 2010 at 4:30 PM, PeterKerk wrote:
> I have this in my query:
> &q=*:*&facet.query=location_rating_total:[3 TO 100]
>
> And this document:
>
> -
>
> 1.0
> 1
> 2
>
>
> But still my total results equals 6 (total population) and not 0 as I would
> expect
>
> Why?
facet.query will
