Utiliser des données JSON et Array dans BigQuery 2.5 avis

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. · Examiné il y a 12 mois

Cristobal V. · Examiné il y a 12 mois

Renato R. · Examiné il y a 12 mois

Jorge A. · Examiné il y a 12 mois

Mauricio H. · Examiné il y a 12 mois

Bien

Víctor C. · Examiné il y a 12 mois

Nassim B. · Examiné il y a 12 mois

Nicolas S. · Examiné il y a 12 mois

Nassim B. · Examiné il y a 12 mois

Marco Q. · Examiné il y a 12 mois

Kalaiselvi S. · Examiné il y a 12 mois

Damindu V. · Examiné il y a 12 mois

good

Palak G. · Examiné il y a 12 mois

Rohit R. · Examiné il y a 12 mois

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

Katawut W. · Examiné il y a 12 mois

Paula B. · Examiné il y a 12 mois

Sumit P. · Examiné il y a 12 mois

Alessandro C. · Examiné il y a 12 mois

Albert X. · Examiné il y a 12 mois

Romain B. · Examiné il y a 12 mois

JONATHAN R. · Examiné il y a 12 mois

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. · Examiné il y a 12 mois

ERIC C. · Examiné il y a 12 mois

JUAN JOSE M. · Examiné il y a 12 mois

Romain M. · Examiné il y a 12 mois