Possible change in object mapping behaviour regarding 'null' values

[Pascal-Oertli]

Possible change in object mapping behaviour regarding 'null' values

[christophstrobl]

Sorry for the inconvenience but this is actually the expected behaviour for fields that are present in the raw document. In the above you'd have to $unset fields.

[Pascal-Oertli]

Thank you for your quick response! I can see that this intuitively makes sense (actual data in DB has precedence over default values). But I was still wondering about the change in behaviour after SB >=v3.2.0 (SpringDataMongoDB >=4.2.0).
It seems that in older versions, 'null' values did in fact not overwrite default values.

[christophstrobl]

Right, that one should have made it into the release notes on the wiki page. The Mapping section in the documentation contains an extra note that explains the current behaviour.

[n0daft]

This change exposes us to all sorts of possible nullPointers. Is there a way we can change this behaviour for collections (see highlighted part in screenshot). A custom converter would not be the right tool, since we actually don't want to convert at all?

[christophstrobl]

@n0daft you could use Lifecycle Events to post process types after conversion.