Re: Merge policy, optimization for small frequently changing indexes.

Hi I have one more question, does Lucene purge the deleted documents before merging the segments, or purging of deleted documents done only when optimized? On Thu, Sep 30, 2010 at 4:59 PM, Naveen Kumar wrote: > Hi > I have a Very large number (say 3 million) of frequently changing Small > index

Need help regarding Lucene Document Iteration...

Hi, i am doing the following in java. I am searching through a lucene index and getting a Collection of Documents. Below is the code that i have written. Collection docCollection= new ArrayList(); try { Query query = new TermQuery(new Term(nameType, queryStr));

RE: Numeric range query not returning results

Hi Uwe, My example wasn't very clear, as I have a load of other code in my actual implementation and I was trying to cut it down for clarity. This is actually my indexing service for my Datanucleus Cassandra plugin, so I have a 1 to 1 relationship where a single document corresponds to a Persist

Recreate segment infos

Lets say the segment infos file is missing, and I'm aware of CheckIndex, however is there a tool to recreate a segment infos file? - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail:

Matching Documents BitSet

In lucene 3, is there an equivalent to obtaining a BitSet of documents from an Index as there was in version 2.x? I'm trying to put together an upgrade path. Thanks! - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.

RE: Updating documents with fields that aren't stored

Yes, even for IW.getReader() - from : Now Lucene offers a unified API where one calls getReader and any updates are immediately searchable. I.e., the reader returned by getReader doesn't track updates; it too represents a sh

Re: Updating documents with fields that aren't stored

Even for IndexWriter.getReader (near real-time)? "changes made during an IndexWriter session can be quickly made available for searching without closing the writer nor calling commit(long)." http://lucene.apache.org/java/3_0_2/api/all/org/apache/lucene/index/IndexWriter.html#getReader()

RE: Updating documents with fields that aren't stored

This is not a defect: . > -Original Message- > From: Justin [mailto:cry...@yahoo.com] > Sent: Monday, October 04, 2010 2:03 PM > To: java-user@lucene.apache.org > Subject: Updating doc

Updating documents with fields that aren't stored

Hi all, The JavaDocs do not appear to mention that only stored fields persist IndexWriter.updateDocument. When opening new readers, from either IndexWriter.getReader or IndexReader.open, neither TermDocs nor IndexSearcher will find terms in fields which weren't stored. Existing readers, howeve

Re: question about Scorer.freq()

On Mon, Oct 4, 2010 at 1:12 PM, Michael McCandless wrote: > I'll open an issue for this. OK I opened https://issues.apache.org/jira/browse/LUCENE-2686 Mike - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For

Re: question about Scorer.freq()

On Mon, Oct 4, 2010 at 7:32 AM, Koji Sekiguchi wrote: > Hi Mike, > >> Hmm are you only gathering the MUST_NOT TermScorers?  (In which case >> I'd expect that the .docID() would not match the docID being >> collected).  Or do you also see .docID() not matching for SHOULD and >> MUST sub queries? >

Re: question about Scorer.freq()

Hmm are you only gathering the MUST_NOT TermScorers? (In which case I'd expect that the .docID() would not match the docID being collected). Or do you also see .docID() not matching for SHOULD and MUST sub queries? Also, are you sure you are getting BooleanScorer2? Because I think this feature

StringIndexCache throws ArrayIndexOutOfBound

Hello all We are migrating our apps from 2.4.1 to 2.9.3, removing deprecated calls so to fast switch to 3.0.2 asap At startup, our apps look for the min and max value of some configured fields, to let the user know the range of documents he/she is looking at and to filter them One of these

RE: StringIndexCache throws ArrayIndexOutOfBound

Fieldcache only support documents with one value per doc! So you are adding a multivalued field, which is not supported! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Federico Fissore [mailto:feder...

Re: question about Scorer.freq()

Hi Mike, Hmm are you only gathering the MUST_NOT TermScorers? (In which case I'd expect that the .docID() would not match the docID being collected). Or do you also see .docID() not matching for SHOULD and MUST sub queries? The snippet I copy-n-paste at previous mail was not appropriate. Sor

RE: Numeric range query not returning results

This test works perfectly and returns 1 doucment: public void testToddNine() throws Exception { RAMDirectory directory = new RAMDirectory(); IndexWriter writer = new IndexWriter(directory, new WhitespaceAnalyzer(), true, MaxFieldLength.UNLIMITED); try { Document doc = n