• instead of making it an extra arg, we use the existing solid_subset: execute_pipeline(pipeline, solid_subset=['*some_solid', 'other_solid_a', 'other_solid_b+'])
• more tests to cover multiple clauses (disjoint, overlapping) and invalid queries

• get_solid_subset_from_query(pipeline_def, query) where query is str => parse_solid_subset(pipeline_def, solid_subset) where solid_subset is List[str]
• dedup
• more tests to cover multiple clauses, invalid syntax, and duplication

up

up

@max i can maybe make the input a multi-select dropdown so it won't get too crowded for many tags. but gonna land this now cos the iteration of this isn't a blocker for 0.8.0

merged into feature branch https://dagster.phacility.com/D3015

up

add test

One last thing that may not feel cohesive is that the filter won't follow the changes in the DSL selector. issue: https://github.com/dagster-io/dagster/issues/2472

rebase

lg2m. shall we do the same to "Open in Playground..."?

rebase

update snapshot

up

1. the selector syntax is linked to all types of step selection:
2. single click: stepKey
3. double click: *stepKey*
4. type in the selector
5. Have a checkbox which optionally hides unselected steps. The default should be to show all steps.

up

I think it makes sense to return a group where ANY child runs that can be applied to the filter, rather than a group where ALL child runs or the root applied. -- thinking about the email filter machinery: it shows the entire thread as long as there's one message matches the filter. also, it could be very real that I filter "status: failure" and I expect to see all the groups where at least one child run failed.

up

back to you queue. all look good. lets rebase and then make the tests green