[
https://issues.apache.org/jira/browse/BEAM-8023?focusedWorklogId=299767&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-299767
]
ASF GitHub Bot logged work on BEAM-8023:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Aug/19 21:07
Start Date: 22/Aug/19 21:07
Worklog Time Spent: 10m
Work Description: kmjung commented on issue #9405: [BEAM-8023] Add value
provider interfaces for BigQueryIO.Read using Method.DIRECT_READ
URL: https://github.com/apache/beam/pull/9405#issuecomment-524078069
@chamikaramj I think this is ready to go -- please take another look when
you can.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 299767)
Time Spent: 2h 10m (was: 2h)
> Allow specifying BigQuery Storage API readOptions at runtime
> ------------------------------------------------------------
>
> Key: BEAM-8023
> URL: https://issues.apache.org/jira/browse/BEAM-8023
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Jeff Klukas
> Assignee: Kenneth Jung
> Priority: Minor
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> We have support in the Java SDK for using the BigQuery Storage API for reads,
> but only the target query or table is supported as a ValueProvider to be
> specified at runtime. AFAICT, there is no reason we can't delay specifying
> readOptions until runtime as well.
> The readOptions are accessed by BigQueryStorageTableSource in getTargetTable;
> I believe that's occurring at runtime, but I'd love for someone with deeper
> BoundedSource knowledge to confirm that.
> I'd advocate for adding new methods
> `TypedRead.withSelectedFields(ValueProvider<List<String>> value)` and
> `TypedRead.withRowRestriction(ValueProvider<String> value)`. The existing
> `withReadOptions` method would then populate the other two as
> StaticValueProviders. Perhaps we'd want to deprecate `withReadOptions` in
> favor or specifying individual read options as separate parameters.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
