[jira] [Updated] (LUCENE-5149) CommonTermsQuery should allow minNrShouldMatch for high low freq terms
[ https://issues.apache.org/jira/browse/LUCENE-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer updated LUCENE-5149: Component/s: modules/other Affects Version/s: 4.4 Fix Version/s: 4.5 5.0 Assignee: Simon Willnauer CommonTermsQuery should allow minNrShouldMatch for high low freq terms Key: LUCENE-5149 URL: https://issues.apache.org/jira/browse/LUCENE-5149 Project: Lucene - Core Issue Type: Improvement Components: modules/other Affects Versions: 4.4 Reporter: Simon Willnauer Assignee: Simon Willnauer Priority: Minor Fix For: 5.0, 4.5 Currently CommonTermsQuery only allows a minShouldMatch for the low frequent query. Yet, we should also allow this for the high frequent part to have better control over scoring. here is an ES issue that is related to this: https://github.com/elasticsearch/elasticsearch/issues/3188 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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
[jira] [Updated] (LUCENE-5149) CommonTermsQuery should allow minNrShouldMatch for high low freq terms
[ https://issues.apache.org/jira/browse/LUCENE-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer updated LUCENE-5149: Attachment: LUCENE-5149.patch here is a patch CommonTermsQuery should allow minNrShouldMatch for high low freq terms Key: LUCENE-5149 URL: https://issues.apache.org/jira/browse/LUCENE-5149 Project: Lucene - Core Issue Type: Improvement Components: modules/other Affects Versions: 4.4 Reporter: Simon Willnauer Assignee: Simon Willnauer Priority: Minor Fix For: 5.0, 4.5 Attachments: LUCENE-5149.patch Currently CommonTermsQuery only allows a minShouldMatch for the low frequent query. Yet, we should also allow this for the high frequent part to have better control over scoring. here is an ES issue that is related to this: https://github.com/elasticsearch/elasticsearch/issues/3188 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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