The detailed declaration of both UUID and String as target conversion types in IdentifierToPrimitivesConverter.getConvertibleTypes() causes problems in Spring Data's CustomConversions as it uses the pairs here to allow clients to detect the target type that will ultimately be handed into the convert(…) method.
This causes issues if the UUID type is returned first, as Identifiers using a sole String will try to be erroneously coerced into a UUID as reported here. Using String as the first value will always cause UUIDs to be rendered as String, even though a store might be able to persist UUIDs directly.
We should rather only return new ConvertiblePair(Identifier.class, Object.class) to delay the decision of which type to use to the actual conversion step.
The detailed declaration of both
UUIDandStringas target conversion types inIdentifierToPrimitivesConverter.getConvertibleTypes()causes problems in Spring Data'sCustomConversionsas it uses the pairs here to allow clients to detect the target type that will ultimately be handed into theconvert(…)method.This causes issues if the
UUIDtype is returned first, asIdentifiers using a soleStringwill try to be erroneously coerced into a UUID as reported here. UsingStringas the first value will always causeUUIDs to be rendered asString, even though a store might be able to persistUUIDs directly.We should rather only return
new ConvertiblePair(Identifier.class, Object.class)to delay the decision of which type to use to the actual conversion step.Related tickets