Closed sean-rose closed 3 months ago
moz-fx-data-marketing-prod
to avoid breaking existing reporting."sql.diff
⚠️ Only part of the diff is displayed.
sql.diff
⚠️ Only part of the diff is displayed.
Just in case you didn't see, there are some scheduled redash queries on the tables so those will need to be updated https://mozilla.acryl.io/container/urn:li:container:97ec3babcfed1a4faa980da5ed10f224/Entities
Thanks for pointing those out, especially since it turns out that some of those are directly referencing ETL tables instead of the intended user-facing views. For now I'll update this PR to add placeholder pass-through views where the ETL tables were in the moz-fx-data-marketing-prod
project to avoid breaking anything, then have a follow-up PR later to remove all such placeholder pass-through views after I've updated the Looker explores to point to the new locations and gotten whoever created those Redash queries to update them (a well as some Looker Studio dashboards I'm aware of).
sql.diff
⚠️ Only part of the diff is displayed.
DENG-1733: Make Google Search Console data available for use
As discussed during the Data Org work week, going forward
moz-fx-data-marketing-prod
will be used as a place for Google Search Console, Google Analytics, etc. to export data, but all ETLs and user-facing views should be inmoz-fx-data-shared-prod
&mozdata
.Checklist for reviewer:
<username>:<branch>
of the fork as parameter. The parameter will also show up in the logs of themanual-trigger-required-for-fork
CI task together with more detailed instructions.For modifications to schemas in restricted namespaces (see
CODEOWNERS
):┆Issue is synchronized with this Jira Task