[ 
https://issues.apache.org/jira/browse/BEAM-8960?focusedWorklogId=367840&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-367840
 ]

ASF GitHub Bot logged work on BEAM-8960:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Jan/20 22:52
            Start Date: 07/Jan/20 22:52
    Worklog Time Spent: 10m 
      Work Description: chamikaramj commented on pull request #10427: 
[BEAM-8960]: Add an option for user to opt out of using insert id for BigQuery 
streaming insert.
URL: https://github.com/apache/beam/pull/10427
 
 
   
 
----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 367840)
    Remaining Estimate: 20h 10m  (was: 20h 20m)
            Time Spent: 3h 50m  (was: 3h 40m)

> Add an option for user to be able to opt out of using insert id for BigQuery 
> streaming insert.
> ----------------------------------------------------------------------------------------------
>
>                 Key: BEAM-8960
>                 URL: https://issues.apache.org/jira/browse/BEAM-8960
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-gcp
>            Reporter: Yiru Tang
>            Assignee: Yiru Tang
>            Priority: Minor
>   Original Estimate: 24h
>          Time Spent: 3h 50m
>  Remaining Estimate: 20h 10m
>
> BigQuery streaming insert id offers best effort insert deduplication. If user 
> choose to opt out of using insert ids, they could potentially to be opt into 
> using our current new streaming backend which gives higher speed and more 
> quota. Insert id deduplication is best effort and doesn't have ultimate just 
> once guarantees.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to