[ 
https://issues.apache.org/jira/browse/LUCENE-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800058#comment-13800058
 ] 

Areek Zillur commented on LUCENE-5294:
--------------------------------------

Sorry for not running the "ant precommit" before uploading the patch (will do 
that from next time!). Thanks for fixing it and committing the patch.
Had a couple of questions though. 
  - Does it make sense for the new dictionary implementation to support 
CompositeReader? (I actually do not know anything about it except for the fact 
that it has multiple leaves). I was thinking whether its worth it to add 
support.
  - What are your thoughts on having a DocumentDictionary setting that will 
collect terms from documents for documents that has all the required fields and 
ignore the others (rather than erroring out)? Is that too much flexibility?

Thanks again for your quick responses!

> Suggester Dictionary implementation that takes expressions as term weights
> --------------------------------------------------------------------------
>
>                 Key: LUCENE-5294
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5294
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/search
>            Reporter: Areek Zillur
>             Fix For: 4.6, 5.0
>
>         Attachments: LUCENE-5294.patch
>
>
> It would be nice to have a Suggester Dictionary implementation that could 
> compute the weights of the terms consumed by the suggester based on an 
> user-defined expression (using lucene's expression module).
> It could be an extension of the existing DocumentDictionary (which takes 
> terms, weights and (optionally) payloads from the stored documents in the 
> index). The only exception being that instead of taking the weights for the 
> terms from the specified weight fields, it could compute the weights using an 
> user-defn expression, that uses one or more NumicDocValuesField from the 
> document.
> Example:
>   let the document have
>      - product_id
>      - product_name
>      - product_popularity
>      - product_profit
>   Then this implementation could be used with an expression of     
> "0.2*product_popularity + 0.8*product_profit" to determine the weights of the 
> terms for the corresponding documents (optionally along with a payload 
> (product_id))



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to