Adds optional "slop" to "pf2", "pf3" and "pf" parameters 
---------------------------------------------------------

                 Key: SOLR-2058
                 URL: https://issues.apache.org/jira/browse/SOLR-2058
             Project: Solr
          Issue Type: Improvement
          Components: SearchComponents - other
    Affects Versions: 3.1, 4.0
         Environment: n/a
            Reporter: Ron Mayer
            Priority: Minor


http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201008.mbox/%[email protected]%3e
{quote}
From    Ron Mayer <[email protected]>
 my results might
 be even better if I had a couple different "pf2"s with different "ps"'s
 at the same time.

 In particular.   One with ps=0 to put a high boost on ones the have
 the right ordering of words.  For example insuring that:
  "red hat black jacket"
 boosts only red hats and not black hats.

 And another pf2 with a more modest boost with ps=5 or so to handle
 the query above also boosting docs with "red baseball hat".
{quote}

[http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201008.mbox/%[email protected]%3e]
{quote}
From    Yonik Seeley <[email protected]>

Perhaps fold it into the pf/pf2 syntax?

pf=text^2    // current syntax... makes phrases with a boost of 2
pf=text~1^2  // proposed syntax... makes phrases with a slop of 1 and
a boost of 2

That actually seems pretty natural given the lucene query syntax - an
actual boosted sloppy phrase query already looks like
text:"foo bar"~1^2

-Yonik
http
{quote}

[http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201008.mbox/%[email protected]%3e]
{quote}
From    Chris Hostetter <[email protected]>

Big +1 to this idea ... the existing "ps" param can stick arround as the 
default for any field that doesn't specify it's own slop in the pf/pf2/pf3 
fields using the "~" syntax.

-Hoss
{quote}

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


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

Reply via email to