[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976652#comment-15976652 ] ASF subversion and git services commented on SOLR-10527: Commit dfc0dd67f7fe45fbf62d88652952ec3e2b3e0070 in lucene-solr's branch refs/heads/branch_6_5 from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dfc0dd6 ] SOLR-10527: remove unused import > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe >Assignee: Steve Rowe > Fix For: 6.5.1, 6.6, master (7.0) > > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975772#comment-15975772 ] ASF subversion and git services commented on SOLR-10527: Commit f577562a647c26af28110c168d8d62d8c2a2fa34 in lucene-solr's branch refs/heads/branch_6x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f577562 ] SOLR-10527: move CHANGES entry to 6.5.1 section > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe > Fix For: 6.6, master (7.0) > > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975773#comment-15975773 ] ASF subversion and git services commented on SOLR-10527: Commit ffe61ff2ad82c355577ea827067dc7196a5e2ca0 in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ffe61ff ] SOLR-10527: move CHANGES entry to 6.5.1 section > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe > Fix For: 6.6, master (7.0) > > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975769#comment-15975769 ] ASF subversion and git services commented on SOLR-10527: Commit e126498cef019f573c13ba7fa3539abcddce in lucene-solr's branch refs/heads/branch_6_5 from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e126498 ] SOLR-10527: edismax with sow=false fails to create dismax-per-term queries when any field is boosted Conflicts: solr/CHANGES.txt solr/core/src/test/org/apache/solr/search/TestExtendedDismaxParser.java > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe > Fix For: 6.6, master (7.0) > > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975714#comment-15975714 ] ASF subversion and git services commented on SOLR-10527: Commit 8b27b82babed40e72eceaec0765d448247a7d322 in lucene-solr's branch refs/heads/master from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8b27b82 ] SOLR-10527: edismax with sow=false fails to create dismax-per-term queries when any field is boosted > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10527) edismax with sow=false fails to create dismax-per-term queries when any field is boosted
[ https://issues.apache.org/jira/browse/SOLR-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975713#comment-15975713 ] ASF subversion and git services commented on SOLR-10527: Commit 141961b00a062422b078b327ba334978ad97604e in lucene-solr's branch refs/heads/branch_6x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=141961b ] SOLR-10527: edismax with sow=false fails to create dismax-per-term queries when any field is boosted > edismax with sow=false fails to create dismax-per-term queries when any field > is boosted > > > Key: SOLR-10527 > URL: https://issues.apache.org/jira/browse/SOLR-10527 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Steve Rowe > Attachments: SOLR-10527.patch > > > When {{sow=false}}, the edismax query parser creates dismax-per-field queries > when field analysis is different enough that query structures differ per > field (stopwords in one field only, e.g.). (By contrast, dismax-per-*term* > queries are produced when {{sow=true}} or when query structures are the same > across all fields.) > However, the code to determine whether per-field query structures differed > wasn't aware of boost queries. As a result, when {{sow=false}} and boost are > specified for at least one field (e.g. {{q=\{!edismax > sow=false\}text=fieldA^2+fieldB^4}}), dismax-per-field queries are always > produced, even when per-field query structures are equivalent. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org