How to properly declare subjectTransforms for KeyValue buckets #274
Unanswered
ricker-flow
asked this question in
Q&A
Replies: 2 comments
-
|
Your transform doesn't look right. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Just FYI, I tried declaring it as a stream: apiVersion: jetstream.nats.io/v1beta2
kind: Stream
metadata:
name: KV_core-v2
spec:
name: KV_core-v2
storage: file
preventDelete: true
description: A single key value store for all core data
replicas: 2
sources:
- name: agreement
subjectTransforms:
- dest: KV_core-v2.node.>
source: agreement.*.*.>
- name: digital
subjectTransforms:
- dest: KV_core-v2.node.>
source: digital.*.*.>Did not work. NATS assumes the sources are buckets. > nats kv info core-v2
Handling connection for 4222
Information for Key-Value Store Bucket core-v2 created 2025-08-12T09:15:08-04:00
Configuration:
Bucket Name: core-v2
History Kept: 1
Values Stored: 0
Compressed: false
Backing Store Kind: JetStream
Description: A single key value store for all core data
Bucket Size: 0 B
Maximum Bucket Size: unlimited
Maximum Value Size: unlimited
Maximum Age: unlimited
JetStream Stream: KV_core-v2
Storage: File
Sources Information:
Source Bucket: physical
Last Seen: never
Lag: 0
Source Bucket: service
Last Seen: never
Lag: 0
Source Bucket: predicate
Last Seen: never
Lag: 0
... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I want to create a KV bucket that is a subject transform of several streams. I created the following resource. The bucket appears in the cluster but it is not being populated.
Beta Was this translation helpful? Give feedback.
All reactions