[ 
https://issues.apache.org/jira/browse/SOLR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jörg Maier resolved SOLR-3144.
------------------------------

    Resolution: Duplicate

Hi Sami,

i was working on an earlier build than the current head. Obviously previous to 
your fix. I couldnt verify the existence of this bug on trunk anymore and 
everything works fine for me. I missed SOLR-3037.

However it might be a good idea to replace the toNamedList method in the Codec 
by the toNamedList method from SolrParams.

I close this as duplicate to SOLR-3037.

                
> Parameter marshalling is broken in Solrj JavaBinUpdateRequestCodec 
> -------------------------------------------------------------------
>
>                 Key: SOLR-3144
>                 URL: https://issues.apache.org/jira/browse/SOLR-3144
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 4.0
>            Reporter: Jörg Maier
>             Fix For: 4.0
>
>         Attachments: JavaBinUpdateRequestCodec.patch
>
>
> The parameter marshalling de-marshalling is broken in Solrj's 
> JavaBinUpdateRequestCodec. 
> The bug can be reproduced by adding a parameter e.g. overwrite=false as 
> parameter to the UpdateRequest. After desiarilizing on the backend side the 
> value will be not "false" it will be "[false]" which results in an Exception 
> in the backend and documents will not be imported.
> This issue can easily be fixed by replacing the serialization method with the 
> correct one in SolrParams. See also this gist for a working version: 
> https://gist.github.com/1853544

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to