[
https://issues.apache.org/jira/browse/BEAM-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994217#comment-15994217
]
Kenneth Knowles edited comment on BEAM-828 at 5/3/17 3:21 AM:
--------------------------------------------------------------
Actually [~vikasrk] is already in progress just using
{{ProcessContext.getPipelineOptions()}} directly, which was an alternative I
simply missed.
The move to {{ValueProvider}} has only to do with making new transforms unable
to do the wrong thing, which is also important.
But we could conceivably still close on BEAM-885 (making them unavailable off
the pipeline) without succeeding at BEAM-818 (setting up the value provider
thing) by just porting transforms to use the one in the process context, which
is nice.
was (Author: kenn):
Actually [~vikasrk] is already in progress just using
{{ProcessContext.getPipelineOptions()}} directly, which was an alternative I
simply missed.
The move to {{ValueProvider}} has only to do with making new transforms unable
to do the wrong thing, which is also important.
But we could conceivably still close on BEAM-885 without succeeding at
BEAM-818, which is nice.
> Remove PipelineOptions from construction time in BigQueryIO
> -----------------------------------------------------------
>
> Key: BEAM-828
> URL: https://issues.apache.org/jira/browse/BEAM-828
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Reporter: Thomas Groh
> Assignee: Vikas Kedigehalli
> Labels: backward-incompatible
> Fix For: First stable release
>
>
> BigQueryIO uses PipelineOptions to configure itself at construction time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
