Delay in visibility of rows inserted by Streaming API

[GoogleCodeExporter]

As a consequence of BigQuery incident #18010 [1] rows inserted via the 
streaming API may take longer to become visible in queries. The delay is 
inversely proportional to the volume of streaming inserts.

[1] https://status.cloud.google.com/incident/bigquery/18010

Original issue reported on code.google.com by me...@google.com on 18 Jun 2015 at 8:43

[GoogleCodeExporter]

I'm still seeing delays in streaming inserts showing up in queries. currently 
all my data sets are atleast an hour behind.

Original comment by a...@thecarousell.com on 18 Jun 2015 at 10:06

[GoogleCodeExporter]

Same here, big delays (an hour or more) in streamed records.

Original comment by lorenzo....@noovle.it on 18 Jun 2015 at 11:07

[GoogleCodeExporter]

Same here. We have big (more than an hour) delay.

Original comment by cou...@gmail.com on 18 Jun 2015 at 11:26

[GoogleCodeExporter]

Same here. :weary::weary::weary::weary::weary:

Original comment by YoheiM...@gmail.com on 18 Jun 2015 at 11:41

[GoogleCodeExporter]

50 minute delay for us

Original comment by ross.dou...@asimmetric.com on 18 Jun 2015 at 12:00

[GoogleCodeExporter]

We are still investigating the issue with Bigquery Streaming API where inserted 
rows might be unavailable for a longer duration. 

This issue affects rows inserted between 2015-06-17 14:12 and 17:48 US/Pacific. 

We will provide another status update by 2015-05-08 10:00 US/Pacific with 
current details.

Original comment by kmuz...@google.com on 18 Jun 2015 at 1:15

[GoogleCodeExporter]

Is duration dependent on size/number of delayed inserts?

Original comment by igor.lau...@bee7.com on 18 Jun 2015 at 5:05

[GoogleCodeExporter]

Issue 264 has been merged into this issue.

Original comment by thomasp...@google.com on 18 Jun 2015 at 5:16

[GoogleCodeExporter]

Issue 265 has been merged into this issue.

Original comment by dk...@google.com on 18 Jun 2015 at 8:21

[GoogleCodeExporter]

Still seeing this too. ~30 min delay.

Original comment by adam.bro...@mobivity.com on 18 Jun 2015 at 11:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It's working for me now. I was getting several hour delays.

Original comment by evan...@gmail.com on 19 Jun 2015 at 4:16

[GoogleCodeExporter]

Thanks Evan for the confirmation.

The issue with BigQuery streaming is partially resolved. Recently streamed data 
should behave as expected. However, there is a subset of data that arrived in 
the system on 2015-06-17 that is still unavailable. We will have further 
updates on this remaining unavailable data no later than 2015-06-19 10:00am PDT.

Original comment by jossel...@google.com on 19 Jun 2015 at 5:15

[GoogleCodeExporter]

Working for me too at this moment.

Thanks for keeping us updated!

Original comment by esan...@nostrum.eu on 19 Jun 2015 at 6:37

[GoogleCodeExporter]

Part of our streamed data is not available since 2015-06-12 and part of it 
started to be unavailable since 2015-06-18. Missing data from 12th June - can 
it be ralated to this issue ?

Original comment by v...@miumeet.com on 19 Jun 2015 at 2:53

[GoogleCodeExporter]

> We will have further updates on this remaining unavailable data no later than 
2015-06-19 10:00am PDT.

Is there any update?

Original comment by cou...@gmail.com on 20 Jun 2015 at 2:52

[GoogleCodeExporter]

As of roughly 5:00PM PST, all data should be fully available (including all 
data from 2015-06-17) and immediately visible after insertion. This issue 
should be fully resolved. Please let us know if there are any persistent issues.

#15, this incident should be independent of any issues you're seeing from 
06-12. Please contact support/file a separate issue with those details if 
necessary.

Original comment by seanc...@google.com on 20 Jun 2015 at 3:16

[GoogleCodeExporter]

Original comment by seanc...@google.com on 20 Jun 2015 at 3:17

• Changed state: Fixed