[ https://issues.apache.org/jira/browse/BEAM-7742?focusedWorklogId=295161&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-295161 ]
ASF GitHub Bot logged work on BEAM-7742: ---------------------------------------- Author: ASF GitHub Bot Created on: 15/Aug/19 03:10 Start Date: 15/Aug/19 03:10 Worklog Time Spent: 10m Work Description: pabloem commented on issue #9242: [BEAM-7742] Partition files in BQFL to cater to quotas & limits URL: https://github.com/apache/beam/pull/9242#issuecomment-521497591 Ah we discussed this, right? We need temp tables for dynamic dstinations : ) ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 295161) Time Spent: 1.5h (was: 1h 20m) > BigQuery File Loads to work well with load job size limits > ---------------------------------------------------------- > > Key: BEAM-7742 > URL: https://issues.apache.org/jira/browse/BEAM-7742 > Project: Beam > Issue Type: Improvement > Components: io-py-gcp > Reporter: Pablo Estrada > Assignee: Tanay Tummalapalli > Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > Load jobs into BigQuery have a number of limitations: > [https://cloud.google.com/bigquery/quotas#load_jobs] > > Currently, the python BQ sink implemented in `bigquery_file_loads.py` does > not handle these limitations well. Improvements need to be made to the > miplementation, to: > * Decide to use temp_tables dynamically at pipeline execution > * Add code to determine when a load job to a single destination needs to be > partitioned into multiple jobs. > * When this happens, then we definitely need to use temp_tables, in case one > of the two load jobs fails, and the pipeline is rerun. > Tanay, would you be able to look at this? -- This message was sent by Atlassian JIRA (v7.6.14#76016)