Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-6399

Benchmark's AbstractQueryMaker.resetInputs should call setConfig

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2
    • Component/s: modules/benchmark
    • Labels:
      None
    • Lucene Fields:
      New

      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!

        Attachments

          Activity

            People

            • Assignee:
              dsmiley David Smiley
              Reporter:
              dsmiley David Smiley
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: