You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:15 UTC
[jira] [Updated] (BEAM-7686) Erroneous Beam Deprecation warnings
are confusing Bigquery IO users.
[ https://issues.apache.org/jira/browse/BEAM-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-7686:
--------------------------------
Labels: stale-P2 (was: )
> Erroneous Beam Deprecation warnings are confusing Bigquery IO users.
> --------------------------------------------------------------------
>
> Key: BEAM-7686
> URL: https://issues.apache.org/jira/browse/BEAM-7686
> Project: Beam
> Issue Type: Improvement
> Components: io-py-gcp
> Reporter: Valentyn Tymofieiev
> Priority: P2
> Labels: stale-P2
>
> Bigquery sink is marked deprecated: https://github.com/apache/beam/blob/32e2e3e910619d400568073dde0d7b36698a416a/sdks/python/apache_beam/io/gcp/bigquery.py#L499, however it is used by Dataflow runner in codepath that processes WriteToBigQuery https://github.com/apache/beam/blob/32e2e3e910619d400568073dde0d7b36698a416a/sdks/python/apache_beam/runners/dataflow/dataflow_runner.py#L680.
> This generates a warning message for all BQ users, including those who use WriteToBigQuery: "Warning: BigQuerySink is deprecated since 2.11.0. Use WriteToBigQuery instead".
> This message is a red herring and confuses BQ users.
> One possibility to address this is to make BigQuerySink an alias for _BigQuerySink, and use _BigQuerySink internally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)