It is on the HEAD version in SVN.
See http://wiki.apache.org/jakarta-lucene/SourceRepository for info
on checking out from SVN.
On Aug 25, 2006, at 10:44 AM, Rupinder Singh Mazara wrote:
Where can I find information which version / tag to checkout so as to
get the lazy loading verity of l
It is on the HEAD version in SVN.
See http://wiki.apache.org/jakarta-lucene/SourceRepository for info
on checking out from SVN.
-Grant
On Aug 25, 2006, at 10:44 AM, Rupinder Singh Mazara wrote:
Where can I find information which version / tag to checkout so as to
get the lazy loading ver
Where can I find information which version / tag to checkout so as to
get the lazy loading verity of lucene
Grant Ingersoll wrote:
Large stored fields can affect performance when you are iterating over
your hits (assuming you are not interested in the value of the stored
field at that point
IMO you should avoid storing any data in the index that you don't need for
display. Lucene is an index (and a damn good one), not a database. If you
find yourself storing large amounts of data in the index, this could be an
indication that you may need to re-think your architecture.
In its simp
Large stored fields can affect performance when you are iterating
over your hits (assuming you are not interested in the value of the
stored field at that point in time) for a results display since all
Fields are loaded when getting the Document. The SVN trunk has a
version of lazy loadi
On Friday 11 August 2006 15:07, Prasenjit Mukherjee wrote:
> I have a requirement ( use highlighter) to store the doc content
> somewhere., and I am not allowed to use a RDBMS. I am thinking of using
> Lucene's Field with (Field.Store.YES and Field.Index.NO) to store the
> doc content. Will it hav
I have a requirement ( use highlighter) to store the doc content
somewhere., and I am not allowed to use a RDBMS. I am thinking of using
Lucene's Field with (Field.Store.YES and Field.Index.NO) to store the
doc content. Will it have any negative affect on my search performance ?
I think I hav