ec0804900a
RoutingRules such as RoutingConfig and ShardConfig use a sink to decide where to write the entries. The write buffer is currently implemented in the `db` and is accessed by using the `write_local_entry` code path. This PR simply invokes that legacy code path whenever a "kafka" sink is selected. This allows us immediately to benefit from the ability of the ShardingConfig to select or reject tables and send some to kafka, some to devnull. This PR does not allow us yet to split an input batch into mulitiple shards and send each to a different kafka topic. For that, we'll need to pull out the write buffer code path out of the `db` and do something similar to a ConnectionManager but for write buffers. TODO |
||
---|---|---|
.. | ||
src | ||
Cargo.toml |