Yep. That's exactly it. The spellCheckCompRH was merely an example
of how to do the necessary configuration with out screwing up the
other examples.
On Sep 24, 2008, at 4:22 PM, Jason Rennie wrote:
On Wed, Sep 24, 2008 at 4:07 PM, Grant Ingersoll
<[EMAIL PROTECTED]>wrote:
Just mimic the configuration for the spellCheckCompRH in the
handler that
you use for querying.
Sounds even better. Let me make sure I'm reading you correctly. Is
the
idea to add lines like this to the requestHandler we normally use?
<lst name="defaults">
<!-- omp = Only More Popular -->
<str name="spellcheck.onlyMorePopular">false</str>
<!-- exr = Extended Results -->
<str name="spellcheck.extendedResults">false</str>
<!-- The number of suggestions to return -->
<str name="spellcheck.count">1</str>
</lst>
<arr name="last-components">
<str>spellcheck</str>
</arr>
Thanks,
Jason
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
