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

Robert Muir commented on LUCENE-3130:
-------------------------------------

{quote}
But for the synonym case, what remains is to modify the QueryParser to act on 
the already-present TypeAttribute, is that so? If so, let's open another issue 
for that.
{quote}

I think so? Though it might be more useful not to modify the core queryparser 
for this? The reason is that such a feature is geared towards synonyms and 
multi-word synonyms don't work well with it... So maybe instead to a simpler 
queryparser that *does* work well with multi-word synonyms by default?

> Use BoostAttribute in in TokenFilters to denote Terms that QueryParser should 
> give lower boosts
> -----------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3130
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3130
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Hoss Man
>
> A recent thread asked if there was anyway to use QueryTime synonyms such that 
> matches on the original term specified by the user would score higher then 
> matches on the synonym.  It occurred to me later that a float Attribute could 
> be set by the SynonymFilter in such situations, and QueryParser could use 
> that float as a boost in the resulting Query.  IThis would be fairly 
> straightforward for the simple "synonyms => BooleamQuery" case, but we'd have 
> to decide how to handle the case of synonyms with multiple terms that produce 
> MTPQ, possibly just punt for now)
> Likewise, there may be other TokenFilters that "inject" artificial tokens at 
> query time where it also might make sense to have a reduced "boost" factor...
> * SynonymFilter
> * CommonGramsFilter
> * WordDelimiterFilter
> * etc...
> In all of these cases, the amount of the "boost" could me configured, and for 
> back compact could default to "1.0" (or null to not set a boost at all)
> Furthermore: if we add a new BoostAttrToPayloadAttrFilter that just copied 
> the boost attribute into the payload attribute, these same filters could give 
> "penalizing" payloads to terms when used at index time) could give 
> "penalizing" payloads to terms.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to