I’m guessing Mike means the luceneutil benchmarks, which do have some of their 
own Java code, some of which calls IndexWriter#numDocs()

> On 15 Dec 2018, at 10:04, Simon Willnauer <[email protected]> wrote:
> 
> 
> 
> What benchmarks are you talking about? Can you link them?
> 
>> On 14. Dec 2018, at 23:47, Mike Sokolov (JIRA) <[email protected]> wrote:
>> 
>> 
>>  [ 
>> https://issues.apache.org/jira/browse/LUCENE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721848#comment-16721848
>>  ] 
>> 
>> Mike Sokolov commented on LUCENE-8609:
>> --------------------------------------
>> 
>> I think this will break nightly benchmarks? Anyway I'm currently getting 
>> compile errors there
>> 
>>> Allow getting consistent docstats from IndexWriter
>>> --------------------------------------------------
>>> 
>>>              Key: LUCENE-8609
>>>              URL: https://issues.apache.org/jira/browse/LUCENE-8609
>>>          Project: Lucene - Core
>>>       Issue Type: Improvement
>>> Affects Versions: master (8.0), 7.7
>>>         Reporter: Simon Willnauer
>>>         Priority: Major
>>>          Fix For: master (8.0), 7.7
>>> 
>>>       Time Spent: 50m
>>> Remaining Estimate: 0h
>>> 
>>> Today we have #numDocs() and #maxDoc() on IndexWriter. This is enough
>>>  to get all stats for the current index but it's subject to concurrency
>>>  and might return numbers that are not consistent ie. some cases can
>>>  return maxDoc < numDocs which is undesirable. This change adds a 
>>> getDocStats()
>>>  method to index writer to allow fetching consistent numbers for these 
>>> stats.
>> 
>> 
>> 
>> --
>> This message was sent by Atlassian JIRA
>> (v7.6.3#76005)
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to