-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove subject_transform_dest
#4557
Remove subject_transform_dest
#4557
Conversation
…ce (config and info) see nats-io/nats-server#4557
…ce (config and info) see nats-io/nats-server#4557
If someone has a stream that had this configured and that was saved into the stream config on disk, what happens to them? |
…ce (config and info) see nats-io/nats-server#4557
This is a safer (less lines of code touched) alternative to #4557 for now, which simply ignores the `subject_transform_dest` field in the API and the stream assignments. We'll still look to merge the other PR to clean up but will do so post-release when we have more time to test it. Signed-off-by: Neil Twigg <[email protected]>
…ce (config and info) see nats-io/nats-server#4557
Co-authored-by: Jean-Noël Moyne <[email protected]> Co-authored-by: Neil Twigg <[email protected]> Signed-off-by: Neil Twigg <[email protected]>
f336a31
to
9fc2603
Compare
Rebased on top of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - if tests pass.
subject_transform_dest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now that the TestJetStreamFilteredSubjectUsesNewConsumerCreateSubject
test exists and passes.
Removes the single subject transform destination field any subject transformation in StreamSources must now be done using the SubjectTransforms array instead.