Hi Shelly, Have you tried sorting in your queries. Is it creating in any issues? Once you open a reader and warm your search with sorting then fieldcache will be loaded for that field. You could see more usage of RAM. You could do as many queries with sorting till you reopen the reader.
If you add document according to increasing / decreasing order then you could prefer sorting on INDEX_ORDER basically it does sorting on document number which is incremental for every document. Try if could control, the way you insert. 12,y,d 100,o,p 1,x,y 23,u,i 31,v,m 22,b,m 109,k,l According to your document, You could use short integer or string as your sort field. You need to worry if you use long or date time sorting as it involves more size. Regards Aditya www.findbestopensource.com On Thu, Aug 19, 2010 at 11:21 AM, Shelly_Singh <shelly_si...@infosys.com> wrote: > Hi Anshum, > > I require sorted results for all my queries and the field on which I need > sorting is fixed; so this lead to me the idea of storing in sorted order to > avoid sorting cost with every query. > > Thanks and Regards, > > Shelly Singh > Center For KNowledge Driven Information Systems, Infosys > Email: shelly_si...@infosys.com > Phone: (M) 91 992 369 7200, (VoIP)2022978622 > > -----Original Message----- > From: Anshum [mailto:ansh...@gmail.com] > Sent: Wednesday, August 18, 2010 5:21 PM > To: java-user@lucene.apache.org > Subject: Re: Sorting a Lucene index > > Hi Shelly, > The search results so returned are sorted either by relevance, index order, > stored field, or custom order. > As you are saying that you would not be able to maintain the index order, > you would have to do the sort at run time. > Sorting on a stored field is not costly and you may use it comfortably. btw, > are you facing any issues in sort time or is it a presumption? > > -- > Anshum Gupta > http://ai-cafe.blogspot.com > > > On Wed, Aug 18, 2010 at 5:12 PM, Shelly_Singh <shelly_si...@infosys.com>wrote: > >> Hi, >> >> I have a Lucene index that contains a numeric field along with certain >> other fields. The order of incoming documents is random and un-predictable. >> As a result, while creating an index, I end up adding docs in random order >> with respect to the numeric field value. >> >> For example, documents may be added in following order: >> 12,y,d >> 100,o,p >> 1,x,y >> 23,u,i >> 31,v,m >> 22,b,m >> 109,k,l >> >> My requirement is that at search time, I want the documents in order of the >> numeric field. >> One, option is to do a score/sort on the numeric field. >> But, this may be a costly operation. >> >> Hence, I am trying to find if there is some way, such that, my stored index >> is sorted by itself. >> >> Please help. >> >> Thanks and Regards, >> >> Shelly Singh >> Center For KNowledge Driven Information Systems, Infosys >> Email: shelly_si...@infosys.com<mailto:shelly_si...@infosys.com> >> Phone: (M) 91 992 369 7200, (VoIP)2022978622 >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
