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

Sat, 02 Dec 2023 14:50:06 -0800


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

Mikhail Khludnev commented on SOLR-10653:
-----------------------------------------

[^non-cloud-json-request-reproducer.patch] draft reproducer 
up to 9.4 it fails on non-cloud json request on vals like 
"uuid":1f9b1f5d-a23a-4a6d-a113-4cf0f230f741,'
I don't think it's worth to commit anything on that. 
discussion: https://lists.apache.org/thread/p8lcwv6lh4yn7g8yyhfvcgc9hrw9ppvq

> 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
>          Components: update
>    Affects Versions: 6.4.2
>            Reporter: Sudharshan Krishnamurthy
>            Assignee: Mikhail Khludnev
>            Priority: Major
>             Fix For: 9.5
>
>         Attachments: SOLR-10653-enums-fine.patch, 
> non-cloud-json-request-reproducer.patch
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to