[LUCENE-6821] TermQuery's constructors should clone the incoming term

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.4, 6.0
• Lucene Fields: New
• Assignee: Tommaso Teofili
• Reporter: Adrien Grand
• Created: 29/Sep/15 12:53
• Updated: 28/Aug/22 14:43
• Resolved: 21/Oct/15 09:43

Description

This is a follow-up of LUCENE-6435: the bug stems from the fact that you can build term queries out of shared BytesRef objects (such as the ones returned by TermsEnum.next), which is a bit trappy. If TermQuery's constructors would clone the incoming term, we wouldn't have this trap.