Tim Fox
Tim Fox
Sinks will allow the output from materialized views or sources to be sent to a Kafka topic. Similarly to sources, they will be declared using a CREATE SINK command. Something...
We currently use the default Pebble config. We should set config and tune it appropriately for our usage. Looking at the config settings that Dragonboat uses for Pebble would be...
Each shard has a 1-1 correspondence with a Raft group. We have R replicas of each shard (including the leader), where R is the replication factor. The leader replica for...
We should allow for periodic snapshots to be taken of the shards, either written to the filesystem or pushed to S3.
This PR enables out of band pull queries. Previously we were executing all pull queries through raft as linearizable reads. This didn't buy us anything as our data is effectively...
TiDB has a lot of interesting JSON functions (which come from MySQL). We don't currently support the JSON type so these are disabled but we should consider implementing the JSON...
There is some unused / over-complex stuff in the ex-TIDB planner code. In particular LogicalDataSource is over complex and could be simplified.
A Prana node is subject to certain limits - usually imposed by the hardware or devices. Examples are CPU processing, disk write throughput, disk read throughput, iops, network bandwidth etc....
Currently, Prana ingests events solely from Kafka topics. This requires a Kafka broker to be setup to receive the events. In some installations it would be nice if a client...