CALL SUGGEST not matching on trigrams

[D3M05]

should be fixed at ec19c5b

Originally posted by @tomatolog in #271

I'm running into the same problem referenced in the original issue linked. I noticed when trying to match "Geroge" to "George", you don't get any hits because neither "GER" or "OGE" match "GEO RGE". In the original issue, the solution was to convert strings that are 5 characters or less into bigrams instead of trigrams. I'm wondering if bigrams should be done on even larger words up to maybe 6-8 characters? I suppose it depends on if there is a big performance or resources hit for bigrams vs trigrams?

[tomatolog]

it might be better to add a new call suggest option to disable initial pass of the bi \ tru gramm filtering and get into the scan of the whole dictionary with the Levenshtein distance function.

It could be slow on production size data however it will allow to get all cases into result set without fixes of the bi \ tru gramm pre filter stage.