Hi Nader, I was wondering if you'd mind me asking you a couple of questions about your implementation?
The main thing I'm interested in is how you handle updates to Lucene's index. I'd imagine you have a fairly high turnover of CVs and jobs, so index updates must place a reasonable load on the CPU/disk. Do you keep CVs and jobs in the same index or two different ones? And what is the process you use to update the index(es) - do you batch-process updates or do you handle them in real-time as changes are made? Any insight you can offer would be much appreciated as I'm about to implement something similar and am a little unsure of the best approach to take. We need to be able to handle indexing about 60,000 documents/day, while allowing (many) searches to continue operating alongside. Thanks! Chris "Nader S. Henein" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > We use Lucene http://www.bayt.com , we're basically an on-line > Recruitment site and up until now we've got around 500 000 CVs and > documents indexed with results that stump Oracle Intermedia. > > Nader Henein > Senior Web Dev > > Bayt.com > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 04, 2003 6:09 PM > To: [EMAIL PROTECTED] > Subject: commercial websites powered by Lucene? > > > > Hello All, > > I've been trying to find examples of large commercial websites that > use Lucene to power their search. Having such examples would > make Lucene an easy sell to management > > Does anyone know of any good examples? The bigger the better, and > the more the better. > > TIA, > -John > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
