-
-
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
Allow stream "republish" to republish multiple subjects #5269
Comments
Why not use a filtered mirror? |
I'll add more detail to the use case cause I see now I didn't add enough info, I also want to be able to publish messages directly to this other stream (due to legacy systems) which eliminates mirroring. |
Sourced streams can have messages from other streams and their own subjects.. |
Definitely! The reason I was trying to use
Once the streams are created, I follow these steps:
|
For any stream, its default behavior is to pub ack once the message is committed, but only if you supply a reply subject for the server to send it to. Meaning in your example above (step 2) if you did You can turn that behavior off. For instance if the reply subject has prior semantic meaning from an existing system but you want to capture those messages in a stream. Create the stream, then do |
Hmmm...I tried setting But even if that worked, we don't want to use |
Let's switch to a video call to discuss. Feel free to shoot me an email: derek@synadia.com |
|
Proposed change
Make stream
republish
a list instead of an objectUse case
I am trying to forward specific subjects from one stream to another and the current subject architecture doesn't allow for wildcard manipulation. An example:
The stream subjects:
hello.a
hello.b
hello.c
I want to republish
hello.a -> world.a
andhello.b -> world.b
but not republishhello.c
There's currently no way to do the above since republishing
hello.*
would includehello.c
and I specifically do not want to republish that subject.I also want to be able to publish messages directly to this new stream so using a
mirror
doesn't work for this use case.Contribution
I'm interested in contributing if accepted.
The text was updated successfully, but these errors were encountered: