Research how durations are getting serialized

[travjenkins]

Question

How are durations getting serialized and handled? Does rust vs go connectors matter? Are there limitations, etc. Also, can we update interval (and possibly ALL durations?) to use something like the duration format to make the spec more explicit.

Background

The interval property in the capture spec is not exactly what it seems if you just read the spec. It has a pattern of ^\d+(s|m|h)$ . However, when the spec is submitted the server will serialize the value to a different pattern. This means that the UI and users have to manage this conversion.

Related

UI task - estuary/ui#1194

Spec

interval
string ∪ null

Configured intervals are applicable only to connectors which are unable to continuously tail their source, and which instead produce a current quantity of output and then exit. Flow will start the connector again after the given interval of time has passed. Intervals are relative to the start of an invocation and not its completion. For example, if the interval is five minutes, and an invocation of the capture finishes after two minutes, then the next invocation will be started after three additional minutes.

Pattern: ^\d+(s|m|h)$