API changes in 2.9

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

API changes in 2.9

Ganesh - yahoo
Hello all,

I am planning to upgrade from 2.4.1 to 2.9.1. I could see some API changes and older APIs are deprecated. In 2.4, I use 'NumberTools' class to convert long to String and now this API is deprecated. I think i have to use 'NumericField' or 'NumericUtils', but in both the class there is a note "NOTE: This API is experimental and might change in incompatible ways in the next release. "

Shall I go ahead and update the API or use the older one till 3.0?

This red note is added to couple of other placeses. Shall we go ahead and use these API or wait for 3.0?

Regards
Ganesh



Send instant messages to your online friends http://in.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: API changes in 2.9

Uwe Schindler
You can use these APIs. They are only marked as experimental not because
they are unstable or something like that, it means the API may change
suddenly (methods get removed and so on). In 3.0 (which was released *now*)
it is still experimental. So it's more "subject to change" than "unstable".

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [hidden email]

> -----Original Message-----
> From: Ganesh [mailto:[hidden email]]
> Sent: Thursday, November 26, 2009 9:47 AM
> To: [hidden email]
> Subject: API changes in 2.9
>
> Hello all,
>
> I am planning to upgrade from 2.4.1 to 2.9.1. I could see some API changes
> and older APIs are deprecated. In 2.4, I use 'NumberTools' class to
> convert long to String and now this API is deprecated. I think i have to
> use 'NumericField' or 'NumericUtils', but in both the class there is a
> note "NOTE: This API is experimental and might change in incompatible ways
> in the next release. "
>
> Shall I go ahead and update the API or use the older one till 3.0?
>
> This red note is added to couple of other placeses. Shall we go ahead and
> use these API or wait for 3.0?
>
> Regards
> Ganesh
>
>
>
> Send instant messages to your online friends http://in.messenger.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: API changes in 2.9

Ganesh - yahoo
Thanks.

I used NumberTool to convert the int to string. In 2.9, NumericField is to be used but it stores it based on some precision. I think the way the integer data gets indexed is changed from 2.4 to 2.9. This means my customers using 2.4.1 should rebuild their index.

Whether 2.9 could able to modify\search the index created by 2.4.1? Is backward compatibility maintained?

Regards
Ganesh


----- Original Message -----
From: "Uwe Schindler" <[hidden email]>
To: <[hidden email]>
Sent: Thursday, November 26, 2009 2:26 PM
Subject: RE: API changes in 2.9


> You can use these APIs. They are only marked as experimental not because
> they are unstable or something like that, it means the API may change
> suddenly (methods get removed and so on). In 3.0 (which was released *now*)
> it is still experimental. So it's more "subject to change" than "unstable".
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [hidden email]
>
>> -----Original Message-----
>> From: Ganesh [mailto:[hidden email]]
>> Sent: Thursday, November 26, 2009 9:47 AM
>> To: [hidden email]
>> Subject: API changes in 2.9
>>
>> Hello all,
>>
>> I am planning to upgrade from 2.4.1 to 2.9.1. I could see some API changes
>> and older APIs are deprecated. In 2.4, I use 'NumberTools' class to
>> convert long to String and now this API is deprecated. I think i have to
>> use 'NumericField' or 'NumericUtils', but in both the class there is a
>> note "NOTE: This API is experimental and might change in incompatible ways
>> in the next release. "
>>
>> Shall I go ahead and update the API or use the older one till 3.0?
>>
>> This red note is added to couple of other placeses. Shall we go ahead and
>> use these API or wait for 3.0?
>>
>> Regards
>> Ganesh
>>
>>
>>
>> Send instant messages to your online friends http://in.messenger.yahoo.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Send instant messages to your online friends http://in.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: API changes in 2.9

Uwe Schindler
> Thanks.
>
> I used NumberTool to convert the int to string. In 2.9, NumericField is to
> be used but it stores it based on some precision. I think the way the
> integer data gets indexed is changed from 2.4 to 2.9. This means my
> customers using 2.4.1 should rebuild their index.

Exactly. Because of that NumberTools is deprecated as a warning, not to use
it for *new* developments. The numeric values are stored completely
different and can only be queried using NumericRangeQuery.

These deprecations needed for index compatibility are *not* removed in 3.0
(they are targeted for 4.0, when indexes < 3.0 cannot be read anymore). So
for performance reasons (if you do range queries on your numeric fields),
you should reindex.

> Whether 2.9 could able to modify\search the index created by 2.4.1? Is
> backward compatibility maintained?

Yes it is maintained, but you should get rid of deprecated APIs. And for the
numeric case, you cannot mix old/new API on the same field. Switch to the
new API in complete (reindex) or let it as it is.

Uwe

 

> Regards
> Ganesh
>
>
> ----- Original Message -----
> From: "Uwe Schindler" <[hidden email]>
> To: <[hidden email]>
> Sent: Thursday, November 26, 2009 2:26 PM
> Subject: RE: API changes in 2.9
>
>
> > You can use these APIs. They are only marked as experimental not because
> > they are unstable or something like that, it means the API may change
> > suddenly (methods get removed and so on). In 3.0 (which was released
> *now*)
> > it is still experimental. So it's more "subject to change" than
> "unstable".
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [hidden email]
> >
> >> -----Original Message-----
> >> From: Ganesh [mailto:[hidden email]]
> >> Sent: Thursday, November 26, 2009 9:47 AM
> >> To: [hidden email]
> >> Subject: API changes in 2.9
> >>
> >> Hello all,
> >>
> >> I am planning to upgrade from 2.4.1 to 2.9.1. I could see some API
> changes
> >> and older APIs are deprecated. In 2.4, I use 'NumberTools' class to
> >> convert long to String and now this API is deprecated. I think i have
> to
> >> use 'NumericField' or 'NumericUtils', but in both the class there is a
> >> note "NOTE: This API is experimental and might change in incompatible
> ways
> >> in the next release. "
> >>
> >> Shall I go ahead and update the API or use the older one till 3.0?
> >>
> >> This red note is added to couple of other placeses. Shall we go ahead
> and
> >> use these API or wait for 3.0?
> >>
> >> Regards
> >> Ganesh
> >>
> >>
> >>
> >> Send instant messages to your online friends
> http://in.messenger.yahoo.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> Send instant messages to your online friends http://in.messenger.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]