You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2009/04/18 07:37:14 UTC

[jira] Commented: (SOLR-633) QParser for use with user-entered query which recognizes subphrases as well as allowing some other customizations on per field basis

    [ https://issues.apache.org/jira/browse/SOLR-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700422#action_12700422 ] 

Otis Gospodnetic commented on SOLR-633:
---------------------------------------

This description could sure use an example! :)  I read it 3 times and still don't have a good picture of what this is really about.


> QParser for use with user-entered query which recognizes subphrases as well as allowing some other customizations on per field basis
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-633
>                 URL: https://issues.apache.org/jira/browse/SOLR-633
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 1.4
>         Environment: All
>            Reporter: Preetam Rao
>            Priority: Minor
>             Fix For: 1.5
>
>
> Create a request handler (actually a QParser) for use with user entered queries with following features-
> a) Take a user query string and try to match it against multiple fields, while recognizing sub-phrase matches.
> b) For each field give the below parameters:
>    1) phraseBoost - the factor which decides how good a n token sub phrase match is compared to n-1 token sub-phrase match.
>    2) maxScoreOnly - If there are multiple sub-phrase matches pick, only the highest
>    3) ignoreDuplicates - If the same sub-phrase query matches multiple times, pick only one.
>    4) disableOtherScoreFactors - Ignore tf, query norm, idf and any other parameters which are not relevant.
> c) Try to provide all the parameters similar to dismax. Reuse or extend dismax.  
> Other suggestions and feedback appreciated :-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.