You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the initial python RowCoder implementation we only added support for the data types that already had coders in the Python SDK. We should add support for the remaining data types that are not currently supported:
INT8 (ByteCoder in Java)
INT16 (BigEndianShortCoder in Java)
FLOAT (FloatCoder in Java) (Note: doubles are supported, this is specifically for single-precision)
BOOLEAN (standard beam:coder:bool:v1, BooleanCoder in Java)
BYTES (standard beam:coder:bytes:v1, ByteArrayCoder in Java)
Map (MapCoder in Java)
We might consider making those coders standard so they can be tested independently from RowCoder in standard_coders.yaml. Or, if we don't do that we should probably add a more robust testing framework for RowCoder itself, because it will be challenging to test all of these types as part of the RowCoder tests in standard_coders.yaml.
Imported from Jira BEAM-7996. Original Jira may contain additional context.
Reported by: bhulette.
The text was updated successfully, but these errors were encountered:
In the initial python RowCoder implementation we only added support for the data types that already had coders in the Python SDK. We should add support for the remaining data types that are not currently supported:
BOOLEAN (standard beam:coder:bool:v1, BooleanCoder in Java)BYTES (standard beam:coder:bytes:v1, ByteArrayCoder in Java)Map (MapCoder in Java)We might consider making those coders standard so they can be tested independently from RowCoder in standard_coders.yaml. Or, if we don't do that we should probably add a more robust testing framework for RowCoder itself, because it will be challenging to test all of these types as part of the RowCoder tests in standard_coders.yaml.
Imported from Jira BEAM-7996. Original Jira may contain additional context.
Reported by: bhulette.
The text was updated successfully, but these errors were encountered: