Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Looker reports and alerts #12068

Closed
pkarman opened this issue Sep 12, 2019 · 1 comment
Closed

Migrate Looker reports and alerts #12068

pkarman opened this issue Sep 12, 2019 · 1 comment
Labels
Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns Epic Team: Delta 🔺

Comments

@pkarman
Copy link
Contributor

pkarman commented Sep 12, 2019

Looker is going to be decommissioned. We need to migrate our existing SQL reports and alerts to some other mechanism.

Proposal

Move the SQL to individual .sql files under the new app/sql directory as with #12044 and write a job that runs each one nightly just as Looker currently does.

@pkarman pkarman added the Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns label Sep 12, 2019
@enriquemanuel
Copy link
Contributor

We could potentially have those jobs that execute sql in lambda's so we don't tax the application with reporting capabilities. (just an idea)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns Epic Team: Delta 🔺
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants