[
https://issues.apache.org/jira/browse/BEAM-6579?focusedWorklogId=194184&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-194184
]
ASF GitHub Bot logged work on BEAM-6579:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Feb/19 19:03
Start Date: 04/Feb/19 19:03
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #7714: [BEAM-6579] Fix
create disposition for the case of temporary tables
URL: https://github.com/apache/beam/pull/7714#issuecomment-460370262
Sadly, I don't see an easy way of unit testing this (though I've asked the
user who is experiencing this bug to test this PR). Our BigQuery fakes today do
not understand the write/create dispositions at all, and adding that to them is
a much larger change. Let me know if you see another way of unit testing this.
I'll file a JIRA to add write/create disposition testing to our BigQueryIO
tests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 194184)
Time Spent: 1h 20m (was: 1h 10m)
> BigQueryIO improperly handles triggering when temp tables are used
> -------------------------------------------------------------------
>
> Key: BEAM-6579
> URL: https://issues.apache.org/jira/browse/BEAM-6579
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.9.0
> Reporter: Reuven Lax
> Assignee: Reuven Lax
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> In WriteTables.java, the create disposition is changed to CREATE_NEVER for
> triggers after the first. This logic is correct when writing directly to the
> destination table - the table is created on the first write, and does not
> need to be recreated. However WriteTables is also used when writing to
> temporary tables, and the logic is incorrect in that case as a new table is
> created on every trigger.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
