You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Jamie Lennox (JIRA)" <ji...@apache.org> on 2018/11/24 22:56:00 UTC

[jira] [Created] (BEAM-6121) Serialization issue with non-bool 'streaming' value

Jamie Lennox created BEAM-6121:
----------------------------------

             Summary: Serialization issue with non-bool 'streaming' value
                 Key: BEAM-6121
                 URL: https://issues.apache.org/jira/browse/BEAM-6121
             Project: Beam
          Issue Type: Bug
          Components: runner-dataflow, sdk-py-harness
    Affects Versions: 2.8.0
            Reporter: Jamie Lennox
            Assignee: Tyler Akidau


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)