[SOLR-10653] After Upgrade from 5.3.1 to 6.4.2, Solr is storing certain fields like UUID, BigDecimal, Enums as <object type >:<value>

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.4.2
• Fix Version/s: 9.5
• Component/s: update
• Assignee: Mikhail Khludnev
• Reporter: Sudharshan Krishnamurthy
• Created: 09/May/17 18:09
• Updated: 12/Feb/24 19:48
• Resolved: 25/Nov/23 20:22

Description

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.

Issue Links

• duplicates: SOLR-5514 atomic update throws exception if the schema contains uuid fields: Invalid UUID String: 'java.util.UUID:e26c4d56-e98d-41de-9b7f-f63192089670'
• links to: GitHub Pull Request #2078
• links to: GitHub Pull Request #2096
• links to: json non-cloud request fails