[
https://issues.apache.org/jira/browse/BEAM-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184406#comment-17184406
]
Beam JIRA Bot commented on BEAM-7686:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> 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: P3
>
> 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)
