Working with JSON and Array data in BigQuery 2.5 Reviews

34606 reviews

Pravin S. · Reviewed больше 1 года ago

NANCY PAOLA P. · Reviewed больше 1 года ago

Syed Ghayur Abbas N. · Reviewed больше 1 года ago

Some parts might be checked because of old Bigquery Interface (grey area not longer grey for nested fields). But really helpful and good for own thinking :)

Luise W. · Reviewed больше 1 года ago

Cristobal V. · Reviewed больше 1 года ago

Renato R. · Reviewed больше 1 года ago

Jorge A. · Reviewed больше 1 года ago

Mauricio H. · Reviewed больше 1 года ago

Bien

Víctor C. · Reviewed больше 1 года ago

Nassim B. · Reviewed больше 1 года ago

Nicolas S. · Reviewed больше 1 года ago

Nassim B. · Reviewed больше 1 года ago

Marco Q. · Reviewed больше 1 года ago

Kalaiselvi S. · Reviewed больше 1 года ago

Damindu V. · Reviewed больше 1 года ago

good

Palak G. · Reviewed больше 1 года ago

Rohit R. · Reviewed больше 1 года ago

Too more tasks for an hour, so we cannot go deep for each task.

Katawut W. · Reviewed больше 1 года ago

Paula B. · Reviewed больше 1 года ago

Sumit P. · Reviewed больше 1 года ago

Alessandro C. · Reviewed больше 1 года ago

Albert X. · Reviewed больше 1 года ago

Romain B. · Reviewed больше 1 года ago

JONATHAN R. · Reviewed больше 1 года ago

This lab should be reviewed. The first question is misleading, as the best answer is "all of the above". If you have a big table, a change in the email address of the customer would need to be reflected in the whole table. If it's an order table, maybe the customer bought a lot of stuff and thus has a lot of lines. We would need to change all those lines. So second answer is good. The third answer is quite valid too. There could be different granularities. Let's say we store "order lines", we could have data related to the "order header". So this would need to be taken into account in the reporting. The correct answer is then "All of the above". + Implicit join on arrays should be considered a bad practice.

SIMON R. · Reviewed больше 1 года ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.