[SOLR-4021] JavaBinCodec has poor default behavior for unrecognized classes of objects

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0
• Component/s: clients - java
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 31/Oct/12 18:11
• Updated: 22/Jun/16 05:02

Description

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.

Issue Links

• relates to: SOLR-9230 Change of default to BinaryRequestWriter breaks some use cases
• relates to: SOLR-5194 Annecdotal reports of what smells like thread safety issues with concurrent partial updates?