@cloudbitmaps/roaring 0.11.1 → 0.11.2

package/dist/index.d.ts

@@ -72,7 +72,8 @@ export interface CloudRoaringOptions {
      * read the registry or list the bucket directly (`exists`, `segments`, `generations`, `getRetention`, and the
      * registry scan `subjectReport`, `exportSegments` and `checkConsistency` start from): they report a transient fault to their caller, because a conditional write that lands and then loses its response would, replayed,
      * report its own write as a conflict. Pass a partial policy to tune it — anything you leave out keeps its
-     * default — or `false` to turn the read retry off (e.g. if your injected client already retries).
+     * default — or `false` to turn the read retry off (e.g. if your injected client already retries). A GCS download is retried by
+     * the GCS driver whatever this says.
      * Deterministic errors (`ValidationError`/`IntegrityError`/`WriteConflictError`/…) are never retried by this
      * layer.
      */
@@ -139,7 +140,7 @@ export interface CacheOptions {
     /**
      * Aggregate byte ceiling on the parsed `.crbm` indices the open readers hold (default 64 MiB) — the byte half
      * of the memory bound, complementing the {@link CacheOptions.readerMax} *count* bound. A wide/dense segment's
-     * parsed index can be several MB, so a count-only bound could let the open readers pin ~GBs and blow a small
+     * parsed index can reach about 1.3 MB, so a count-only bound could let the open readers pin over a GB and blow a small
      * heap (e.g. a 128 MB Lambda); this evicts the least-recently-used reader once the summed index footprint
      * would exceed the ceiling — whichever of the count/byte bounds binds first. Lower it for memory-tight
      * deployments that read across wide segments. Applies whenever the store builds its own read path.