{"id":91903,"date":"2020-08-20T07:42:18","date_gmt":"2020-08-20T05:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2"},"modified":"2020-08-20T07:42:18","modified_gmt":"2020-08-20T05:42:18","slug":"kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2","title":{"rendered":"Kuidas Google'i BigQuery demokratiseerib andmeanal\u00fc\u00fcsi. Osa 2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b><i>Tere, Habr! Just n\u00fc\u00fcd on OTUS avatud uue kursuse ootenimekirjale <noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/wDZQ\/\">\u201eAndmeinsener\u201c<\/a><\/noindex>. Kursuse alguse eel j\u00e4tkame kasulike materjalide jagamist. <\/i><\/b><\/p>\n<p><i><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/otus\/\">Loe esimest osa<\/a><\/noindex><\/i><\/p>\n<p><img decoding=\"async\" alt=\"Kuidas Google&#039;i BigQuery demokratiseerib andmeanal\u00fc\u00fcsi. Osa 2\" src=\"\/wp-content\/uploads\/2020\/08\/7b9314bffd954cd408807280f8956c21.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h4>Andmete haldamine<\/h4>\n<p>\nTugev andmete haldamine (Strong Data Governance) on Twitter Engineering'i p\u00f5hialus. Kuna me rakendame BigQuery'd oma platvormil, keskendume andmete avastamisele, juurdep\u00e4\u00e4su kontrollimisele, turvalisusele ja privaatsusele.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Andmete avastamise ja haldamise jaoks oleme laiendanud oma andmejuurdep\u00e4\u00e4su taset (Data Access Layer \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.twitter.com\/engineering\/en_us\/topics\/insights\/2016\/discovery-and-consumption-of-analytics-data-at-twitter.html\">DAL<\/a><\/noindex>), et pakkuda t\u00f6\u00f6riistu nii kohalikule andmele kui ka Google Cloud'i andmetele, pakkudes meie kasutajatele \u00fchtset liidest ja API-d. Kui Google <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/data-catalog\/\">Data Catalog<\/a><\/noindex> liigub avalikustamise suunas, integreerime selle meie projektidesse, et pakkuda kasutajatele funktsioone, nagu veergude otsing.<\/p>\n<p>BigQuery v\u00f5imaldab andmeid kergesti jagada ja neile juurde p\u00e4\u00e4seda, kuid meil oli mingil m\u00e4\u00e4ral seda kontrollida, et v\u00e4ltida andmete lekkeid. Muuhulgas valisime kaks funktsiooni:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/resource-manager\/docs\/organization-policy\/restricting-domains\">Domeenikeelatud jagamine<\/a><\/noindex>: beetaversioon, mis keelab kasutajatel jagada BigQuery andmekogusid kasutajatega, kes asuvad v\u00e4ljaspool Twitterit.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/vpc-service-controls\/\">VPC teenuse kontrollid<\/a><\/noindex>: kontrollielement, mis takistab andmete lekkeid ja n\u00f5uab, et kasutajad p\u00e4\u00e4seksid BigQuery'le juurde tuntud IP-aadresside vahemikest.<\/li>\n<\/ul>\n<p>\nSelleks, et tagada turvalisus, oleme rakendanud autentimise, autoriseerimise ja auditi (AAA) n\u00f5uded j\u00e4rgmistel viisidel:<\/p>\n<ul>\n<li> Autentimine: oleme kasutanud GCP kasutajakontosid ad hoc p\u00e4ringute jaoks ja teenuste kontosid t\u00f6\u00f6p\u00e4ringute jaoks.<\/li>\n<li>Autoriseerimine: oleme n\u00f5udnud, et igal andmekogul oleks teenuse konto omanik ja lugejate grupp.<\/li>\n<li>Audit: oleme eksportinud BigQuery logide ajakava, mis sisaldas \u00fcksikasjalikku teavet p\u00e4ringute t\u00e4itmise kohta, BigQuery andmekogusse anal\u00fc\u00fcsi mugavuse huvides.<\/li>\n<\/ul>\n<p>\nKasutajate isikliku andmete n\u00f5uetekohase t\u00f6\u00f6tlemise tagamiseks peame registreerima k\u00f5ik BigQuery andmekogud, annotaatorima isiklikud andmed, tagama n\u00f5uetekohase s\u00e4ilitamise ja kustutama (\u00fcheksasama) andmed, mis on kasutajate poolt kustutatud.<\/p>\n<p>Olemitasime Google <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/dlp\/\">Cloud Data Loss Prevention API<\/a><\/noindex>, mis kasutab masin\u00f5pet konfidentsiaalsete andmete klassifitseerimiseks ja redigeerimiseks, kuid otsustasime andmekogumi k\u00e4sitsi annotatsiooni kasuks t\u00e4psuse t\u00f5ttu. Kavatseme kasutada Andmekao Ennetamise API-d, et t\u00e4iendada kasutaja annotatsiooni.<\/p>\n<p>Twitteris oleme loonud neli konfidentsiaalsuse kategooriat BigQuery andmekogude jaoks, loetletud siin tundlikkuse v\u00e4henemise j\u00e4rjekorras:<\/p>\n<ul>\n<li>K\u00f5rge tundlikkusega andmekogud on vajalikul juhul saadaval v\u00e4himate privileegide p\u00f5him\u00f5ttel. Igal andmekogul on eraldi lugejate grupp, ja me j\u00e4lgime individuaalsete kontode kasutamist.<\/li>\n<li>Keskmise tundlikkusega andmekogud (\u00fchekordsed pseudon\u00fc\u00fcmid soolatud r\u00e4si kasutades) ei sisalda isikuandmeid (Personally Identifiable Information \u2014 PII) ja on saadaval suuremale t\u00f6\u00f6tajate r\u00fchmale. See on hea tasakaal konfidentsiaalsuse ja andmete kasutusv\u00f5imaluste vahel. See v\u00f5imaldab t\u00f6\u00f6tajatel teostada anal\u00fc\u00fcsi\u00fclesandeid, n\u00e4iteks arvutada, mitu kasutajat on funktsiooni kasutanud, teadmata, kes on tegelikud kasutajad.<\/li>\n<li>Madala tundlikkusega andmekogud sisaldavad kogu identifitseerivat teavet. See on hea l\u00e4henemine konfidentsiaalsuse seisukohalt, kuid seda ei saa kasutada kasutaja tasemel anal\u00fc\u00fcsimiseks.<\/li>\n<li>Avalikud andmekogud (v\u00e4lja antud Twitteri v\u00e4liselt) on k\u00f5igile Twitteri t\u00f6\u00f6tajatele kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti kergesti<\/li>\n<\/ul>\n<p>\nRegistreerimise osas kasutasime plaanitud \u00fclesandeid BigQuery andmekogude loetlemiseks ja nende registreerimiseks Andmejuurdep\u00e4\u00e4su tasemele (<noindex><a rel=\"nofollow\" href=\"https:\/\/blog.twitter.com\/engineering\/en_us\/topics\/insights\/2016\/discovery-and-consumption-of-analytics-data-at-twitter.html\">DAL<\/a><\/noindex>), Twitteri metainfode riiul. Kasutajad annotatsioonmisevad andmekogudele konfidentsiaalsuse teavet ning m\u00e4\u00e4ravad s\u00e4ilitamise t\u00e4htaja. Andmete puhastamise osas hindame kahe variandi j\u00f5udlust ja kulusid: <i>1.<\/i> Andmekogude puhastamine GCS-is selliste t\u00f6\u00f6riistade nagu Scalding abil ja nende laadimine BigQuery-sse; <i>2.<\/i> BigQuery DML operaatorite kasutamine. T\u00f5en\u00e4oliselt kasutame m\u00f5lema meetodi kombinatsiooni erinevate r\u00fchmade ja andmete n\u00f5uete rahuldamiseks.<\/p>\n<h4>S\u00fcsteemi funktsionaalsus<\/h4>\n<p>\nKuna BigQuery on hallatav teenus, polnud vaja Twitteri SRE meeskonda s\u00fcsteemide haldamise v\u00f5i t\u00f6\u00f6vahetuste t\u00e4itmisega seotud \u00fclesannete jaoks kaasata. Suure salvestus- ja arvutusv\u00f5imekuse tagamine oli lihtne. Saime slotide reserveerimist muuta, luues Google'i tugipileteid. Oleme tuvastanud, et teatud valdkondi, nagu slotide jaotamise eneseabi ning j\u00e4relevalve t\u00f6\u00f6riista t\u00e4iustamine, v\u00f5iks parandada ja edastasime need ettepanekud Google'ile.<\/p>\n<h4>Hind<\/h4>\n<p>\nMeie esialgne anal\u00fc\u00fcs n\u00e4itas, et p\u00e4ringute maksumus BigQuery ja Presto osas oli samal tasemel. Me soetasime slotid <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/bigquery\/pricing#flat_rate_pricing\">fikseeritud<\/a><\/noindex> hinna eest, et tagada stabiilne igakuine kulu, selle asemel, et maksta <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/bigquery\/pricing#on_demand_pricing\">n\u00f5udmise j\u00e4rgi<\/a><\/noindex> processed data per TB. See otsus p\u00f5hines ka kasutajate tagasisidel, kes ei soovinud igat p\u00e4ringu sooritamise eel m\u00f5elda kuludele.<\/p>\n<p>Andmete salvestamine BigQuery'sse t\u00f5i kaasa kulud GCS-i kuludele. Sellised t\u00f6\u00f6riistad nagu Scalding n\u00f5uavad andmekogusid GCS-is ja BigQuery juurde p\u00e4\u00e4semiseks pidime laadima need samad andmekogud BigQuery formaati <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/blog\/products\/gcp\/inside-capacitor-bigquerys-next-generation-columnar-storage-format\">Capacitor<\/a><\/noindex>. Me t\u00f6\u00f6tame selle nimel, et \u00fchendada Scalding BigQuery andmekogudega, mis k\u00f5rvaldab vajaduse andmekogude salvestamiseks nii GCS-is kui ka BigQuery's.<\/p>\n<p>Harvadel juhtudel, mis n\u00f5udsid harvade p\u00e4ringute tegemist k\u00fcmnete petabaitide ulatuses, leidsime, et andmekogude salvestamine BigQuery'sse ei ole majanduslikult m\u00f5ttekas ning kasutasime Presto't, et p\u00e4\u00e4seda andmekogudele GCS-is. Selleks uurime BigQuery v\u00e4liseid andmeallikaid.<\/p>\n<h3>J\u00e4rgmised sammud<\/h3>\n<p>\nOleme m\u00e4rganud suurt huvi BigQuery vastu alates alfa v\u00e4ljaandmisest. Me lisanud rohkem andmekogusid ja rohkem meeskondi BigQuery'sse. T\u00f6\u00f6tame andmeanal\u00fc\u00fcsi t\u00f6\u00f6riistade konnektorite v\u00e4ljat\u00f6\u00f6tamise nimel, nagu Scalding, et lugeda ja kirjutada BigQuery salvestusse. Me vaatame selliseid t\u00f6\u00f6riistu nagu Looker ja Apache Zeppelin, et luua \u00e4riaruandeid BigQuery andmekogude baasilt.<\/p>\n<p>Koost\u00f6\u00f6 Google'iga on olnud v\u00e4ga viljakas ja oleme r\u00f5\u00f5msad, et saame j\u00e4tkata ja edendada seda partnerlust. Oleme t\u00f6\u00f6tanud koos Google'iga, et rakendada meie oma <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/issue-tracker\/guides\/partner-access\">Partner Issue Tracker<\/a><\/noindex>, et otseselt Google'ile p\u00e4ringuid saata. M\u00f5ned neist, nagu BigQuery Parquet'i laadija, on Google juba ellu viinud.<\/p>\n<p>Siin on m\u00f5ned meie k\u00f5rgeima prioriteediga funktsioonisoovid Google'i jaoks:<\/p>\n<ul>\n<li>T\u00f6\u00f6riistad mugavaks andmete vastuv\u00f5tmiseks ja LZO-Thrift formaadi toetamine.<\/li>\n<li>Tunnip\u00f5hine segmentimine<\/li>\n<li>Parandused juurdep\u00e4\u00e4suhalduse valdkonnas, nagu tabeli, rea ja veeru taseme \u00f5igused.<\/li>\n<li>BigQuery <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/bigquery\/external-data-sources\">V\u00e4listingimustes andmeallikad<\/a><\/noindex> koos Hive Metastore'i integreerimise ja LZO-Thrift formaadi toetamisega.<\/li>\n<li>Parendatud andmekatalooge BigQuery kasutajaliideses<\/li>\n<li>Iseteenindus slotide jaotamiseks ja j\u00e4lgimiseks.<\/li>\n<\/ul>\n<p><\/p>\n<h3>Kokkuv\u00f5te<\/h3>\n<p>\nAndmete anal\u00fc\u00fcsi, visualiseerimise ja masin\u00f5ppe demokratiseerimine ohutult on Data Platformi meeskonna k\u00f5rgeim prioriteet. Oleme m\u00e4\u00e4ratlenud Google BigQuery ja Data Studio t\u00f6\u00f6riistad, mis v\u00f5ivad aidata selle eesm\u00e4rgi saavutamisel, ja v\u00e4lja andnud eelmisel aastal BigQuery Alpha kogu ettev\u00f5ttele. <\/p>\n<p>Oleme leidnud, et p\u00e4ringud BigQuery-s olid lihtsad ja t\u00f5husad. Andmete vastuv\u00f5tmiseks ja transformeerimiseks kasutasime Google'i t\u00f6\u00f6riistu lihtsate torude jaoks, kuid keerukamate torude puhul pidime looma oma Airflow infrastruktuuri. BigQuery teenused autentimise, autoriseerimise ja auditi valdkonnas rahuldasid meie vajadusi. Metaandmete haldamiseks ja privaatsuse tagamiseks vajasime suurt paindlikkust ja pidime looma oma s\u00fcsteemid. BigQuery, olles hallatav teenus, oli lihtne kasutada. P\u00e4ringute kulud olid meie olemasolevate t\u00f6\u00f6riistadega sarnased. Andmete salvestamine BigQuery-s t\u00f5i kaasa lisakulud GCS-i kuludele.<\/p>\n<p>Kokkuv\u00f5ttes t\u00f6\u00f6tab BigQuery h\u00e4sti \u00fcldise SQL anal\u00fc\u00fcsi jaoks. M\u00e4rkame suurt huvi BigQuery vastu ning t\u00f6\u00f6tame selle nimel, et \u00fcle kanda rohkem andmehulkasid, kaasata rohkem meeskondi ja luua rohkem torusid BigQuery abil. Twitteris kasutatakse erinevaid andmeid, mille jaoks on vajalik selliste t\u00f6\u00f6riistade nagu Scalding, Spark, Presto ja Druid kombinatsioon. Kavatseme j\u00e4tkata oma andmeanal\u00fc\u00fcsi t\u00f6\u00f6riistade arendamist ja anda oma kasutajatele selged soovitused, kuidas meie pakkumisi parimal viisil kasutada.<\/p>\n<h3>T\u00e4nu s\u00f5nad<\/h3>\n<p>\nTahaksin t\u00e4nada oma kaast\u00f6\u00f6tajaid ja meeskonnakaaslasi, Anzhu Dja ja Willa Pascucci, nende suurep\u00e4rase koost\u00f6\u00f6 ja raske t\u00f6\u00f6 eest selle projekti kallal. Samuti tahaksin t\u00e4nada insenere ja juhte mitmetest meeskondadest Twitteris ja Google'is, kes aitasid meid ja BigQuery kasutajaid Twitteris, pakkudes v\u00e4\u00e4rtuslikku tagasisidet.<\/p>\n<p>Kui olete huvitatud nende \u00fclesannete kallal t\u00f6\u00f6tamisest, tutvuge meie <noindex><a rel=\"nofollow\" href=\"https:\/\/careers.twitter.com\/content\/careers-twitter\/en\/jobs-search.html?q=&amp;team=careers-twitter%3Ateam%2Finfrastructure-engineering\">t\u00f6\u00f6pakkumistega<\/a><\/noindex> Data Platform meeskonnas.<\/p>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/eD9S\/\">Andmete kvaliteet DWH-is - andmehoidla konsistents.<\/a><\/noindex><\/p>\n<p>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/otus\/blog\/513782\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u044f\u043c\u043e \u0441\u0435\u0439\u0447\u0430\u0441 \u0432 OTUS \u043e\u0442\u043a\u0440\u044b\u0442 \u043d\u0430\u0431\u043e\u0440 \u043d\u0430 \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0442\u043e\u043a \u043a\u0443\u0440\u0441\u0430 \u00abData Engineer\u00bb. \u0412 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043a\u0443\u0440\u0441\u0430 \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u0435\u043c \u0434\u0435\u043b\u0438\u0442\u044c\u0441\u044f \u0441 \u0432\u0430\u043c\u0438 \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u043c \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u043c. \u0427\u0438\u0442\u0430\u0442\u044c \u043f\u0435\u0440\u0432\u0443\u044e \u0447\u0430\u0441\u0442\u044c \u0423\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u043c\u0438 \u0421\u0438\u043b\u044c\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u043c\u0438 (Strong Data Governance) \u2014 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u0439 \u043f\u0440\u0438\u043d\u0446\u0438\u043f Twitter Engineering. \u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u043c\u044b \u0432\u043d\u0435\u0434\u0440\u044f\u0435\u043c BigQuery \u0432 \u043d\u0430\u0448\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443, \u043c\u044b \u043a\u043e\u043d\u0446\u0435\u043d\u0442\u0440\u0438\u0440\u0443\u0435\u043c\u0441\u044f \u043d\u0430 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u0438 \u0434\u0430\u043d\u043d\u044b\u0445, \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0435 \u0434\u043e\u0441\u0442\u0443\u043f\u0430, \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":91904,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-91903","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u044f\u043c\u043e \u0441\u0435\u0439\u0447\u0430\u0441 \u0432 OTUS \u043e\u0442\u043a\u0440\u044b\u0442 \u043d\u0430\u0431\u043e\u0440 \u043d\u0430 \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0442\u043e\u043a \u043a\u0443\u0440\u0441\u0430 \u00abData Engineer\u00bb.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a BigQuery \u043e\u0442 Google \u0434\u0435\u043c\u043e\u043a\u0440\u0430\u0442\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b \u0430\u043d\u0430\u043b\u0438\u0437 \u0434\u0430\u043d\u043d\u044b\u0445. \u0427\u0430\u0441\u0442\u044c 2 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u044f\u043c\u043e \u0441\u0435\u0439\u0447\u0430\u0441 \u0432 OTUS \u043e\u0442\u043a\u0440\u044b\u0442 \u043d\u0430\u0431\u043e\u0440 \u043d\u0430 \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0442\u043e\u043a \u043a\u0443\u0440\u0441\u0430 \u00abData Engineer\u00bb.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-08-20T05:42:18+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-08-20T05:42:18+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kuidas Google'i BigQuery demokratiseeris andmete anal\u00fc\u00fcsi. Osa 2 | ProHoster","description":"Tere, Habrahabr! Praegu toimub OTUSes uue \"Andmeinseneri\" kursuse voolu vastuv\u00f5tt.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0430\u043a BigQuery \u043e\u0442 Google \u0434\u0435\u043c\u043e\u043a\u0440\u0430\u0442\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b \u0430\u043d\u0430\u043b\u0438\u0437 \u0434\u0430\u043d\u043d\u044b\u0445. \u0427\u0430\u0441\u0442\u044c 2 | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u0425\u0430\u0431\u0440! \u041f\u0440\u044f\u043c\u043e \u0441\u0435\u0439\u0447\u0430\u0441 \u0432 OTUS \u043e\u0442\u043a\u0440\u044b\u0442 \u043d\u0430\u0431\u043e\u0440 \u043d\u0430 \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0442\u043e\u043a \u043a\u0443\u0440\u0441\u0430 \u00abData Engineer\u00bb.","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-bigquery-ot-google-demokratiziroval-analiz-dannyh-chast-2","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-08-20T05:42:18+00:00","article:modified_time":"2020-08-20T05:42:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"91903","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 12:18:28","updated":"2022-10-08 11:10:45","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/91903","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=91903"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/91903\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/91904"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=91903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=91903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=91903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}