A bit of Solr Kung Fu on this topic:
Let us suppose that your data source cannot be changed to use leading
zeroes. Also suppose that the field is required in every record.
The copyField directive automatically populates other fields with your input
data. If you do this:
fieldQuestion type=
Because the lucene term ordering is lexicographic,
if you index strings "11", "100", and "150",
the terms in the index "100","11","150" in this order.
Koji
Jim Adams wrote:
Why is this?
Thanks.
On Sat, Jan 31, 2009 at 3:50 AM, Koji Sekiguchi wrote:
Jim Adams wrote:
True, which
Why is this?
Thanks.
On Sat, Jan 31, 2009 at 3:50 AM, Koji Sekiguchi wrote:
> Jim Adams wrote:
>
>> True, which is what I'll probably do, but is there any way to do this
>> using
>> 'string'? Actually I have even seen this with date fields, which seems
>> very
>> odd (more data being returned
Jim Adams wrote:
True, which is what I'll probably do, but is there any way to do this using
'string'? Actually I have even seen this with date fields, which seems very
odd (more data being returned than I expected).
If you want to stick with string, index "011" instead of "11".
Koji
True, which is what I'll probably do, but is there any way to do this using
'string'? Actually I have even seen this with date fields, which seems very
odd (more data being returned than I expected).
On Fri, Jan 30, 2009 at 7:04 PM, Koji Sekiguchi wrote:
> Jim Adams wrote:
>
>> I have a string
Jim Adams wrote:
I have a string field in my schema that actually numeric data. If I try a
range search:
fieldInQuestion:[ 100 TO 150 ]
I fetch back a lot of data that is NOT in this range, such as 11, etc.
Any idea why this happens? Is it because this is a string?
Thanks.
Yep, try si
I have a string field in my schema that actually numeric data. If I try a
range search:
fieldInQuestion:[ 100 TO 150 ]
I fetch back a lot of data that is NOT in this range, such as 11, etc.
Any idea why this happens? Is it because this is a string?
Thanks.
