Orchestration (in the sense.... Order of execution) of expectations in an expectations suite


I know Great Expectations has no intent to replace tools like Dagster, AirFlow, … but as a use case, we would be interested in running the expectations of an expectations suite in a given order.

That way we could simply, NOT evaluate the other tests if expect_table_row_count_to_be_between(min_value=1) fails. That is an obvious useful example for many most probably and we can think of more complex relations between the expectations.

Just let us know if this could be on the roadmap or most probably “never” :wink:


@patechoc This is a great point. Eventually, the code that evaluates a suite will be “smart” enough to figure out these dependencies.