Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <005901caeae4$c38225d0$4a867170$@de>
References: <o2wc68e39171005021032vef44d155l89eeffea5f650b07@mail.gmail.com>
	 <g2x9ac0c6aa1005030236nd4a6325cw34bc74a319e4f2d1@mail.gmail.com>
	 <r2l786fde51005030315k3a452879s4cd7cec58f7b364b@mail.gmail.com>
	 <y2z9ac0c6aa1005030330n90a317d4u33fc4da50a10a0ae@mail.gmail.com>
	 <w2tc68e39171005030737i85875110x3ab2e329e86c77a2@mail.gmail.com>
	 <z2t9ac0c6aa1005030749p2768c43bmd22cbb8eb15982d1@mail.gmail.com>
	 <j2s786fde51005030908r3b2df9c7qd66c6e8157d383bc@mail.gmail.com>
	 <005901caeae4$c38225d0$4a867170$@de>
Date: Mon, 3 May 2010 13:23:33 -0400
Message-ID: <i2s9ac0c6aa1005031023r54cd7688r73085655201c2f6c@mail.gmail.com>
Subject: Re: BytesRef comparable
From: Michael McCandless <lucene@mikemccandless.com>
To: dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I think the tool would require you to specify which [numeric] fields
need conversion?

And maybe also for collated fields?

Mike

On Mon, May 3, 2010 at 1:19 PM, Uwe Schindler <uwe@thetaphi.de> wrote:
> We will provide it for 4.0 for the index order change and possibly to con=
vert NumericFields to full-width byte[] (only problem: how to detect them w=
ithout strange heuristics?)!
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
>> -----Original Message-----
>> From: Shai Erera [mailto:serera@gmail.com]
>> Sent: Monday, May 03, 2010 6:09 PM
>> To: dev@lucene.apache.org
>> Subject: Re: BytesRef comparable
>>
>> Trunk matters here only if this changes within the same manor release.
>> If sort order changes between 4.0 and 5.0, we'll needto provide and
>> index migration tool or something, because such change does not
>> justify reindexing.
>>
>> Shai
>>
>> On Monday, May 3, 2010, Michael McCandless <lucene@mikemccandless.com>
>> wrote:
>> > On Mon, May 3, 2010 at 10:37 AM, Yonik Seeley
>> > <yonik@lucidimagination.com> wrote:
>> >> On Mon, May 3, 2010 at 6:30 AM, Michael McCandless
>> >> <lucene@mikemccandless.com> wrote:
>> >>> But... we probably should do this after we switch to sorting terms
>> by
>> >>> unicode code point order? =A0(LUCENE-2426)
>> >>
>> >> So perhaps we should define this in terms of Lucene's default index
>> >> order instead... so it could be UTF16 order for now, and switch to
>> >> code-point / unsigned byte order when the index format does?
>> >
>> > This seems a bit dangerous (first sorts by UTF16 order and then by
>> > codepoint order, when we switch)... ie, I'd rather make BytesRef
>> > compare by code point order, after we've cutover to that order by
>> > default.
>> >
>> > Though it is "trunk", so, we could do that I guess... (Erik: this is
>> > what "unstable" means ;) ).
>> >
>> > Mike
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

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