[BEAM-2959] Fix proto enums to not use 0 for a valid value

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Component/s: beam-model
• Assignee: Luke Cwik
• Reporter: Luke Cwik
• Created: 15/Sep/17 18:16
• Updated: 16/May/20 13:46
• Resolved: 27/Sep/17 19:34

Description

Proto3 uses 0 as the default value for enums and does not encode it on the wire which means that you can not detect the difference between a value that is unset and an enum that is set but has a value of zero.

Defining an "YYY_UNSPECIFIED" is considered a best practice. Unfortunately this is not done automatically because of proto2 compatibility within proto3.

Issue Links

• links to: GitHub Pull Request #3856
• links to: GitHub Pull Request #3904
• links to: GitHub Pull Request #3913