You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:02 UTC
[jira] [Updated] (BEAM-11115) Remove _CustomBigQuerySource implementation to rely on ReadAllFromBigQuery
[ https://issues.apache.org/jira/browse/BEAM-11115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-11115:
-----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> Remove _CustomBigQuerySource implementation to rely on ReadAllFromBigQuery
> --------------------------------------------------------------------------
>
> Key: BEAM-11115
> URL: https://issues.apache.org/jira/browse/BEAM-11115
> Project: Beam
> Issue Type: Improvement
> Components: io-py-gcp
> Reporter: Pablo Estrada
> Priority: P3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> there are two implementations of ReadFromBQ. One is used for a new feature in ReadAllFromBQ - the other is used for the regular ReadFromBigQuery transform - we need to move ReadFromBQ to rely on ReadAllFromBQ under the covers.
>
> It is not possible at the moment because ReadAllFromBQ only works on portable runners. Once Python runners are all portable, we can move.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)