V3 node is unable to evolve serialised type that has introduced a property that is of an unknown type

Description

The root cause of is the introduction of a new property to StateConsumptionDetails whose type is an new enum that doesn't exist in V3.

However this is a general problem whereby any serialised type that V3 knows about cannot be evolved by V3 if a new property is introduced to it which is of a type that V3 doesn't already know about. If we are to support V3 in mixed networks then until this bug is fixed we are severely restricted in how we evolve V3-aware types.

The fix should be straightforward: https://r3-cev.atlassian.net/browse/CORDA-2307?focusedCommentId=51131&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-51131

Activity

Show:
Katelyn Baker
February 26, 2019, 5:02 PM

Assignee

Dominic.Fox@r3.com

Reporter

Shams Asari

Labels

None

Sprint

None

Epic Link

None

Priority

Medium

Severity

Critical

CVSS Score

None

CVSS Vector

None

Due Date

None

Engineering Teams

None

Fix versions

Affects versions

Ported to...

None

Story Points / Dev Days

None
Configure