[LUCENE-6399] Benchmark's AbstractQueryMaker.resetInputs should call setConfig

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.2
• Component/s: modules/benchmark
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 06/Apr/15 21:30
• Updated: 28/Aug/22 14:30
• Resolved: 10/Apr/15 20:10

Description

DocMaker.resetInput() will call setConfig. QueryMaker should too for the same reason – so that it can respond to properties that change per round. DocMaker is concrete but QueryMaker is an interface, but this behavior can be put into AbstractQueryMaker.

I found this as some benchmarking was driving me crazy as I couldn't get spatial benchmark queries to see changes I had!