Fixed
Status Update
Comments
bl...@google.com <bl...@google.com>
el...@google.com <el...@google.com> #2
We are not likely to implement this. You can recreate a CREATE TABLE statement using INFORMATION_SCHEMA, though: b/35906063 .
el...@google.com <el...@google.com>
th...@google.com <th...@google.com>
si...@leroymerlin.fr <si...@leroymerlin.fr> #3
+1, this also exists in Teradata. This is a REAL time saver!
al...@weplananalytics.com <al...@weplananalytics.com> #4
+1
ab...@gmail.com <ab...@gmail.com> #5
this feature really help us in migrating the table between different environment in HIVE data warehouse system.
ja...@google.com <ja...@google.com>
vi...@gmail.com <vi...@gmail.com> #6
Yes this feature is much needed. Please introduce this feature.
sg...@tcs.woolworths.com.au <sg...@tcs.woolworths.com.au> #7
Yes please introduce this feature asap. It would be very much helpful.
ra...@gmail.com <ra...@gmail.com> #8
We also agree to include feature to extract Database object DDL in Bigquery. For eg: we are in a phase of migrating into BigQuery and extraction of DDL of Objects like Table, View, Synonyms are very much needed from time to time but it is not available to end users.
Description
Currently there are some workarounds available:
- Use the Job ID of the query that created the table, and then use the "jobs.get" method in order to retrieve the query executed in that job.
- If you are only interested in the table information and/or its schema, it may be enough to get the table information from the UI/API/bq.
---
[1]
[2]