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

feat: new report schedule models #11550

Merged
merged 9 commits into from
Nov 6, 2020
Merged

Conversation

dpgaspar
Copy link
Member

@dpgaspar dpgaspar commented Nov 4, 2020

SUMMARY

First PR (out of 3 on backend) for alerts and reports revamp, our main goals are: simplify and support future improvements/extensions.

This work will proceed on a side by side fashion until it will be considered complete and stable, then the current implementation will be removed from the codebase.

(Team work with @willbarrett and @mistercrunch)

Following PR's on the backend:
1 - REST API and business logic
2 - Celery tasks revamp

Superset Report Schedules (3)

ADDITIONAL INFORMATION

  • Has associated issue:
  • Changes UI
  • Requires DB Migration.
  • Confirm DB Migration upgrade and downgrade tested.
  • Introduces new feature or API
  • Removes existing feature or API

@codecov-io
Copy link

codecov-io commented Nov 4, 2020

Codecov Report

Merging #11550 into master will decrease coverage by 0.33%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #11550      +/-   ##
==========================================
- Coverage   59.59%   59.26%   -0.34%     
==========================================
  Files         832      834       +2     
  Lines       40482    40581      +99     
  Branches     3666     3666              
==========================================
- Hits        24126    24051      -75     
- Misses      16187    16361     +174     
  Partials      169      169              
Flag Coverage Δ
cypress 55.01% <ø> (ø)
python 61.57% <0.00%> (-0.52%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...ions/versions/49b5a32daba5_add_report_schedules.py 0.00% <0.00%> (ø)
superset/models/reports.py 0.00% <0.00%> (ø)
superset/db_engine_specs/sqlite.py 65.62% <0.00%> (-9.38%) ⬇️
superset/databases/commands/create.py 82.97% <0.00%> (-8.52%) ⬇️
superset/databases/commands/update.py 85.71% <0.00%> (-8.17%) ⬇️
superset/utils/celery.py 82.14% <0.00%> (-3.58%) ⬇️
superset/datasets/api.py 89.56% <0.00%> (-3.30%) ⬇️
superset/models/core.py 86.22% <0.00%> (-2.21%) ⬇️
superset/views/core.py 71.69% <0.00%> (-2.09%) ⬇️
superset/db_engine_specs/base.py 85.60% <0.00%> (-1.87%) ⬇️
... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 52145f8...f015c35. Read the comment docs.

@dpgaspar dpgaspar marked this pull request as ready for review November 4, 2020 19:12
@dpgaspar dpgaspar added the risk:db-migration PRs that require a DB migration label Nov 4, 2020
superset/models/reports.py Outdated Show resolved Hide resolved
@dpgaspar dpgaspar merged commit bd79bd2 into apache:master Nov 6, 2020
@dpgaspar dpgaspar mentioned this pull request Nov 9, 2020
6 tasks
@dpgaspar dpgaspar mentioned this pull request Nov 19, 2020
6 tasks
auxten pushed a commit to auxten/incubator-superset that referenced this pull request Nov 20, 2020
* feat: new report schedule models

* lint and unique constraint

* support sqlite

* fix sqlite

* add audit mixin and minor fixes

* fix FK's

* address comments

* lint
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 1.0.0 labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels risk:db-migration PRs that require a DB migration size/L 🚢 1.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants