Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

BigQuery returning `There is no data to display.`

I've setup a Datastream CDC into BigQuery stream. The stream started without issues and is currently showing that data is being transferred successfully.

In BigQuery, the database and the tables have reflected. Selecting a table schema shows the correct columns. In table details > Storage info, it shows that there are rows in the tables already.

AdrianQ_0-1713407830498.png

However, on table preview, it says `There is no data to display.` When running a query on the table, I get the same results.

AdrianQ_1-1713407878522.png

I expected initially there might be some delay from when the stream was setup to when I can query the data on BigQuery. But more than 8 hours since the stream has started (and logs says the tables were populated almost immediately), and I still can't query any data from my tables even though table details says they're there.

Would appreciate any insight into this. Thanks.

 

EDIT: This has been resolved. The data has become available without intervention around 18 hours after. I guess there's just a really huge delay when using Datastream to BigQuery.

Solved Solved
8 5 5,075
1 ACCEPTED SOLUTION

This was eventually resolved for me by simply waiting. It took a looong time, ~18hrs for me, but the data ended up appearing in the end. Hope this helps all others experiencing the same issue (it might not solve the problem but at least alleviate the anxiety that something's wrong)

View solution in original post

5 REPLIES 5

we are having the exact problem on a new datastream/big query integration on europe-west1

I'm also having the exact same problem (us-central1) - well, i'm assuming it's the same problem as it's been 1 hour and no data can be queried in BQ.

The same issue europe-west3
Should I just wait?

This was eventually resolved for me by simply waiting. It took a looong time, ~18hrs for me, but the data ended up appearing in the end. Hope this helps all others experiencing the same issue (it might not solve the problem but at least alleviate the anxiety that something's wrong)

for me I just had to wait as well, my guess is that while the first import was happening, I queried one of the tables, and it probably cached the result without any data, then I had to wait for my cache to die until the records actually showed up