Tue, Oct 20
should we track the API change in a GH issues somewhere?
I think the textarea could be a little beginner-friendly in terms of the syntax, but we can iterate and see what folks think
This looks good!
I kind of like the codemirror idea... and having yaml removes the requirement to learn another DSL.
Code looks okay, but hitting lots of merge conflicts... Req'ing for rebase.
update doc, messages
remove test for removed migration
Mon, Oct 19
rebase, add more logging to migration script
remove hard-coded version check
update, share secondary_indexes table across run, event_log storage.
Still doesn't seem possible to set subset selection for the partitions with no runs. Is that going to be part of this diff?
Yeah, I think this looks reasonable. Let's add some tests to document the behavior we're going for?
Fri, Oct 16
add cli argument to iterate through list of reindex migrations
fix super signature
build upon D4800, use secondary index to track asset key table migration
Thu, Oct 15
rebase for k8s pin
refactor asset UI into root catalog, and a matching page, which first checks for exact asset key matches, and then falls back to a prefix search
Wed, Oct 14
remove counter (thanks @max!!)
use postgres upsert
Tue, Oct 13
Mon, Oct 12
Hmm, I'm not sure there's a reason for it to go to stderr... but it's been that way forever.
Sep 20 2020
Sep 18 2020
update to use admin key for api key