[
https://issues.apache.org/jira/browse/BEAM-4824?focusedWorklogId=138352&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138352
]
ASF GitHub Bot logged work on BEAM-4824:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Aug/18 11:42
Start Date: 27/Aug/18 11:42
Worklog Time Spent: 10m
Work Description: calonso commented on issue #6055: [BEAM-4824] Batch
BigQueryIO returns job results
URL: https://github.com/apache/beam/pull/6055#issuecomment-416199545
Sorry for the delay, been on holidays.
I think I can make the new behaviour opt-in by adding a new method to the
builder, similar to what I did in #5341.
I'm not sure though on what to do about your second comment. Maybe just
limiting to batch jobs? (using `expandUntriggered`?) although I think having
the job result information is really valuable in all cases, even if it changes
the record granularity.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 138352)
Time Spent: 0.5h (was: 20m)
> Get BigQueryIO batch loads to return something actionable
> ---------------------------------------------------------
>
> Key: BEAM-4824
> URL: https://issues.apache.org/jira/browse/BEAM-4824
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Carlos Alonso
> Assignee: Carlos Alonso
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ATM BigQueryIO batchloads returns an empty collection that has no information
> related to how the load job finished. It is even returned before the job
> finishes.
>
> Change it so that:
> # The returning PCollection only appers when the job has actually finished
> # The returning PCollection contains information about the job result
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
