[
https://issues.apache.org/jira/browse/SOLR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098209#comment-15098209
]
Demian Katz commented on SOLR-2798:
-----------------------------------
Thanks again for the pointers!
The full test suite completed overnight, and I don't appear to have broken any
existing tests. I believe the solution really is as simple as it looks.
I've added deprecations (and some missing javadoc) here:
https://github.com/demiankatz/lucene-solr/commit/107f6224aa33edea08a961adcb2e57b2cc96e69e
I've added a test to QueryEqualityTest which fails on trunk but passes in my
branch here, based on your bf example in the ticket:
https://github.com/demiankatz/lucene-solr/commit/ed544b6d726e4e79319cfb5808cc3fdfde6e0f26
I'm feeling pretty good about this -- should I open a pull request, or is there
anything more you would like me to do first?
> Local Param parsing does not support multivalued params
> -------------------------------------------------------
>
> Key: SOLR-2798
> URL: https://issues.apache.org/jira/browse/SOLR-2798
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Anshum Gupta
>
> As noted by Demian on the solr-user mailing list, Local Param parsing seems
> to use a "last one wins" approach when parsing multivalued params.
> In this example, the value of "111" is completely ignored:
> {code}
> http://localhost:8983/solr/select?debug=query&q={!dismax%20bq=111%20bq=222}foo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
