Re: Scaling out/up or a mix

There is no single answer -- this is always application specific. Without knowing anything about what you are doing: 1. disk i/o is probably the most critical. Go SSD or even RAM disk if you can, if performance is absolutely critical 2. Sometimes CPU can become an issue, but 8 cores is probably

Re: Delete by docId in IndexWriter

This requires tracking the genealogy of docids as they are merged inside IndexWriter. It's doable, so if you're particularly interested feel free to open a jira issue. On Sun, Jun 28, 2009 at 2:21 AM, Shay Banon wrote: > > Hi, > > I have a case where deleting documents by doc id make sense (I

Re: Optimizing unordered queries

On Fri, Jun 26, 2009 at 11:06 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Thu, Jun 25, 2009 at 10:11 PM, Nigel wrote: > > > Currently we're (perhaps naively) doing the equivalent of > > query.weight(searcher).scorer(reader).score(collector). Obviously > there's a > > certain a

Re: Optimizing unordered queries

On Fri, Jun 26, 2009 at 10:52 AM, eks dev wrote: > > also see, > http://lucene.apache.org/java/2_2_0/api/org/apache/lucene/search/BooleanQuery.html#getAllowDocsOutOfOrder() Interesti

Re: Optimizing unordered queries

On Fri, Jun 26, 2009 at 10:51 AM, eks dev wrote: > > You omitNorms(), did you also omitTf()? We did, but had to include TF after all since omitting it also dropped position information, which we needed for phrase queries. I didn't think it was possible to remove just the TFs without the positi

Re: Scaling out/up or a mix

Hi. I think I need to be more specific. What I am trying to find out is if I should aim for: CPU (2x4 cores, 2.0-3.0Ghz)? or perhaps just a 4 cores is enough. Fast disk IO: 8 disks, RAID1+0 ? or perhaps 2 disks is enough... RAM - if the index does not fit into RAM how much RAM should I then buy ?

RE: Correctly indexing latitude and longitude values in Lucene

Thanks Uwe...but I have not mentioned the padding logic in my earlier mail.Just wanted to know if that logic would work. Uwe Schindler wrote: > > I already responded to your eMail and answered all your questions! > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thet

RE: Correctly indexing latitude and longitude values in Lucene

I already responded to your eMail and answered all your questions! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: mitu2009 [mailto:musicfrea...@gmail.com] > Sent: Sunday, June 28, 2009 7:39 PM > To: java

Correctly indexing latitude and longitude values in Lucene

Hi, Am working on a "US based nearest city search within a given radius" functionality using Lucene API. Am indexing city's lat and long values in Lucene as follows: doc.Add(new Field("latitude", paddedLatitude, Field.Store.YES, Field.Index.UN_TOKENIZED)); doc.Add(new Field("longit

MultiSegmentReader problems - current is null

Hi, I have an index that is a multi-segment index (how come it is created this way?) When I try to get the freq of a term at the following way: TermDocs tDocs = this.indexReader.termDocs(term); tf = tDocs.freq(); the greq method : public int freq() { return current.freq(); } is in

Delete by docId in IndexWriter

Hi, I have a case where deleting documents by doc id make sense (I know before hand the docs I want to delete based on the doc id). I am wondering why the API is not exposed in the IndexWriter (as it is in IndexReader). I understand that this API is more "expert" than typical usage, but it all