[LUCENE-10180] Remove usage of lambdas in SegmentMerger?

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 9.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Adrien Grand
• Created: 15/Oct/21 09:01
• Updated: 28/Aug/22 16:28
• Resolved: 19/Oct/21 13:01

Description

SegmentMerger now uses lambdas to share the logic around logging merging times for all file formats.

One problem is that these lambdas get auto-generated names, and it makes it harder to work with profilers since things that should logically end up in the same sub tree end up in different sub trees because two instances of the same lambda get different names.

Issue Links

• links to: GitHub Pull Request #385