t;> about here. Without some such detail, it's really hard to make a
> >> recommendation.
> >>
> >> Best
> >> Erick
> >>
> >> On Wed, Sep 1, 2010 at 9:30 AM, Sertic Mirko, Bedag
> >> wrote:
> >>
> >> > The data
ntry matches to
>> many
>> > index entries, so storing it in the index would be redundant. Also there
>> > would be the challenge to keep index and db in sync. Any ideas?
>> >
>> > Mirko
>> >
>> > -Ursprünglich
entries, so storing it in the index would be redundant. Also there
> > would be the challenge to keep index and db in sync. Any ideas?
> >
> > Mirko
> >
> > -Ursprüngliche Nachricht-
> > Von: Ian Lea [mailto:ian@gmail.com]
> > Gesendet: Mittwoch, 1.
t; Gesendet: Mittwoch, 1. September 2010 15:17
> An: java-user@lucene.apache.org
> Betreff: Re: Combine data from index and db before sorting and pagination
>
> If the sorting and pagination doesn't require data from the database,
> just do db lookups for the hits on a page, page by
]
Gesendet: Mittwoch, 1. September 2010 15:17
An: java-user@lucene.apache.org
Betreff: Re: Combine data from index and db before sorting and pagination
If the sorting and pagination doesn't require data from the database,
just do db lookups for the hits on a page, page by page as required.
But i
If the sorting and pagination doesn't require data from the database,
just do db lookups for the hits on a page, page by page as required.
But if the db data is required I'd suggest storing it in the index.
--
Ian.
On Wed, Sep 1, 2010 at 1:43 PM, Sertic Mirko, Bedag
wrote:
> Hi
>
>
>
> I need t
Hi
I need to implement sorting and pagination of lucene search results.
This is quite easy, but I have to combine Data from the index with data
from a database. The index has the fulltext data plus a unique
identifier for a record from the database. The database stores
additional data. Fulltext
