Lazy field loading error

[jason rutherglen <ja...@yahoo.com>]

I implemented lazy field loading in Solr, but then get messed up results or EOFExceptions.  The index is fine, I turned off lazy loading and it looks fine.  Is this known behavior?

Re: Lazy field loading error

[jason rutherglen <ja...@yahoo.com>]

Looks like a bug in Lucene, the lazy loading is fairly simple to implement.  I guess I should post this to the Lucene dev list and I don't think lazy loading is all that necessary for Solr.  

----- Original Message ----
From: Chris Hostetter <ho...@fucit.org>
To: solr-dev@lucene.apache.org; jason rutherglen <ja...@yahoo.com>
Sent: Sunday, September 3, 2006 4:41:58 PM
Subject: Re: Lazy field loading error

: I implemented lazy field loading in Solr, but then get messed up results
: or EOFExceptions.  The index is fine, I turned off lazy loading and it
: looks fine.  Is this known behavior?

I think it's safe to say you are in uncharted territory -- i certianly
wouldn't categorize an EOFException as "known behavior", but anythings
possible when you start modifying guts of Solr.  Getting "messed up
results" wouldnt' suprise me if there was a bad interaction between the
code you modified to do lazy loading and the document cache -- but it's
hard to say without knowing exactly how you turned on the lazy loading; it
might be a bug in your changes, it might be a bug in Solr, it might be a
bug in the lazy loading in the lucene core.




-Hoss

Re: Lazy field loading error

[Chris Hostetter <ho...@fucit.org>]

: I implemented lazy field loading in Solr, but then get messed up results
: or EOFExceptions.  The index is fine, I turned off lazy loading and it
: looks fine.  Is this known behavior?

I think it's safe to say you are in uncharted territory -- i certianly
wouldn't categorize an EOFException as "known behavior", but anythings
possible when you start modifying guts of Solr.  Getting "messed up
results" wouldnt' suprise me if there was a bad interaction between the
code you modified to do lazy loading and the document cache -- but it's
hard to say without knowing exactly how you turned on the lazy loading; it
might be a bug in your changes, it might be a bug in Solr, it might be a
bug in the lazy loading in the lucene core.




-Hoss