Re: Stored fields access

yeah, i would like to see a more "term-vector"/sax like api for extracting values that requires no extra object overhead as well pass in a "collector" that will call methods as fields are encountered (and can return false if walking the document should stop (or some Enum for more options)) i jus

Re: Stored fields access

Missed that, I have a heap of unread Jira mails :/ Okay, you're reusing Document object and the list inside. To reuse Fieldable instances you'd have to do some very awkward things. More awkward things are required to extract your longed-for values from the Document. To add insult to injury, Docume

Re: Stored fields access

I created LUCENE-2276 a couple of days ago to at least allow reusing Document objects (didn't see any interest from anyone though) -- Tim Erick Erickson wrote: > OK, never mind > > Erick > > On Thu, Feb 25, 2010 at 1:48 PM, Earwin Burrfoot > wrote: > > My issu

Re: Stored fields access

My issue is with extra objects created in the process. Field selection can be handled with, well, FieldSelector. 2010/2/25 Erick Erickson : > Does LazyLoading address this? I'm assuming your issue is > that the default behavior loads the entire document regardless > of whether you actually want al

Re: Stored fields access

OK, never mind Erick On Thu, Feb 25, 2010 at 1:48 PM, Earwin Burrfoot wrote: > My issue is with extra objects created in the process. Field selection > can be handled with, well, FieldSelector. > > 2010/2/25 Erick Erickson : > > Does LazyLoading address this? I'm assuming your issue is > >

Re: Stored fields access

Does LazyLoading address this? I'm assuming your issue is that the default behavior loads the entire document regardless of whether you actually want all the fields. Erick On Thu, Feb 25, 2010 at 7:52 AM, Earwin Burrfoot wrote: > I'm thinking, should Lucene introduce new interface to read s

Stored fields access

I'm thinking, should Lucene introduce new interface to read stored document fields? Current 'Document document(int n)' mechanism is barely usable due to overhead involved. While I believe underlying index structure works pretty fast (if it fits in memory, as is the case for most performance-concer