Page MenuHomeElementl

Clarify dagster/priority docs
ClosedPublic

Authored by johann on Mar 25 2021, 12:51 PM.

Details

Summary

Docs previously stated that priority tags should be ints- rather, they should be ints converted to strings. Added examples to help

Test Plan

make dev

Diff Detail

Repository
R1 dagster
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

docs/content/deployment/run-coordinator.mdx
63โ€“64

better wording?

sashank added inline comments.
docs/content/deployment/run-coordinator.mdx
63โ€“64

Took a pass, might be helpful:

The run queue is a first-in-first-out priority queue. By default, all runs have a priority of 0. Dagster will launch runs with higher priority first. If multiple runs have the same priority, Dagster will launch the runs in the order you submitted them to the queue. Negative priorities are also allowed and are useful for de-prioritizing sets of runs such as backfills. Priority values must be integers.

You can specify a custom priority using the dagster/priority tag, which you can set in code on definitions or in the Dagit playground. Note that because both tag keys and values must be strings, so you must specify the priority integer as a string. For example, if you wanted to specify a priority of -1, you would set the dagster/priority tag value to be the string "-1".

87โ€“99

Please make these literal includes and put them under test ๐Ÿ™

This revision is now accepted and ready to land.Mar 25 2021, 1:33 PM
This revision was landed with ongoing or failed builds.Mar 25 2021, 2:25 PM
This revision was automatically updated to reflect the committed changes.