RE: NumericField API

2010-06-01 Thread Uwe Schindler
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 > > po

Re: NumericField API

2010-06-01 Thread Mark Miller
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 ---

Re: NumericField API

2010-06-01 Thread Mindaugas Žakšauskas
ents in it? If this > is so, you have a mixed field contents and then behavior of range query and > sort is wrong. I have completely reindexed all documents so this clearly isn't the case. > >> 3) NumericField API is marked as experimental and volatile >> (http://lucene.ap

RE: NumericField API

2010-06-01 Thread Uwe Schindler
does that relate to passing index=true VS index=false in NumericField > constructor? Which of the two is preferred, assuming I need the data to be > stored and indexed as well as being able to run range queries? This is incorrect. If you want to sort, you must turn on indexing, without that sorti

NumericField API

2010-06-01 Thread Mindaugas Žakšauskas
Field.LONG and SortField.STRING should only be as in numeric sorting VS lexicographical sorting, right? Why would changing to SortField.LONG prevent the exception? 2) How does that relate to passing index=true VS index=false in NumericField constructor? Which of the two is preferred, assuming I need th