-
Notifications
You must be signed in to change notification settings - Fork 577
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
Add filter to skip some entities on topology recovery #383
Comments
Per discussion with @michaelklishin, an interface with N filter methods each taking an SMI/lambda will do. |
To clarify: there will be one filter for entity type (queues, exchanges, etc) since having a single lambda without pattern matching will require ugly and error prone switch statements many users would probably rather avoid. |
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Topology recovery is all-or-nothing right, there's no way to tweak it. Being able to skip the recovery of some entities could be useful in very specific cases: #382. There's already a way to remove some queues from the recorded queue list: #346. What is considered in this issue is a filter that could be set in the
ConnectionFactory
.It could be something like this in
4.x.x
:It would be a
Predicate<? extends RecordedEntity>
in 5.x.The text was updated successfully, but these errors were encountered: