We're updating the issue view to help you get more done. 

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

Status

Assignee

Dominic.Fox@r3.com

Reporter

Shams Asari

Labels

None

Affected OS

None

Severity

Critical

Target Version/s

None

Feature Team

Corda Core

Fix versions

Affects versions

Corda 3.3
Corda Enterprise 3.2

Priority

Medium