You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/14 19:18:00 UTC
[jira] [Work logged] (BEAM-7195) BigQuery - 404 errors for 'table
not found' when using dynamic destinations - sometimes, new table fails to
get created
[ https://issues.apache.org/jira/browse/BEAM-7195?focusedWorklogId=536134&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-536134 ]
ASF GitHub Bot logged work on BEAM-7195:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/21 19:17
Start Date: 14/Jan/21 19:17
Worklog Time Spent: 10m
Work Description: aaltay commented on pull request #12968:
URL: https://github.com/apache/beam/pull/12968#issuecomment-760411638
Do we want to merge this? Should this be closed?
Or do we not want to do this because it will break updates?
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 536134)
Time Spent: 2h (was: 1h 50m)
> BigQuery - 404 errors for 'table not found' when using dynamic destinations - sometimes, new table fails to get created
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-7195
> URL: https://issues.apache.org/jira/browse/BEAM-7195
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.5.0
> Environment: Windows
> Reporter: Chris
> Priority: P1
> Time Spent: 2h
> Remaining Estimate: 0h
>
> See the following StackOverflow question, which describes the details:
>
> [https://stackoverflow.com/questions/55932291/apache-beam-for-google-cloud-dataflow-404-errors-when-using-bigqueryio-write-c]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)