[ https://issues.apache.org/jira/browse/SOLR-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280180#comment-13280180 ]
James Dyer edited comment on SOLR-2058 at 5/21/12 2:38 PM: ----------------------------------------------------------- Jan, I'm curious: is the patch you're working on more of a "clean-up" of Jack's patch, or does it do something Jack's patch didn't do? I've been testing this and so far while it issues the dismax queries I'd expect, it doesn't help relevance like I though it would. so I'm a little less confident about it. I also was wondering if it should be generalized to allow "pf[\d]" so users can have pf4, pf5 etc if they wanted. This extra functionality wouldn't be hard to add but would it make sense? In any case, I would like to have something to commit here this week if possible. Your insight is very much appreciated. was (Author: jdyer): Jan, I'm curious: is the patch you're working on more of a "clean-up" of Jack's patch, or does it do something Jack's patch didn't do? I've been testing this and so far while it issues the dismax queries I'd expect, it doesn't help do relevance like I though it would. so I'm a little less confident about it. I also was wondering if it should be generalized to allow "ps[\d]" so users can have ps4, ps5 etc if they wanted. This extra functionality wouldn't be hard to add but would it make sense? In any case, I would like to have something to commit here this week if possible. Your insight is very much appreciated. > Adds optional "phrase slop" to edismax "pf2", "pf3" and "pf" parameters with > field~slop^boost syntax > ---------------------------------------------------------------------------------------------------- > > Key: SOLR-2058 > URL: https://issues.apache.org/jira/browse/SOLR-2058 > Project: Solr > Issue Type: Improvement > Components: query parsers > Environment: n/a > Reporter: Ron Mayer > Priority: Minor > Fix For: 4.0 > > Attachments: SOLR-2058.patch, edismax_pf_with_slop_v2.1.patch, > edismax_pf_with_slop_v2.patch, pf2_with_slop.patch > > > http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201008.mbox/%3c4c659119.2010...@0ape.com%3E > {quote} > From Ron Mayer <r...@0ape.com> > ... 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 [the query]: > "red hat black jacket" > boosts only documents with "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/%3caanlktimd+v3g6d_mnhp+jykkd+dej8fvmvf_1lqoi...@mail.gmail.com%3E] > {quote} > From Yonik Seeley <yo...@lucidimagination.com> > 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 > {quote} > [http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201008.mbox/%3calpine.deb.1.10.1008161300510.6...@radix.cryptio.net%3E] > {quote} > From Chris Hostetter <hossman_luc...@fucit.org> > 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org