On Thursday 09 March 2006 15:54, Yonik Seeley wrote:
> On 3/9/06, Øyvind Stegard <[EMAIL PROTECTED]> wrote:
> > - How does many stored fields eventually affect indexing/query
> > performance compared to if no fields were stored (only indexed) ?
>
> Additional stored fields should have no effect on
On 3/9/06, Øyvind Stegard <[EMAIL PROTECTED]> wrote:
> - How does many stored fields eventually affect indexing/query performance
> compared to if no fields were stored (only indexed) ?
Additional stored fields should have no effect on querying (the
internal information about a field is looked up
On Thursday 09 March 2006 14:55, Samuru Jackson wrote:
> Is there a way to save an object to the a lucene index?
>
> In my project I noticed that the performance bottleneck is my
> database. Lucene gives back a result in no time but to retrieve the
> corresponding data sets at the backend in the da
On 3/9/06, Samuru Jackson <[EMAIL PROTECTED]> wrote:
> Is there a way to save an object to the a lucene index?
Any field may be stored as well as indexed, or stored and not indexed.
If a field is stored only (not indexed), you can opt to store it as
binary or compressed binary.
See the JavaDoc fo
Is there a way to save an object to the a lucene index?
In my project I noticed that the performance bottleneck is my
database. Lucene gives back a result in no time but to retrieve the
corresponding data sets at the backend in the database can take long
especially if you need to execeute many que