Out-of-dictionary results returned about liblevenshtein-java HOT 6 CLOSED

Seems to equally apply to the Algorithm.STANDARD algorithm.
It starts popping up when maxDistance is increased to 3, although this last comment is of circumstantial nature. Possibly people typically only go up until 2.

from liblevenshtein-java.

Hi,

What do you mean by, findAll results? Also, please provide a test case that demonstrates the issue.

from liblevenshtein-java.

Sorry about that, it was the name of my Scala wrapper around tranduce. It will take a huge amount of creativity being able to demonstrate this without providing the proprietary lexicon... but it should be demonstrated in a reproducible way, I know. Lets put it on hold until I get to that.

from liblevenshtein-java.

Okay. In the meantime, please test your wrapper against version 2.2.0, as the issue #6 was a pretty bad bug and may be the root cause of this.

from liblevenshtein-java.

On first examination, looks like the bug I reported here consistently reproduces with 2.1.2 but not with 2.2.0. I will check again tomorrow. Any idea how the fix for #6 may have solved this?

from liblevenshtein-java.

Yes, I do. Depending on the terms provided, some of the non-final nodes were overwriting the final ones, and vice-versa. The way the final nodes were stored missed a few edge cases. The tiny list I was using for testing happened to not have such terms, which is how the bug made it to production.

While debugging #6, I encountered similar behavior to what this issue describes, which is why I recognized it as the likely root cause.

from liblevenshtein-java.