Mengoptimalkan Performa Kueri LookML Ulasan

Venkata S. · Diulas sekitar 3 tahun lalu

SMRITI G. · Diulas sekitar 3 tahun lalu

KANDI A. · Diulas sekitar 3 tahun lalu

Ishav V. · Diulas sekitar 3 tahun lalu

Sherilyn P. · Diulas sekitar 3 tahun lalu

Emiliano A. · Diulas sekitar 3 tahun lalu

María Del Mar D. · Diulas sekitar 3 tahun lalu

Jaume A. · Diulas sekitar 3 tahun lalu

V S. · Diulas sekitar 3 tahun lalu

done

Vani M. · Diulas sekitar 3 tahun lalu

Yaxiong W. · Diulas sekitar 3 tahun lalu

María Del Mar D. · Diulas sekitar 3 tahun lalu

Marie-Christine C. · Diulas sekitar 3 tahun lalu

Multiple notes, in order: - 1 hour and 30 minutes is NOT enough to do this lab properly and read through things and extra resources being listed within the lab. At least another 30 minutes would be required. - In the section "Implement caching policies", you are describing an extract, load, transform process but then you summarize that as "ETL" instead of "ELT". - In the section "Join the minimal amount of views to define new Explores", you state that the one_to_many configuration may not be the "most optimal configuration" when in fact this is not about optimal, using one_to_many here is just incorrect. - In the section "Define performant join relationships for efficient Explore queries", you provide the instruction - "Return to the browser tab for the Explore query, and refresh the page." and then speak about there being 2 queries, which I understand, but when you ask folks to refresh the page the explore runs automatically and if you are not quick enough you won't see the query that generates the table because you will already have run the updated configuration. Either find a different way to do this (like opening through a new tab) or provide a workaround for folks to see the 2 queries. - In the section "Modify and review PDTs in development", the question "Why is aggregated_orders::aggregate_sales still not listed under the Production tab, even though it was built successfully?" doesn't make sense. "aggregated_orders::aggregate_sales" IS listed within the Production tab as its previous version that was run, it didn't go anywhere, it is just also listed in the Development tab because of the changes we implemented in Development. - The section 4 is missing a completion check as if it isn't even part of this lab. - In the section "Ready for more?", and this I think applies to all labs I took so far, please suggest the next step in the learning path or at least don't suggest something general/unspecific/unrelated to the current lab being done.

Tiago R. · Diulas sekitar 3 tahun lalu

素 李. · Diulas sekitar 3 tahun lalu

Ajit P. · Diulas sekitar 3 tahun lalu

Gopi J. · Diulas sekitar 3 tahun lalu

Martyna K. · Diulas sekitar 3 tahun lalu

Good

Gitesh G. · Diulas sekitar 3 tahun lalu

Dr. Kondala Kameswara Rao N. · Diulas sekitar 3 tahun lalu

537 Chinni krishna M. · Diulas sekitar 3 tahun lalu

Saurav K. · Diulas sekitar 3 tahun lalu

YOGENDER S. · Diulas sekitar 3 tahun lalu

Kishan P. · Diulas sekitar 3 tahun lalu

Raji n. · Diulas sekitar 3 tahun lalu