[ 
https://issues.apache.org/jira/browse/BEAM-4069?focusedWorklogId=92192&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-92192
 ]

ASF GitHub Bot logged work on BEAM-4069:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Apr/18 18:02
            Start Date: 18/Apr/18 18:02
    Worklog Time Spent: 10m 
      Work Description: tgroh commented on issue #5126: [BEAM-4069] Gracefully 
deserialize empty options structs
URL: https://github.com/apache/beam/pull/5126#issuecomment-382476425
 
 
   Cool LGTM

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 92192)
    Time Spent: 1h 10m  (was: 1h)

> Empty pipeline options can be gracefully serialized/deserialized
> ----------------------------------------------------------------
>
>                 Key: BEAM-4069
>                 URL: https://issues.apache.org/jira/browse/BEAM-4069
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Ben Sidhom
>            Assignee: Ben Sidhom
>            Priority: Minor
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> PipelineOptionsTranslation.fromProto currently crashes with a 
> NullPointerException when passed an empty options Struct. This is due to 
> ProxyInvocationHandler.Deserializer expecting a non-empty enclosing Struct.
> Empty pipeline options may be passed by SDKs interacting with a job server, 
> so this case needs to be handled. Note that testing a round-trip of an 
> effectively-empty Java PipelineOptions object is not sufficient to catch this 
> because "empty" Java options still contain default fields not defined in 
> other SDKs.



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

Reply via email to