Doug Cutting wrote: > Like anything else in an all-volunteer operation, it will only happen if > folks volunteer to do it. Someone needs to take the lead and index a > reference collection with a couple of different Similarity > implementations and post the code and the results of various searches > for folks to evaluate. Chuck?
Although I would like to volunteer for this, I'm unlikely to find the time to take the lead. I'm tuning and customizing Lucene as a small part of developing a new site. I can continue to share my observations and recommendations, along with code for new Lucene functionality that is important to the effort (e.g., DistributingMultiFieldQueryParser and MaxDisjunctionQuery). The limited time I have to work on Lucene itself must be focused on requirements for my site (e.g., achieving intrinsic score normalization). If someone else takes the lead on the relevance benchmark, I'd be happy to contribute my Similarity and query processing tools and have them compared to the Lucene's current defaults. Sorry, Chuck > -----Original Message----- > From: Doug Cutting [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 27, 2005 11:08 AM > To: Lucene Developers List > Subject: Re: How to proceed with Bug 31841 - MultiSearcher problems with > Similarity.docFreq() ? > > Chuck Williams wrote: > > Christoph Goller writes: > > > You may be right. But I am not completely convinced. I think > > > this should be decided based on the proposed benchmark evaluation. > > > > Is that still happening? > > Like anything else in an all-volunteer operation, it will only happen if > folks volunteer to do it. Someone needs to take the lead and index a > reference collection with a couple of different Similarity > implementations and post the code and the results of various searches > for folks to evaluate. Chuck? > > Doug > > --------------------------------------------------------------------- > 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]
