mark harwood wrote:
For these outlier situations is it worth adding a "maxDf" property to TermQuery like BooleanQuery's maxClause query-time control? I could fix my problem in my own app-specific query construction code but I wonder if others would find it a useful fix to add to TermQuery in the Lucene core?
Another approach is to use a TopDocCollector (in 1.9 only) and override the collect() method to, if too much time has transpired, throw an exception to stop the query with the results found thus far.
For an example of how to extend TopDocCollector, see: http://svn.apache.org/viewcvs.cgi/lucene/nutch/trunk/src/java/org/apache/nutch/searcher/LuceneQueryOptimizer.java?view=markup Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
