2 ms·
> The biggest lie I have seen across databases is actual time travel for your data. Or in other words given a date and time in the past it gives you what the da
by lumost 5y ago
> The biggest lie I have seen across databases is actual time travel for your data. Or in other words given a date and time in the past it gives you what the data was then.
I worked at a company where we built this for our internal HBase clusters. Given any timestamp (or even better a commit ID) we could restore the cluster to that point in time. This was done through a combination of backing up the store files + write ahead logs. As I recall we had a retention limit for how much time we could do this for - but they were high enough for all of the "oh crap" moments.
- pengaru 5y agoThat seems like it would burn a lot of space on store file snapshots to replay the relevant WAL atop. Did they integrate with an underlying filesystem's snapshotting feature to make the store file snapshots differentials, or was that also implemented in the database? Or just threw space at the problem?