Simon
Simon
Currently the `/suspend` endpoint performs the shutdown by itself. Instead, add a `Suspended` and possibly `Suspending` state. The `Suspended` state is also a desired state. Once transitioned, it by itself...
The Web Console is able to display statistics of tables and views with connectors as it aggregates (add together) across the connectors of a table/view and shows those numbers. However,...
Addition of a pipeline interaction endpoint which shows: - Any errors the connector has experienced but was able to resolve (e.g., temporarily disconnected) - Parsing errors
The pipeline HTTP server has grown to have quite some endpoints. A rework is necessary in several aspects: - Split off pipeline status monitoring from `/stats` - Connector status monitoring...
The Python client methods should use generous timeouts for their operation, for example such that a script that runs `start()` doesn't wait indefinitely for a pipeline to move from `Initializing`...
Currently the API server does enforce a timeout for the requests it issues itself, which indirectly enforces a timeout for the client as well when it proxies a request on...
The pipeline lifecycle documentation (https://docs.feldera.com/pipelines/lifecycle#runtime-status-diagram) currently is missing the runtime status diagram. Notes: - It should account for current runtime status (/deployment id) being written in storage or not, and...