[
https://issues.apache.org/jira/browse/SOLR-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudharshan Krishnamurthy updated SOLR-10653:
--------------------------------------------
Summary: After Upgrade from 5.3.1 to 6.4.2, Solr is storing certain fields
like UUID, BigDecimal, Enums as <object type >:<value> (was: After Upgrade
from 5.3.1 to 6.4.2, Solr is storing certain fields like UUID, BigDecimal and
Enums as <object type >:<value>)
> 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
>
> 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'
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
