You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Shon Vella <sv...@technologist.com> on 2009/09/25 16:27:01 UTC
Numeric Field index compatibility
I have some indexes that were created using a dev version of 2.9 from
early June, when the Numeric field stuff was moved to lucene core from
the query contrib package. Now that 2.9 is becoming available, I need to
migrate to using the stuff in core and was wondering about the index
level compatibility between the two. In other words, can I use the stuff
in core against an index that was created using the contrib stuff?
-Shon
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: Numeric Field index compatibility
Posted by Shon Vella <sv...@technologist.com>.
Thanks, Uwe. I suspected as much, but wanted to make sure.
-Shon
Uwe Schindler wrote:
> The term format did not change since the major revision with Yonik at the
> begin of year. Only the API and term generation was changed (NumericField,
> NumericTokenStream).
>
> If you use the same precStep it should work.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>> -----Original Message-----
>> From: Shon Vella [mailto:svella@technologist.com]
>> Sent: Friday, September 25, 2009 4:27 PM
>> To: java-dev@lucene.apache.org
>> Subject: Numeric Field index compatibility
>>
>> I have some indexes that were created using a dev version of 2.9 from
>> early June, when the Numeric field stuff was moved to lucene core from
>> the query contrib package. Now that 2.9 is becoming available, I need to
>> migrate to using the stuff in core and was wondering about the index
>> level compatibility between the two. In other words, can I use the stuff
>> in core against an index that was created using the contrib stuff?
>>
>> -Shon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
RE: Numeric Field index compatibility
Posted by Uwe Schindler <uw...@thetaphi.de>.
The term format did not change since the major revision with Yonik at the
begin of year. Only the API and term generation was changed (NumericField,
NumericTokenStream).
If you use the same precStep it should work.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Shon Vella [mailto:svella@technologist.com]
> Sent: Friday, September 25, 2009 4:27 PM
> To: java-dev@lucene.apache.org
> Subject: Numeric Field index compatibility
>
> I have some indexes that were created using a dev version of 2.9 from
> early June, when the Numeric field stuff was moved to lucene core from
> the query contrib package. Now that 2.9 is becoming available, I need to
> migrate to using the stuff in core and was wondering about the index
> level compatibility between the two. In other words, can I use the stuff
> in core against an index that was created using the contrib stuff?
>
> -Shon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org