Need a way for the UI to allow users to do a full proper "backfill"
Before implementing this we need to see if it is technically easier to pull this off by adding it to the details page OR work it into the existing flows.
Notes from UI/UX
The batch script is not 100% correct and incorrect in small ways that are not huge. This is a good basis for making the final script
The core workflow is:
Capture - Disable
Capture - Publish
Runtime must stop 100% and is done writing documents (wait for publication to succeed and then wait… or keep looking for shards)
(IMPORTANT) - save current time
Bindings - update backfill property
Capture - enable
Materialization - update notBefore property
Capture & Materialization - Publish
Maybe still add a CTA next to backfill all button that tells the user to go to this flow.
Original Notes
Control plane:
Extend automatic backfills to the collection level
Change it so that it first disables the capture and then does what it currently does in two publications
Turn it into a script that the UI could call to initiate a backfill when the user is in the loop
UI:
New button on the the binding and capture level in the edit ui for captures next to "Backfill" that is called "Reset Dataflow" and calls the script as a cloud function.
Overview
Need a way for the UI to allow users to do a full proper "backfill"
Before implementing this we need to see if it is technically easier to pull this off by adding it to the details page OR work it into the existing flows.
Notes from UI/UX
The batch script is not 100% correct and incorrect in small ways that are not huge. This is a good basis for making the final script
The core workflow is:
notBeforepropertyMaybe still add a CTA next to backfill all button that tells the user to go to this flow.
Original Notes
Control plane:
UI: New button on the the binding and capture level in the edit ui for captures next to "Backfill" that is called "Reset Dataflow" and calls the script as a cloud function.