关于“Working with JSON and Array data in BigQuery 2.5”的评价

Syed Ghayur Abbas N. · 已于 12 months前审核

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. · 已于 12 months前审核

Cristobal V. · 已于 12 months前审核

Renato R. · 已于 12 months前审核

Jorge A. · 已于 12 months前审核

Mauricio H. · 已于 12 months前审核

Bien

Víctor C. · 已于 12 months前审核

Nassim B. · 已于 12 months前审核

Nicolas S. · 已于 12 months前审核

Nassim B. · 已于 12 months前审核

Marco Q. · 已于 12 months前审核

Kalaiselvi S. · 已于 12 months前审核

Damindu V. · 已于 12 months前审核

good

Palak G. · 已于 12 months前审核

Rohit R. · 已于 12 months前审核

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

Katawut W. · 已于 12 months前审核

Paula B. · 已于 12 months前审核

Sumit P. · 已于 12 months前审核

Alessandro C. · 已于 12 months前审核

Albert X. · 已于 12 months前审核

Romain B. · 已于 12 months前审核

JONATHAN R. · 已于 12 months前审核

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. · 已于 12 months前审核

ERIC C. · 已于 12 months前审核

JUAN JOSE M. · 已于 12 months前审核