You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Commit Tag Bot (JIRA)" <ji...@apache.org> on 2013/03/22 17:31:20 UTC
[jira] [Commented] (LUCENE-3842) Analyzing Suggester
[ https://issues.apache.org/jira/browse/LUCENE-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610728#comment-13610728 ]
Commit Tag Bot commented on LUCENE-3842:
----------------------------------------
[branch_4x commit] Michael McCandless
http://svn.apache.org/viewvc?view=revision&revision=1391704
LUCENE-3842: refactor: don't make spooky State methods public
> Analyzing Suggester
> -------------------
>
> Key: LUCENE-3842
> URL: https://issues.apache.org/jira/browse/LUCENE-3842
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/spellchecker
> Affects Versions: 3.6, 4.0-ALPHA
> Reporter: Robert Muir
> Assignee: Michael McCandless
> Fix For: 4.1, 5.0
>
> Attachments: LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842-TokenStream_to_Automaton.patch
>
>
> Since we added shortest-path wFSA search in LUCENE-3714, and generified the comparator in LUCENE-3801,
> I think we should look at implementing suggesters that have more capabilities than just basic prefix matching.
> In particular I think the most flexible approach is to integrate with Analyzer at both build and query time,
> such that we build a wFST with:
> input: analyzed text such as ghost0christmas0past <-- byte 0 here is an optional token separator
> output: surface form such as "the ghost of christmas past"
> weight: the weight of the suggestion
> we make an FST with PairOutputs<weight,output>, but only do the shortest path operation on the weight side (like
> the test in LUCENE-3801), at the same time accumulating the output (surface form), which will be the actual suggestion.
> This allows a lot of flexibility:
> * Using even standardanalyzer means you can offer suggestions that ignore stopwords, e.g. if you type in "ghost of chr...",
> it will suggest "the ghost of christmas past"
> * we can add support for synonyms/wdf/etc at both index and query time (there are tradeoffs here, and this is not implemented!)
> * this is a basis for more complicated suggesters such as Japanese suggesters, where the analyzed form is in fact the reading,
> so we would add a TokenFilter that copies ReadingAttribute into term text to support that...
> * other general things like offering suggestions that are more "fuzzy" like using a plural stemmer or ignoring accents or whatever.
> According to my benchmarks, suggestions are still very fast with the prototype (e.g. ~ 100,000 QPS), and the FST size does not
> explode (its short of twice that of a regular wFST, but this is still far smaller than TST or JaSpell, etc).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: [jira] [Commented] (LUCENE-3842) Analyzing Suggester
Posted by Uwe Schindler <uw...@thetaphi.de>.
What is going on here? Those are very old issues and very old commits!
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Commit Tag Bot (JIRA) [mailto:jira@apache.org]
> Sent: Friday, March 22, 2013 5:31 PM
> To: dev@lucene.apache.org
> Subject: [jira] [Commented] (LUCENE-3842) Analyzing Suggester
>
>
> [ https://issues.apache.org/jira/browse/LUCENE-
> 3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=13610728#comment-13610728 ]
>
> Commit Tag Bot commented on LUCENE-3842:
> ----------------------------------------
>
> [branch_4x commit] Michael McCandless
> http://svn.apache.org/viewvc?view=revision&revision=1391704
>
> LUCENE-3842: refactor: don't make spooky State methods public
>
>
> > Analyzing Suggester
> > -------------------
> >
> > Key: LUCENE-3842
> > URL: https://issues.apache.org/jira/browse/LUCENE-3842
> > Project: Lucene - Core
> > Issue Type: New Feature
> > Components: modules/spellchecker
> > Affects Versions: 3.6, 4.0-ALPHA
> > Reporter: Robert Muir
> > Assignee: Michael McCandless
> > Fix For: 4.1, 5.0
> >
> > Attachments: LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842.patch, LUCENE-3842.patch,
> > LUCENE-3842.patch, LUCENE-3842-TokenStream_to_Automaton.patch
> >
> >
> > Since we added shortest-path wFSA search in LUCENE-3714, and
> > generified the comparator in LUCENE-3801, I think we should look at
> implementing suggesters that have more capabilities than just basic prefix
> matching.
> > In particular I think the most flexible approach is to integrate with
> > Analyzer at both build and query time, such that we build a wFST with:
> > input: analyzed text such as ghost0christmas0past <-- byte 0 here is
> > an optional token separator
> > output: surface form such as "the ghost of christmas past"
> > weight: the weight of the suggestion
> > we make an FST with PairOutputs<weight,output>, but only do the
> > shortest path operation on the weight side (like the test in LUCENE-3801),
> at the same time accumulating the output (surface form), which will be the
> actual suggestion.
> > This allows a lot of flexibility:
> > * Using even standardanalyzer means you can offer suggestions that
> ignore stopwords, e.g. if you type in "ghost of chr...",
> > it will suggest "the ghost of christmas past"
> > * we can add support for synonyms/wdf/etc at both index and query time
> > (there are tradeoffs here, and this is not implemented!)
> > * this is a basis for more complicated suggesters such as Japanese
> suggesters, where the analyzed form is in fact the reading,
> > so we would add a TokenFilter that copies ReadingAttribute into term text
> to support that...
> > * other general things like offering suggestions that are more "fuzzy" like
> using a plural stemmer or ignoring accents or whatever.
> > According to my benchmarks, suggestions are still very fast with the
> > prototype (e.g. ~ 100,000 QPS), and the FST size does not explode (its short
> of twice that of a regular wFST, but this is still far smaller than TST or JaSpell,
> etc).
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
> commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org