Liftbridge offers the option of pausing a stream (with some or all of its partitions) to reduce the amount of CPU and memory usage on idle streams. When that happens, every subscriber to a partition receives an error. Publishing to a paused partition will resume it, allowing it to function as before.
Our use-case includes a situation where we would like to read from a partition even if it is paused. It has to be resumed to do so, but we do not want to publish to it. We have found two possible options to do so: either provide an API to resume a stream/partition, or add a boolean to the subscription request to allow it to resume a partition instead of returning an error.
We are ready to create a PR with a working implementation of either options, but would like to know your opinion on this, @tylertreat.
Liftbridge offers the option of pausing a stream (with some or all of its partitions) to reduce the amount of CPU and memory usage on idle streams. When that happens, every subscriber to a partition receives an error. Publishing to a paused partition will resume it, allowing it to function as before.
Our use-case includes a situation where we would like to read from a partition even if it is paused. It has to be resumed to do so, but we do not want to publish to it. We have found two possible options to do so: either provide an API to resume a stream/partition, or add a boolean to the subscription request to allow it to resume a partition instead of returning an error.
We are ready to create a PR with a working implementation of either options, but would like to know your opinion on this, @tylertreat.