Greetings,
I too have a strong need to handle multiple words. Also I have run in to a
limitation within the current SpellCheckerRequestHandler where it does not
identify if a word is spelled correctly or not. This is a problem, for if
there are no suggestions, one cannot currently tell if the word is spelled
correctly, or if there are just are no matches in the index.
I have made modifications to the SpellCheckerRequestHandler source code to
handle all of these issues. It reports if a word is correctly spelled or not,
and it can handle multiple words too. The nice thing is that it should NOT
"break" current implementations are are using it the way it currently exists.
I am also wanting to ensure the design format of how the
SpellCheckerRequestHandler plays well with other technologies such as Prototype.
I am in the process of making significant changes to our application and I have
not been able to fully write the interface to utilize these new spelling
features, so as such, I was hesitant to make any posts in this area. I was
wanting to fully test these changes to ensure their optimal functionality and
structure before I said anything on this thread or the developer's thread.
If you like, I can post the source code changes that I made to the
SpellCheckerRequestHandler, but at this time I am not ready to open a JIRA
issue and submit the changes back through the subversion. I will need to do a
little more testing, documentation, and create some unit tests to cover all of
these changes, but what I have been able to perform, it is working very well.
Please let me know if you would like me to explain at a higher level what these
changes are and how the output will look. I personally would like some
feedback, but right now (Monday AM) I am pressed for time. This afternoon I
could give you some examples of how these changes look under the "standard"
format and the multi-word formats.
One area that I was wanting to really include with the documentation, is how
they can be utilized with Prototype using the JSon output type. As I stated
earlier, I have not had a chance to write the code yet, but I am thinking that
with utilizing Prototype's AJax support with Solr and the JSon output type, one
should be able to get a great deal of functionality with very few lines of code.
Anyway, let me know if you want me to expand on any of these subjects and I
should be able to get back with you this afternoon.
If you are wanting me to create a jar so you to play with these changes, let me
know and I can email it directly to you.
Thanks for your time,
Scott Tabar
---- Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
Hello,
Did I miss this contribution or did it not happen? I'm referring to the change
to the SpellCheckerRequestHandler to handle spelling corrections/suggestions
for multi-word queries.
Any chance you can provide a patch?
Thanks!
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
----- Original Message ----
From: climbingrose <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Sunday, August 12, 2007 8:24:12 AM
Subject: Re: Spell Check Handler
I'm happy to contribute code for the SpellCheckerRequestHandler. I'll post
the code once I strip off stuff related to our product.
On 8/12/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
>
> <http://issues.apache.org/jira/browse/LUCENE-626>On 11/08/07,
> climbingrose<
> [EMAIL PROTECTED]> wrote:
> >
> > That's exactly what I did with my custom version of the
> > SpellCheckerHandler.
> > However, I didn't handle suggestionCount and only returned the one
> > corrected
> > phrase which contains the "best" corrected terms. There is an issue on
> > Lucene issue tracker regarding multi-word spellchecker:
> >
> https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >
>
>
> I'd be interested to take a look at your modifications to the
> SpellCheckerHandler, how did you handle phrase queries? maybe we can open
> a
> JIRA issue to expand the spell checking functionality to perform analysis
> on
> multi-word input values.
>
> I did find http://issues.apache.org/jira/browse/LUCENE-626 after looking
> at
> LUCENE-550, but since these patches are not yet included in the Lucene
> trunk
> yet it might be a little difficult to justify implementing them in Solr.
>
--
Regards,
Cuong Hoang
