[GitHub] [beam] kennknowles opened a new issue, #19127: Serialization issue with non-bool 'streaming' value

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #19127:
URL: https://github.com/apache/beam/issues/19127

   Hi all,
   
   Just want to start out with that this was my own fault and I'm only reporting because it took me a while to figure out and the library could prevent it.
   
   I'm using the python 2.8.0 beam library pushing to Google dataflow.
   
   Based on the options that were presented to the application I set streaming or not like:
   
       streaming = options.topic or options.subscription
       options.view_as(StandardOptions).streaming = streaming
   
   This was working fine with the direct runner, but when i push to dataflow the container wasn't starting. In python (str or str) is a string, which works great for truth-y ness and local dev, but at some point we serialize this value and send it to dataflow which tries to deserialize this string as a boolean and the harness crashes.
   
   Anyway, my fault, however if we're serializing values that are going to be decoded by golang it'd be nice to be stricter about this on the client side as it's easy to screw up.
   
   Thanks for your help.
   
   Imported from Jira [BEAM-6121](https://issues.apache.org/jira/browse/BEAM-6121). Original Jira may contain additional context.
   Reported by: jamielennox.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org