Re: document object

2011-03-11 Thread Ian Lea
ge- > From: suman.holani [mailto:suman.hol...@zapak.co.in] > Sent: Friday, March 11, 2011 11:35 AM > To: 'java-user@lucene.apache.org' > Subject: RE: document object > > Hello Erick, > > Hits .length is 1800 > > Version is lucene 3.0.3 > > I need the e

Re: document object

2011-03-11 Thread Ian Lea
heduling with entire fields A, > B,C,D,E > > Regards, > Suman > > > > > > -Original Message- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Thursday, March 10, 2011 7:46 PM > To: java-user@lucene.apache.org > Subject: Re: document obje

RE: document object

2011-03-11 Thread suman.holani
iginal Message- From: suman.holani [mailto:suman.hol...@zapak.co.in] Sent: Friday, March 11, 2011 11:35 AM To: 'java-user@lucene.apache.org' Subject: RE: document object Hello Erick, Hits .length is 1800 Version is lucene 3.0.3 I need the entire result set . As I ll be fetching recor

RE: document object

2011-03-10 Thread suman.holani
t;> Hi Anshum, >> >> Thanks for prompt reply. >> >> I am only storing the fields in index , which I want to get/fetch after >> search. >> >> The area I am not sure is when we call searcher/reader class to initialize >> Document object is heavy? >

Re: document object

2011-03-10 Thread Erick Erickson
i Anshum, >> >> Thanks for prompt reply. >> >> I am only storing the fields in index , which I want to get/fetch after >> search. >> >> The area I am not sure is when we call searcher/reader class to initialize >> Document object is heavy? >

Re: document object

2011-03-10 Thread Anshum
ks for prompt reply. > > I am only storing the fields in index , which I want to get/fetch after > search. > > The area I am not sure is when we call searcher/reader class to initialize > Document object is heavy? > Can we use something else in that place, which doesnot need

RE: document object

2011-03-10 Thread suman.holani
Hi Anshum, Thanks for prompt reply. I am only storing the fields in index , which I want to get/fetch after search. The area I am not sure is when we call searcher/reader class to initialize Document object is heavy? Can we use something else in that place, which doesnot needs to load all doc

Re: document object

2011-03-10 Thread Anshum
Hi Suman, Do you need to load/use all fields that you have stored in the index? If that's not the case I'd suggest you to use the public Document *doc*(int i, FieldSelector fieldSelector) http://lucene.apache

document object

2011-03-10 Thread suman.holani
Hi, I am facing the problem The line in the loop is going very slow giving me a performance hit for (int i = 0; i < hits.length; ++i) { int docId = hits[i].doc; Document d = searcher.doc(docId); //problem } How can I improve

Re: What is the best way to modify a Document object

2009-03-17 Thread Simon Willnauer
Hi Paul, If you do not store all the data inside lucene you have to get you updated data from you spreadsheet again. Even if you would store all the data you would have to update the document by creating a new one and adding it to the index using updateDocument(). You can not update just one single

What is the best way to modify a Document object

2009-03-17 Thread Paul Taylor
I am using lucene to index rows in a spreadsheet , each row is a Document, and the document indexes 10 fields from the row plus the row number used to relate thethe Document to the row number So when someone modifies one of the 10 fields I am interested in a row I have to update the document wi

Re: How to extract Document object after the search?

2009-02-03 Thread Erick Erickson
Here's a writeup I did a couple of years ago that might help... http://wiki.apache.org/lucene-java/FieldSelectorPerformance?highlight=(fieldselector) Best Erick On Tue, Feb 3, 2009 at 5:06 AM, Ian Lea wrote: > > I have not seen much time difference between when I load the single field > & > >

Re: How to extract Document object after the search?

2009-02-03 Thread Ian Lea
> I have not seen much time difference between when I load the single field & > all the fields of a document. That's fine - sometimes it helps, sometimes it doesn't. Depends on the structure of your documents, maybe your hardware, maybe more. And sometimes a small difference, over many documents

RE: How to extract Document object after the search?

2009-02-02 Thread mittals
Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > >> -Original Message- >> From: mittals [mailto:sourabh-931.mit...@morganstanley.com] >> Sent: Monday, February 02, 2009 12:54 PM >> To: java-user@lucene.apache.org >> Subject: How to extract

RE: How to extract Document object after the search?

2009-02-02 Thread Uwe Schindler
t; Subject: How to extract Document object after the search? > > > As per Lucene documentation - > "For good search performance, implementations of this method should not > call > Searcher.doc(int) or IndexReader.document(int) on every document number > encountered.

Re: How to extract Document object after the search?

2009-02-02 Thread Ganesh
Searcher.doc(int) or IndexReader.document(int) will give you the document object and to my knowledge this is the only way available, however it is not advisable to query all documents (MatchAllDocsQuery) and load all document objects. While using Searcher.doc(int) or IndexReader.document(int

Re: How to extract Document object after the search?

2009-02-02 Thread Ian Lea
Hi That quote is from the javadoc for HitCollector/TopDocCollector.collect(). You missed out the bit saying "This is called in an inner search loop". If, as your subject implies, you want to get at the Document object AFTER the search, those methods are fine. Just don't use th

How to extract Document object after the search?

2009-02-02 Thread mittals
he other way to get the Document object to avoid performance bottleneck? -- View this message in context: http://www.nabble.com/How-to-extract-Document-object-after-the-search--tp21788361p21788361.html Sent from the Lucene - Java Users mailing list archiv