1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
use crateHardwareCounterCell;
use crateSortedSlice;
use cratePointOffsetType;
use crateOperationResult;
/// Common live-reload surface shared by the read-only, gridstore-backed stores —
/// the read-only field-index variants and the read-only payload storage.
///
/// A read-only store is opened over a [`UniversalRead`] backend while a writer
/// keeps appending to the same files. `live_reload` refreshes the in-memory
/// view to the current on-disk state without a full re-open. Implementers fall
/// into a few shapes:
///
/// - immutable mmap field-index variants only re-apply the authoritative
/// `deleted_points` to their in-memory deletion bitmap — `fs` and
/// `new_points` are unused because no on-disk state changes after build;
/// - appendable gridstore field-index variants reload the backing storage
/// through `fs`, drop `deleted_points` from the in-memory index, then ingest
/// `new_points` from the refreshed storage view;
/// - stores with no separate in-memory index (e.g. the payload storage) only
/// reload the backing storage through `fs`; deletions and newly written
/// points are served straight from the refreshed gridstore, so
/// `deleted_points` / `new_points` are unused.
///
/// `deleted_points` / `new_points` are supplied by the caller (typically the
/// segment's id-tracker diff accumulated since the previous reload).
///
/// [`UniversalRead`]: common::universal_io::UniversalRead
pub