Page MenuHomePhabricator

Basic implementation of search through run history

Authored by bengotow on Sep 9 2019, 10:32 PM.


Group Reviewers
Restricted Project
R1:c827de8558d8: Basic implementation of search through run history

This diff adds a basic search bar to the runs list that searches pipeline name, mode,
and stepsToExecute (if present.) I'm planning to add autocompletion / tokenization in
a stacked diff.

This also includes a small GraphQL interface change - the type of stepKeysToExecute
was (string | null)[] | null which isn't quite right. If it's present, the elements
are non-null strings. Updated the dauphin representation and checked that it's now
(string | null)[]

Test Plan

Run tests

Diff Detail

R1 dagster
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

bengotow created this revision.Sep 9 2019, 10:32 PM
schrockn requested changes to this revision.Sep 9 2019, 11:23 PM
schrockn added a subscriber: schrockn.

can we also search for run id?

This revision now requires changes to proceed.Sep 9 2019, 11:23 PM

Sure! Don't see why not. While I'm at it I'll make it so this search field can be populated from the query string - If there's some other place people are copy-pasting runIds from, it'd be cool to switch to a dagit link.

bengotow updated this revision to Diff 4703.Sep 13 2019, 2:58 PM

Make runId searchable, support /runs?q=<term> so nobody is copy-pasting runIds

bengotow updated this revision to Diff 4707.Sep 13 2019, 4:04 PM


prha accepted this revision.Sep 13 2019, 10:36 PM
prha added a subscriber: prha.


schrockn accepted this revision.Sep 16 2019, 3:48 PM
This revision is now accepted and ready to land.Sep 16 2019, 3:48 PM