[ 
https://issues.apache.org/jira/browse/SOLR-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751087#comment-13751087
 ] 

Sandro Mario Zbinden edited comment on SOLR-4021 at 8/27/13 8:49 AM:
---------------------------------------------------------------------


I am getting the same exception. With solr 4.2.1 and using partial updates 
configured like.



{code:xml}
    <updateHandler class="solr.DirectUpdateHandler2">
        <autoCommit>
            <maxDocs>25000</maxDocs>
            <maxTime>300000</maxTime>
            <openSearcher>false</openSearcher>
        </autoCommit>
        <updateLog class="solr.FSUpdateLog">
            <str name="dir">${solr.data.dir:}</str>
        </updateLog>
    </updateHandler>
{code}

[~david_fennessey] Did you find a way to manage this issue ?
                
      was (Author: sandrozbinden):
    I am getting the same exception. With solr 4.2.1 and using partial updates 
configured like.

{code:xml}
    <updateHandler class="solr.DirectUpdateHandler2">
        <autoCommit>
            <maxDocs>25000</maxDocs>
            <maxTime>300000</maxTime>
            <openSearcher>false</openSearcher>
        </autoCommit>
        <updateLog class="solr.FSUpdateLog">
            <str name="dir">${solr.data.dir:}</str>
        </updateLog>
    </updateHandler>
{code}

[~david_fennessey] Did you find a way to manage this issue ?
                  
> 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]

Reply via email to