[jira] [Commented] (SOLR-10653) After Upgrade from 5.3.1 to 6.4.2, Solr is storing certain fields like UUID, BigDecimal, Enums as :

Tue, 06 Feb 2018 13:13:17 -0800

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

Thomas Heigl commented on SOLR-10653:
-------------------------------------

I just ran into the same issue when upgrading from Solr 4.10 to Solr 7.1. Do I 
have to change all my enum fields to String values to fix this or is there some 
kind of configuration for SolrJ?

> After Upgrade from 5.3.1 to 6.4.2, Solr is storing certain fields like UUID, 
> BigDecimal, Enums as <object type >:<value>
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10653
>                 URL: https://issues.apache.org/jira/browse/SOLR-10653
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: clients - java, SolrJ
>    Affects Versions: 6.4.2
>            Reporter: Sudharshan Krishnamurthy
>            Priority: Major
>
> Originally being in 5.3.1 when supplying object types such as java.util.UUID, 
> Enum, BigDecimal supplied to SolrInputDocument the conversion to 
> corresponding data types defined in the Solr schema happened just fine in 
> this case string, string, float respectively. After the upgrade to 6.4.2 
> version, I see that when such values are supplied to SolrInputDocument, while 
> saving it gets stored as 
> "java.util.UUID:0997e78e-6e3d-4824-8c52-8cc15533e541" with UUID for example 
> and fully qualified name of the class for Enums etc. Hence while 
> deserializing we are getting errors such as 
> Invalid UUID String: 'java.util.UUID:0997e78e-6e3d-4824-8c52-8cc15533e541'
> Although converting these fields to String before supplying to 
> SolrInputDocument or converting to varchar for delta import queries seem to 
> fix the problem. I wonder what changed between the 2 versions to have me do 
> this String or varchar conversion that was not required before.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to