Ben Johnson
Ben Johnson
LiteFS currently only supports the rollback journal, however, it should also be able to convert WAL writes to LTX files as well.
Ideally, it'd be nice to support the creation or replacement of a database with simple file commands. e.g. ```sh cp /path/to/src.db /mnt/target.db ```
As LiteFS is a database replication tool, test coverage should be high—likely 80-90% test coverage. Some areas of LiteFS may be difficult to report test coverage around such as the...
LiteFS currently handles the `DELETE` rollback journal mode. It should also handle `PERSIST` & `TRUNCATE`.
[A comment on HN](https://news.ycombinator.com/item?id=32242742) had an interesting idea of having the primary walled off from the other nodes and having the primary reach out to replicas instead of replicas connecting...
The LTX file format is designed to store optional event data (similar to [SSE](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events)) for each transaction file. This can be useful as replicas may need to know when and...
LTX files are designed to support encryption so that remote storage, such as AWS S3, will not be able to read the underlying data. Currently, I'm leaning toward using AES-GCM-SIV...
While LiteFS is mostly a passthrough file system, it'd be good to run the SQLite test suite against it to verify correctness. Most of the test suite does not test...
Currently, replicas will automatically obtain the lease quickly after the primary shuts down. However, this incurs a small window of downtime. We can remove this window by having the primary...
I was having trouble pushing up some minor changes to #414 so I'm just creating a new PR instead. /cc @hifi