Re: Best design for an use case which is going to stress Lucene

You're both true, this doesn't sound like Lucene at all... But the problem of such SQL tables is their size: speaking about millions of customers and thousands of news items, the many-to-many (CustArt) table would end up by containing BILLIONS of lines A bit too big even for an Oracle table, I

Best design for an use case which is going to stress Lucene

Hi all, I'm required to develop an application for searching over news items. There will be thousands of news items, each one will be assigned directly to a list of millions of customerIDs. The query will be done by passing a customerID and will return all news items associated to it. Furthermore,