[jira] [Resolved] (LUCENE-5251) New Dictionary Implementation for Suggester consumption

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (LUCENE-5251) New Dictionary Implementation for Suggester consumption

Sebastian Nagel (Jira)

     [ https://issues.apache.org/jira/browse/LUCENE-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-5251.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.6
                   5.0

Thanks Areek, I just committed this!

I just had to fix one assert in testWithDeletions; it didn't hold up under beasting.

And fixed up a few things on backporting to 4.x ...

> New Dictionary Implementation for Suggester consumption
> -------------------------------------------------------
>
>                 Key: LUCENE-5251
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5251
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/search
>            Reporter: Areek Zillur
>             Fix For: 5.0, 4.6
>
>         Attachments: LUCENE-5251.patch, LUCENE-5251.patch, LUCENE-5251.patch, LUCENE-5251.patch
>
>
> With the vast array of new suggester, It would be nice to have a dictionary implementation that could feed the suggesters terms, weights and (optionally) payloads from the lucene index.
> The idea of this dictionary implementation is to grab stored documents from the index and use user-configured fields for terms, weights and payloads.
> use-case: If you have a document with three fields
>    - product_id
>    - product_name
>    - product_popularity_score
> then using this implementation would enable you to have a suggester for product_name using the weight of product_popularity_score and return you the payload of product_id, with which you can do further processing on (example: construct a url etc).  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]