If I remember correctly, this was related to change of the signature of run on runners to run(pipeline, options) instead of just run(pipeline). A runner accepts a pipeline and set of options to run that pipeline, instead of a pipeline and options being a combined thing.
It would be good to update the comments or bug with some explanation. On Fri, Sep 21, 2018 at 2:20 PM, Sindy Li <qiny...@google.com> wrote: > I think it's just deprecating referencing the option as > pipeline.options > , because it is made into a private variable, but we can still do > pipeline.options() > > On Fri, Sep 21, 2018 at 2:11 PM Udi Meiri <eh...@google.com> wrote: > >> Hey, does anybody know why the pipeline.options property was deprecated? >> I found this bug: https://issues.apache.org/jira/browse/BEAM-2124 >> but there's no explanation. >> >
