sijocherian / google-bigquery

Automatically exported from code.google.com/p/google-bigquery
0 stars 0 forks source link

bq export measurement-lab:m_lab.2015_02 failure with unexpected internal error #229

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. bq export measurement-lab:m_lab.2015_02 into sharded gzipped json, or same 
for a copy scaled-inference:publicdata.m_lab_2015_02
2. get
Error Reason:internalError. Get more information about this error at 
Troubleshooting Errors: internalError.
Errors:
Unexpected. Please try again.
3.

What is the expected output? What do you see instead?
expected: exported shard-*.json.gz files
see: internalError, repeatable and reproducible, never succeeded.  

What version of the product are you using? On what operating system?
mac os x, latest, chrome browser

Please provide any additional information below.

Original issue reported on code.google.com by dmi...@scaledinference.com on 28 Mar 2015 at 10:18

GoogleCodeExporter commented 9 years ago
Unfortunately, export of the measurement-lab tables is not supported right 
now--they're a special kind of table hosted by BigQuery for certain projects at 
Google.

We should probably improve the error message, but export of these tables is 
unlikely to ever be supported. Instead, we'd like to migrate them to "native" 
BigQuery tables.

Original comment by jcon...@google.com on 30 Mar 2015 at 4:49

GoogleCodeExporter commented 9 years ago
What do you suggest as automated way of processing a sample of 
measurement-lab:m_lab.2015_* data?

Should I schedule BQ SELECT query over m_lab data with my own table as a 
destination and export it? Or Dataflows?

Original comment by dmi...@scaledinference.com on 30 Mar 2015 at 8:23

GoogleCodeExporter commented 9 years ago
Yes, if you run a query over the table with "allow large results" _disabled_, 
you will generate a native BQ table that can then be exported. That's pretty 
much the only way to get data out of an M-Lab table.

Original comment by jcon...@google.com on 30 Mar 2015 at 9:17