[
https://issues.apache.org/jira/browse/BEAM-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121979#comment-17121979
]
Kenneth Knowles commented on BEAM-7686:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Pablo Estrada
> Priority: P2
> Labels: stale-assigned
>
> 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)
