Skip to content

Conversation

@aricart
Copy link
Member

@aricart aricart commented May 5, 2025

Introduced markerTTL and per-message TTL options, allowing fine-grained control over retention policies. Updated KV methods, types, and tests to support these features, ensuring compatibility with streams enabling allow_msg_ttl.

aricart added 2 commits May 5, 2025 14:39
Introduced `markerTTL` and per-message TTL options, allowing fine-grained control over retention policies. Updated KV methods, types, and tests to support these features, ensuring compatibility with streams enabling `allow_msg_ttl`.

Signed-off-by: Alberto Ricart <[email protected]>
@aricart aricart requested a review from piotrpio May 6, 2025 15:46
aricart added 5 commits May 6, 2025 11:07
…t server seems to not honor the request, but doesn't return an error.

Signed-off-by: Alberto Ricart <[email protected]>
Copy link
Contributor

@piotrpio piotrpio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@aricart aricart merged commit 16a6c92 into main May 7, 2025
24 of 25 checks passed
@aricart aricart deleted the kv-ttl branch May 7, 2025 16:34
h.set(PubHeaders.ExpectedLastSubjectSequenceHdr, `${opts.previousSeq}`);
}
if (opts.ttl) {
const h = o.headers || headers();
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If o.headers isn't set, the newly created headers won't be attached to o on line 626, right?

@EvilaMany
Copy link

EvilaMany commented Aug 18, 2025

Can you do something so that it become available in nats.js package? It merged a couple of months ago, but still impossible to use it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants