Hi,
> >> 3) NumericField API is marked as experimental and volatile
> >> (http://lucene.apache.org/java/3_0_1/api/core/index.html). Is there
> >> any other "stable" API I can rely on in Lucene 3.0? If not, what
> >> would be
> > possible
> >> NumericField replacement I could use now?
> >
> > "Expe
On 6/1/10 9:34 AM, Mindaugas Žakšauskas wrote:
It's just an early
observation as historically Lucene has been doing an amazing job in
terms of API stability.
Yes it has :)
Get ready for even more change in that area though :)
--
- Mark
http://www.lucidimagination.com
---
Hi,
Thanks for your reply Uwe. Just a couple of notes:
>> In order to get rid of this exception, I had to change one of the
> following:
>> - SortField must be changed from SortField.STRING to SortField.LONG
>
> This does the trick and is *not* weird. You are using *numeric* fields, so
> you cann
Hi,
> I have recently been in charge of converting code that was using
> pre-3.0 API to be compatible with 3.0 API.
>
> There was a piece of code which was storing a date field:
>
> String date = "20091231131415"; // MMddHHmmss new
> Field("creationDate", date, Field.Store.YES, Field.Index.U
