[LUCENE-3656] IndexReader's add/removeCloseListener should not use ConcurrentHashMap, just a synchronized set

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.5, 4.0-ALPHA
• Fix Version/s: 3.6, 4.0-ALPHA
• Component/s: core/index
• Labels: curiosity
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 19/Dec/11 14:43
• Updated: 28/Aug/22 13:04
• Resolved: 20/Dec/11 18:02

Description

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