You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a fault tolerant (FT) Feldera pipeline, the division of input into steps must be durable (see https://github.com/feldera/dist-design?tab=readme-ov-file#inputoutput-synchronization). To achieve that, we require that each FT input connector have its own way for it to record the division into steps persistently. We only have a single FT input connector now, for Kafka.
Speculatively, we think that it will be difficult for some users to be able to add extra Kafka topics for recording input division. There can be a separate team that admins the Kafka broker, which might need to approve new topics.
In the presence of multiple FT pipelines that use the same Kafka topics for input, we will need some way to invent unique names for recording the divisions. (Probably a minor problem on its own but it would exacerbate the problem if it's difficult to add Kafka topics at all.)
This design suits the Kafka FT input connector, since Kafka provides write access, but it doesn't extend to read-only input connectors like the URL connector. For FT support, those connectors would need to add some log on the side.
For a fault tolerant (FT) Feldera pipeline, the division of input into steps must be durable (see https://github.com/feldera/dist-design?tab=readme-ov-file#inputoutput-synchronization). To achieve that, we require that each FT input connector have its own way for it to record the division into steps persistently. We only have a single FT input connector now, for Kafka.
Problems:
The proposal, then, is to add a new database or log to record the division of input. The goal of this issue is for the design of such a log. See https://github.com/feldera/dist-design?tab=readme-ov-file#inputoutput-synchronization for further background and contraints.
The text was updated successfully, but these errors were encountered: