[
https://issues.apache.org/jira/browse/LUCENE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3656:
----------------------------------
Fix Version/s: 4.0
3.6
> IndexReader's add/removeCloseListener should not use ConcurrentHashMap, just
> a synchronized set
> -----------------------------------------------------------------------------------------------
>
> Key: LUCENE-3656
> URL: https://issues.apache.org/jira/browse/LUCENE-3656
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/index
> Affects Versions: 3.5, 4.0
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Minor
> Labels: curiosity
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3656.patch, LUCENE-3656.patch
>
>
> The use-case for ConcurrentHashMap is when many threads are reading and less
> writing to the structure. Here this is just funny: The only reader is
> close(). Here you can just use a synchronized HashSet. The complexity of CHM
> is making this just a joke :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
