Hello, Lucene team,
My team and I are currently running a quite old version of the lucene-core library - 3.0.0. As part of our internal memory optimization fixes, we are also planning to migrate to newer version. Research so far brought me to think our best risk-benefit trade off is Lucene 3.6.2. (We are planning to go to the 4.X branch - current development, but that would perhaps come in our own major version upgrade) However, due to this here issue, I would really like to know which version of the core library does not have it? 3.6.1 perhaps? Or 3.5.X?
As I understand from your comments, you are not yet planning to provide a fix on the 3.6.X branch - please advise to which version we should migrate where this bug is not present?
Thank you very much!
Vassil Zorev, web developer