You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2015/04/06 23:51:12 UTC
[jira] [Updated] (LUCENE-6399) Benchmark's
AbstractQueryMaker.resetInputs should call setConfig
[ https://issues.apache.org/jira/browse/LUCENE-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated LUCENE-6399:
---------------------------------
Attachment: LUCENE-6399_Benchmark_QueryMaker_resetInput_setConfig.patch
> Benchmark's AbstractQueryMaker.resetInputs should call setConfig
> ----------------------------------------------------------------
>
> Key: LUCENE-6399
> URL: https://issues.apache.org/jira/browse/LUCENE-6399
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/benchmark
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: 5.2
>
> Attachments: LUCENE-6399_Benchmark_QueryMaker_resetInput_setConfig.patch
>
>
> 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!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org