[FLINK-25936] MutableTypeCell is not setting correctly the value's type_name

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Stateful Functions
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Igal Shilman
• Created: 02/Feb/22 20:48
• Updated: 03/Feb/22 09:16
• Resolved: 03/Feb/22 09:16

Description

In the remote Java SDK, when a type doesn't specify an IMMUTABLE_VALUE type characteristics, (which is the case for custom type implementations by default) the type_name field is not set correctly on the resulting TypedValue.

A MutableTypeCell was assuming incorrectly that the backend will send a TypedValue with a type_name field set even if the value is missing (TypedValue.has_value = false). This is not the case, and hence the type_name needs to be set explicitly.

Issue Links

• links to: GitHub Pull Request #297