Mailing-List: contact user-help@lucenenet.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@lucenenet.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Sender: omri@diffdoof.com
From: Omri Suissa <omri.suissa@diffdoof.com>
Date: Sun, 17 Feb 2013 18:03:49 +0200
Message-ID: 
 <CAAd_LB+OrmeTEFwmXpQMFJf59rLndZwHsW3pU8MwRN9X-z_V_A@mail.gmail.com>
Subject: Extending QueryParser to properly handle numeric fields
To: user@lucenenet.apache.org
Content-Type: multipart/alternative; boundary=14dae9340a2d38c41a04d5edc2d3

--14dae9340a2d38c41a04d5edc2d3
Content-Type: text/plain; charset=ISO-8859-1

Hi,
I want to extend QueryParser to properly handle numeric fields.
I found a lot of info about it on the java mailing list.
One of the resolutions to this problem looks very good:
override GetRangeQuery and create NumericRangeQuery.

But, here is my problem, in all examples the code is looks like this:

int num1 = Integer.parseInt(part1);
int num2 = Integer.parseInt(part2);
Query q = NumericRangeQuery.newIntRange(field, num1, num2, inclusive,
inclusive);

where part1 and part2 are the 2 parts of the range.

when i search for "price:[1 TO 10]" i get in part1: "price:[1" and in
part2: "price:[1 TO 10]".

why is that?
there is a difference between the Java version and the .net version of the
QueryParser?
or this is a bug in the .net version?

Thanks,
Omri

--14dae9340a2d38c41a04d5edc2d3--