1
83%
main: 83%

Ran 07 Aug 2025 05:55AM UTC

Files 59

Run time 3s

Badge

Embed ▾

Committed 05 Aug 2025 10:22AM UTC coverage: 85.894% (-0.02%) from 85.911%

Job # 16795446610.1

Build Type

push

github

Committed by

web-flow

Commit Message

(2.12) Atomic batch: support `Nats-Expected-Last-Sequence`, `Nats-Rollup`, `DiscardNew` (#7119)

Add support for the `Nats-Expected-Last-Sequence` and `Nats-Rollup`
headers for batching, as well as `DiscardNew` support.

To do this we need to be able to fully rely on clustered-level
consistency checks, such that followers will always apply them and never
call `bumpCLFS()`. Just a few cases remain, but these should not be
problematic. Now we can rely on `mset.clseq - mset.clfs` to be what the
highest last sequence is going to be, which can then be compared in
consistency checks.

`Nats-Rollup` additionally has some batch-specific consistency checks:
- `Nats-Rollup: all` is allowed only on the first message. Using it on
any later message would mean you'd be purging data at the start of the
batch.
- `Nats-Rollup: sub` is only allowed on the first message of a specific
subject. If allowed on a later message with the same subject, that would
mean you'd be purging data at the start of the batch. This means we can
allow rolling up multiple subjects in the batch at once.

Resolves https://github.com/nats-io/nats-server/issues/6975

Signed-off-by: Maurice van Veen <github@mauricevanveen.com>

Coverage Stats

71684 of 83456 relevant lines covered (85.89%)

358869.36 hits per line

nats-io / nats-server / 16795446610 / 1
83%
main: 83%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16795446610.1

nats-io / nats-server / 16795446610 / 1 83% main: 83%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16795446610.1

nats-io / nats-server / 16795446610 / 1
83%
main: 83%

README BADGES
x