[Java] Deserialization optimization, instead of discarding fields, puts non-existent fields into a specified field.

[DemonJun]

Is your feature request related to a problem? Please describe.

When the upstream and downstream attributes are inconsistent, for example, the upstream is 10 fields, the downstream is not synchronized to update the field attributes, and there are only 9 attributes, then the downstream non-existent attributes will be ignored during deserialization.

Describe the solution you'd like

In some scenarios, we don't want the attribute to be lost, so can we put the attribute into a specified field, such as the other field (a map collection)?