[
https://issues.apache.org/jira/browse/LUCENE-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490277#comment-14490277
]
ASF subversion and git services commented on LUCENE-6399:
---------------------------------------------------------
Commit 1672742 from [~dsmiley] in branch 'dev/trunk'
[ https://svn.apache.org/r1672742 ]
LUCENE-6399: Benchmark's QueryMaker.resetInputs should call setConfig
> 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: [email protected]
For additional commands, e-mail: [email protected]
