[
https://issues.apache.org/jira/browse/SOLR-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012039#comment-14012039
]
Ron Mayer commented on SOLR-6062:
---------------------------------
Regarding "the original/linked issue allowed the same field to be passed
through a pf parameter with differing slop values. The intent being that those
scores would be combined, rather than the max being used across those fields".
The observation that lead to using the same field with different slop values
was that if: either many of the words in searched clauses were in the same
paragraph ( a pretty large slop value); or many pairs of words from search
clauses were in the same adjectives/noun clauses of the text (quite small small
slop value; to make a search for 'old hairy cat' rank well against 'hairy old
cat' ) a document was likely to be interesting.
If I understand right, it sounds to me like what Michael described continue to
be good for those cases. I'm traveling this week, but have some test cases
comparing ranking of solr-2058 vs human-sorted documents that I can run when
I'm back thursday of next week.
> Phrase queries are 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
> Attachments: combined-phrased-dismax.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
