influxdb/generated_types
Marco Neumann a5fc1c7d38 fix: collect min AND max in database checkpoints
This is required to correctly handle the following case:

1. There are two partitions A and B w/ a single write each (from the same
   sequencer).
2. We persist A:
   - The partition checkpoint for A will be empty because after persistence
     there will be nothing to replay (the single write is persisted and
     we're ready).
   - The database checkpoint that contains the global minimum of all ranges
     recognizes that for the sequencer there is indeed something left (the
     minimum sequence number from B).
3. DB restart happens, replay starts
4. We scan all persisted files, figure out that we have a DB checkpoint
   with a sequence minimum but (w/o the change in this commit) there is no
   maximum. Only partition checkpoints contain maxima, and the only partition
   checkpoint that was persisted was the one for partition A and that one was
   empty (see above).
5. So now how do we recover partition B?
2021-07-21 14:48:29 +02:00
..
protos fix: collect min AND max in database checkpoints 2021-07-21 14:48:29 +02:00
src chore: update parquet_cache_limit to u64 and 0 for default 2021-07-20 15:41:06 -04:00
.gitignore feat: Check in generated WAL flatbuffers code 2021-03-22 09:38:59 -04:00
Cargo.toml refactor: default to num_cpu 2021-07-19 14:00:10 +01:00
build.rs refactor: remove now unused chunk sort order (#1854) 2021-07-01 16:39:45 +00:00