Working with JSON and Array data in BigQuery 2.5 Reviews

Syed Ghayur Abbas N. · Reviewed 12 months 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 12 months ago

Cristobal V. · Reviewed 12 months ago

Renato R. · Reviewed 12 months ago

Jorge A. · Reviewed 12 months ago

Mauricio H. · Reviewed 12 months ago

Bien

Víctor C. · Reviewed 12 months ago

Nassim B. · Reviewed 12 months ago

Nicolas S. · Reviewed 12 months ago

Nassim B. · Reviewed 12 months ago

Marco Q. · Reviewed 12 months ago

Kalaiselvi S. · Reviewed 12 months ago

Damindu V. · Reviewed 12 months ago

good

Palak G. · Reviewed 12 months ago

Rohit R. · Reviewed 12 months ago

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

Katawut W. · Reviewed 12 months ago

Paula B. · Reviewed 12 months ago

Sumit P. · Reviewed 12 months ago

Alessandro C. · Reviewed 12 months ago

Albert X. · Reviewed 12 months ago

Romain B. · Reviewed 12 months ago

JONATHAN R. · Reviewed 12 months 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 12 months ago

ERIC C. · Reviewed 12 months ago

JUAN JOSE M. · Reviewed 12 months ago