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
All cross lang transformations that are implemented in java that have a python wrapper that use the old ExternalTransform API such as KafkaIO are forced to have int64 properties since the translation layer converts a python int to int64. So if an int32 property is added to the java transform, unless the python wrapper specifies an np.int32 (which is clunky since it needlessly adds an np dependency), the python pipeline will error.
What would you like to happen?
All cross lang transformations that are implemented in java that have a python wrapper that use the old ExternalTransform API such as KafkaIO are forced to have int64 properties since the translation layer converts a python int to int64. So if an int32 property is added to the java transform, unless the python wrapper specifies an np.int32 (which is clunky since it needlessly adds an np dependency), the python pipeline will error.
Issue comes from this file:
beam/sdks/python/apache_beam/typehints/schemas.py
Line 4 in 0f2e196
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components
The text was updated successfully, but these errors were encountered: