contrib/HighFreqTerms should use ByteRefs but provide human-readable output [LUCENE-2403]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
contrib HighFreqTerms was upgraded to use the flex APIs but currently displays hex code if you do not give a field argument and strings if you do.
The conversion to a string should be consistent and should occur just before output rather than when loading the priority queue
See: http://n3.nabble.com/Bug-in-contrib-misc-HighFreqTerms-java-tc719202.html#a719202
---
Migrated from [LUCENE-2403](https://issues.apache.org/jira/browse/LUCENE-2403) by Tom Burton-West, updated May 09 2016
Contributor guide
Research direction
Start with contrib/HighFreqTerms and trace how terms are loaded into the priority queue and later displayed, comparing behavior with and without a field argument. Check the linked LUCENE-2403 discussion for context. Done means output uses consistent human-readable strings in both cases, with conversion occurring immediately before output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100