Details

Reviewers

dgibson
sashank
schrockn

Commits

R1:5a662977dfb0: [sensors-10] schedule def new API

Summary

Should note: this will require a wipe for folks who are running off of master. This changes the schema by dropping run_key as a column, and changing the tick data schema.

Thought about doing a migration, but it might save some complexity to require the wipe.

Test Plan

Diff Detail

Repository

R1 dagster

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

prha created this revision.Nov 24 2020, 11:41 PM

Harbormaster returned this revision to the author for changes because remote builds failed.Nov 24 2020, 11:57 PM

Harbormaster failed remote builds in B21735: Diff 26391!

update

Harbormaster returned this revision to the author for changes because remote builds failed.Nov 25 2020, 3:58 PM

Harbormaster failed remote builds in B21754: Diff 26418!

update

Harbormaster returned this revision to the author for changes because remote builds failed.Nov 25 2020, 10:25 PM

Harbormaster failed remote builds in B21807: Diff 26488!

test multi run scheduler
get rid of run_key on ticks table
store multiple run_ids instead of single run_id

Harbormaster returned this revision to the author for changes because remote builds failed.Dec 1 2020, 3:45 AM

Harbormaster failed remote builds in B21911: Diff 26606!

update cron scheduler

Harbormaster completed remote builds in B21913: Diff 26608.Dec 1 2020, 5:02 AM

prha requested review of this revision.Dec 1 2020, 5:02 AM

prha edited the summary of this revision. (Show Details)Dec 1 2020, 5:27 AM

prha added reviewers: dgibson, schrockn.

prha added a reviewer: sashank.

accepting but we should probably sort out the range query thing before landing

python_modules/dagster-graphql/dagster_graphql/schema/jobs.py
35	this is O(n) sql queries in the number of runs, do we anticipate sensors returning lots of runs?
python_modules/dagster-graphql/dagster_graphql/schema/schedules/ticks.py
4–6	does whatever UI this is powering need to be updated? Technically after your work it's possible to have a success tick but no first run Id right?
python_modules/dagster/dagster/cli/api.py
593	as discussed offline this should probably wait until all runs are created? We don't need to be as careful for this path though since we don't have the same failure recovery guarantees
python_modules/dagster/dagster/core/definitions/job.py
59	sensor/schedule?
66	i missed that this is now required, excellent
python_modules/dagster/dagster/core/definitions/schedule.py
65–81	should we indicate that some of these are deprecated now
python_modules/dagster/dagster/core/storage/schedules/sql_schedule_storage.py
155–172	as discussed offline it seems super important that the query we are replacing this with be possible without a full table scan on run storage - that seems blocking for landing this so that existing schedule runs on master doesn't slow to a crawl on large run DBs
python_modules/dagster/dagster/scheduler/scheduler.py
54	oops
315	if we're going to show run key in dagit for sensors should we also show this? Maybe in a less gross-looking format / in the actual execution timezone? Shouldn't block this massive diff though of course
317–322	this is what we need to make efficient looks like
python_modules/dagster/dagster_tests/scheduler_tests/test_scheduler_failure_recovery.py
69	Should we include how many runs? Maybe their IDs?

This revision is now accepted and ready to land.Dec 1 2020, 6:00 PM

comments

i'll let dgibson handle the rest of this, but i'm really excited to see this api consolidation with sensors

python_modules/dagster/dagster_tests/scheduler_tests/test_scheduler_run.py
196–203	really exciting to see this

Harbormaster failed remote builds in B21972: Diff 26680!Dec 1 2020, 9:31 PM

fix check for wrong config

Harbormaster completed remote builds in B21985: Diff 26693.Dec 1 2020, 9:58 PM

roll up last run key

Harbormaster completed remote builds in B22013: Diff 26726.Dec 2 2020, 1:00 AM

Closed by commit R1:5a662977dfb0: [sensors-10] schedule def new API (authored by prha). · Explain WhyDec 2 2020, 1:04 AM

This revision was automatically updated to reflect the committed changes.

prha added a commit: R1:5a662977dfb0: [sensors-10] schedule def new API.

[sensors-10] schedule def new APIClosedPublicActions

Details

Diff Detail

Event Timeline

Revision ContentsChangeset List

Diff 26727

js_modules/dagit/src/schedules/ScheduleUtils.tsx

js_modules/dagit/src/schedules/types/RepositorySchedulesFragment.ts

js_modules/dagit/src/schedules/types/SchedulerRootQuery.ts

js_modules/dagit/src/schedules/types/SchedulesRootQuery.ts

js_modules/dagit/src/schema.graphql

python_modules/dagster-graphql/dagster_graphql/schema/jobs.py

python_modules/dagster-graphql/dagster_graphql/schema/schedules/ticks.py

python_modules/dagster-graphql/dagster_graphql_tests/graphql/test_sensors.py

python_modules/dagster/dagster/api/snapshot_sensor.py

python_modules/dagster/dagster/cli/api.py

python_modules/dagster/dagster/cli/sensor.py

python_modules/dagster/dagster/core/definitions/job.py

python_modules/dagster/dagster/core/definitions/schedule.py

python_modules/dagster/dagster/core/definitions/sensor.py

python_modules/dagster/dagster/core/host_representation/external_data.py

python_modules/dagster/dagster/core/host_representation/repository_location.py

python_modules/dagster/dagster/core/instance/__init__.py

python_modules/dagster/dagster/core/scheduler/job.py

python_modules/dagster/dagster/core/storage/schedules/base.py

python_modules/dagster/dagster/core/storage/schedules/schema.py

python_modules/dagster/dagster/core/storage/schedules/sql_schedule_storage.py

python_modules/dagster/dagster/core/telemetry.py

python_modules/dagster/dagster/grpc/impl.py

python_modules/dagster/dagster/grpc/server.py

python_modules/dagster/dagster/grpc/types.py

python_modules/dagster/dagster/scheduler/scheduler.py

python_modules/dagster/dagster/scheduler/sensor.py

python_modules/dagster/dagster/utils/test/schedule_storage.py

python_modules/dagster/dagster_tests/api_tests/test_api_snapshot_schedule_execution_data.py

python_modules/dagster/dagster_tests/api_tests/test_api_snapshot_sensor.py

python_modules/dagster/dagster_tests/api_tests/test_launch_scheduled_execution.py

python_modules/dagster/dagster_tests/core_tests/definitions_tests/test_decorators.py

python_modules/dagster/dagster_tests/scheduler_tests/test_scheduler_failure_recovery.py

python_modules/dagster/dagster_tests/scheduler_tests/test_scheduler_run.py

python_modules/dagster/dagster_tests/scheduler_tests/test_scheduler_timezones.py

python_modules/dagster/dagster_tests/scheduler_tests/test_sensor_failure_recovery.py

python_modules/dagster/dagster_tests/scheduler_tests/test_sensor_run.py

[sensors-10] schedule def new API
ClosedPublic
Actions

Revision Contents
Changeset List

python_modules/dagster/dagster/core/instance/init.py