On Oct 6, 2008, at 4:08 PM, Jason Rennie wrote:
I've noticed a few issues with spellcheck as I've been testing it
out for
use on our site...
1. Rebuild breaks requests - I'm using rebuildOnCommit ATM. If a
commit
is going on and files are being rebuilt in the spellcheck data dir,
spellcheck requests yield bogus answers. I.e. I can issue identical
requests and get drastically different answers. The first time, I
get
suggestions and "correctlySpelled" is false. The second time
(during the
commit), I get no suggestions and "correctlySpelled" is true.
Shouldn't
spellcheck use the old index until the new one is ready for use,
like solr
does with optimizes?
Hmm, that sounds like a bug.
2. Inconsistent ordering - The first suggestion changes depending
on the
spellcheck.count that I specify. If my query is "chanl" and I ask
for one
result, the suggestion is "chant" (freq. 16). If I ask for 5
results, the
first suggestion is also "chant"; the other 4 suggestions are less
frequent
(e.g. "chang", freq. 11). However, if I ask for 10 results, the
first
suggestion is "chanel" (freq. 1296); #2 and #3 are "chant" and
"chang"; #9
is "chan" (freq. 174). Shouldn't spellcheck return the best
suggestion
first? In my case, shouldn't "chanel" always top "chant" and
"chang" since
they all have the same edit distance yet "chanel" is two orders of
mangnitude more popular?
Is there anyway you can write up a small test case? This definitely
sounds like a bug.
Is there anything I could be doing wrong to create these problems?
I suppose there is, but it doesn't sound like it.
If not,
are these known issues? If not, should I create jira's for them?
Can you try to isolate it to a small repeatable example?
Thanks,
Grant
