[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: CollapsingQParserPlugin-6168.patch.1-1stcut CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1, 4.8.1 Reporter: Umesh Prasad Assignee: Joel Bernstein Attachments: CollapsingQParserPlugin-6168.patch.1-1stcut, SOLR-6168-group-head-inconsistent-with-sort.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.8.1 revision number 1603061 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: (was: SOLR-6168-broken-multi-sort-test-case.patch) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1, 4.8.1 Reporter: Umesh Prasad Assignee: Joel Bernstein CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.8.1 revision number 1603061 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: SOLR-6168-group-head-inconsistent-with-sort.patch Test case that demonstrates that group head picked by collapsing qparser is inconsistent with sort spec CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1, 4.8.1 Reporter: Umesh Prasad Assignee: Joel Bernstein Attachments: SOLR-6168-group-head-inconsistent-with-sort.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.8.1 revision number 1603061 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: (was: SOLR-6168-broken-sort-test-case.patch) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1 Reporter: Umesh Prasad Attachments: SOLR-6168-broken-multi-sort-test-case.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: SOLR-6168-broken-multi-sort-test-case.patch CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1 Reporter: Umesh Prasad Attachments: SOLR-6168-broken-multi-sort-test-case.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Affects Version/s: 4.8.1 CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1, 4.8.1 Reporter: Umesh Prasad Attachments: SOLR-6168-broken-multi-sort-test-case.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Description: CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.8.1 revision number 1603061 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. was: CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1, 4.8.1 Reporter: Umesh Prasad Attachments: SOLR-6168-broken-multi-sort-test-case.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.8.1 revision number 1603061 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Summary: CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used (was: CollapsingQParserPlugin ranks incorretly when 3 or more sort params are used) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1 Reporter: Umesh Prasad CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
[ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Prasad updated SOLR-6168: --- Attachment: SOLR-6168-broken-sort-test-case.patch This shows the broken sort with 3 or more params. CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used - Key: SOLR-6168 URL: https://issues.apache.org/jira/browse/SOLR-6168 Project: Solr Issue Type: Bug Affects Versions: 4.7.1 Reporter: Umesh Prasad Attachments: SOLR-6168-broken-sort-test-case.patch CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are used. I have attached a test case, which demonstrates the broken behavior when 3 sort fields are used. The failing test case patch is against Lucene/Solr 4.7 revision number 1602388 PS : SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing one to specify max/min=field-name. However that requires 2nd sort field to be a numeric field. It will not work with string field or function query sort. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
