You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael Dodsworth (JIRA)" <ji...@apache.org> on 2014/05/13 07:44:14 UTC

[jira] [Created] (SOLR-6062) a phrase query is created for each field supplied through edismax's pf, pf2 and pf3 parameters (rather them being combined in a single dismax query)

Michael Dodsworth created SOLR-6062:
---------------------------------------

             Summary: a phrase query is created for each field supplied through edismax's pf, pf2 and pf3 parameters (rather them being combined in a single dismax query)
                 Key: SOLR-6062
                 URL: https://issues.apache.org/jira/browse/SOLR-6062
             Project: Solr
          Issue Type: Bug
          Components: query parsers
    Affects Versions: 4.0
            Reporter: Michael Dodsworth
            Priority: Minor


https://issues.apache.org/jira/browse/SOLR-2058 subtly changed how phrase queries, created through the pf, pf2 and pf3 parameters, are merged into the main user query.

For the query: 'term1 term2' with pf2:[field1, field2, field3] we now get (omitting the non phrase query section for clarity):

{code:java}
<main query>
DisjunctionMaxQuery((field1:"term1 term2"^1.0)~0.1)
DisjunctionMaxQuery((field2:"term1 term2"^1.0)~0.1)
DisjunctionMaxQuery((field3:"term1 term2"^1.0)~0.1)
{code}

Prior to this change, we had:

{code:java}
<main query> 
DisjunctionMaxQuery((field1:"term1 term2"^1.0 | field2:"term1 term2"^1.0 | field3:"term1 term2"^1.0)~0.1)
{code}

The upshot being that if the phrase query "term1 term2" appears in multiple fields, it will get a significant boost over the previous implementation.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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