[
https://issues.apache.org/jira/browse/LUCENE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2966:
---------------------------------------
Fix Version/s: (was: 3.1)
3.2
Pushing this to 3.2 -- removing sync'd from the norms methods is a tad spooky,
and I think the concurrency bug only results in a false assert trip, so, we can
let this fix bake only in trunk I think...
> SegmentReader.doCommit should be sync'd; norms methods need not be sync'd
> -------------------------------------------------------------------------
>
> Key: LUCENE-2966
> URL: https://issues.apache.org/jira/browse/LUCENE-2966
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.2, 4.0
>
> Attachments: LUCENE-2966.patch
>
>
> I fixed the failure in TestNRTThreads, but in the process tripped an assert
> because SegmentReader.doCommit isn't sync'd.
> So I sync'd it, but I don't think the norms APIs need to be sync'd -- we
> populate norms up front and then never change them. Un-sync'ing them is
> important so that in the NRT case calling IW.commit doesn't block searches
> trying to pull norms.
> Also some small code refactoring.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]