Remove TFIDFSimilarity [LUCENE-7720]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
It was already considered worse than BM25 and the removal of coords made it even worse, maybe we should think about removing it entirely? Backward compatibility should be easy since the BM25 similarity uses the same index-time encoding.
---
Migrated from [LUCENE-7720](https://issues.apache.org/jira/browse/LUCENE-7720) by Adrien Grand (@jpountz)
Contributor guide
Research direction
Start by locating TFIDFSimilarity and the code that handles its index-time encoding. Review whether BM25 can preserve compatibility with existing indexes, then identify the affected tests and run them after the removal. Done means TFIDFSimilarity is removed without breaking compatible index reading or search behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100