[
https://issues.apache.org/jira/browse/SOLR-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751269#comment-13751269
]
Sandro Mario Zbinden commented on SOLR-4021:
--------------------------------------------
Hey Dave
Thank you very much for the tip. The problem was exactly what you described. We
were running a DataImport and in the same time we did an update with solrj
(solserver.add(inputdocuments). We will implement a lock feature now that
synchronized the calls between DataImport and the Update.
> JavaBinCodec has poor default behavior for unrecognized classes of objects
> --------------------------------------------------------------------------
>
> Key: SOLR-4021
> URL: https://issues.apache.org/jira/browse/SOLR-4021
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 4.0
> Reporter: Hoss Man
>
> It seems that JavaBinCodec has inconsistent serialize/deserialize behavior
> when dealing with objects of classes that it doesn't recognized. In
> particular, unrecnognized objects seem to be serialized with the full
> classname prepented to the "toString()" value, and then that resulting
> concatentated string is left as is during deserialization.
> as a concrete example: serializing & deserializing a BigDecimal value results
> in a final value like "java.math.BigDecimal:1848.66" even though for most
> users the simple toString() value would have worked as intended.
--
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: [email protected]
For additional commands, e-mail: [email protected]
