Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of yseeley@gmail.com designates
 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=OMQzHzDQWrglqSw8d/HzV4Jq4YmuedvvsEMZhQFyaUifASjF7rDRqSsX7cvOuFBOEpE8uAivkhRnRNDht8fBQnXny81Gs+v7MsA3s2Lh/WsylZQnZQoSa+WGYv6i3NxXb5K/NYBB5KVjp2vfU8U3VSVxhSPIxlR5l7xMVWgfDXI=
Message-ID: <c68e39170704061020y2361e04me153594fb747155a@mail.gmail.com>
Date: Fri, 6 Apr 2007 13:20:10 -0400
From: "Yonik Seeley" <yonik@apache.org>
Sender: yseeley@gmail.com
To: java-user@lucene.apache.org
Subject: Re: indexing and searching real numbers
In-Reply-To: <9859816.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <9859816.post@talk.nabble.com>

On 4/5/07, Leon <lmikhailov@netzero.net> wrote:
> I need to index and search real numbers in Lucene. I found NumberUtils cl=
ass
> in Solr project which permits one to encode doubles into string so that
> alpha numeric ordering would correctly correspond to the ordering on
> numbers. When I use ConstantScoreRangeQuery programmatically everything
> works just fine. However when I convert this query to a string, parse it
> with QueryParser and use the resulting query =96 no result are found.
>
> ConstantScoreRangeQuery wquery =3D
>   new ConstantScoreRangeQuery("westbc", null,
> NumberUtils.double2sortableStr(-110.500000), false, true);
> Hits hits =3D is.search(wquery); //returns expected results
>
> Now if I do
>
> String wqueryString =3D wquery.toString();
> QueryParser queryParser =3D new QueryParser("westbc", new KeywordAnalyzer=
());
> Query query =3D queryParser.parse(wqueryString);
> Hits hits =3D is.search(query); // returns nothing

Query.toString() is really for debugging only, and I don't believe
current implementations try to escape characters that might be interpreted
as something else if reparsed.

Simple example...  I think
(new TermQuery(new Term("foo","\"a\""))).toString() would yield
foo:"a"
which if put through the query parser, would be parsed as
foo:a

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org