Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support for query/reply messages to Downsampling #1797

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

oteffahi
Copy link
Contributor

@oteffahi oteffahi commented Feb 26, 2025

Adds query/reply message filters to Downsampling interceptor. Query/reply message types are respectively named "query" and "reply", with the addition of "push" which is the previously supported Publication message type.

Also changes Downsampling config to accept a list of flows instead of a single one, to limit the need to duplicate a downsampling conf for query/reply messages which go in opposite flows.

Note that this PR breaks compatibility with previous format of Downsampling configuration.

In the current implementation, rules within the same Downsampling
config share the same state if configured on the same keyexpr.
Having message types within the rules can lead users to configure
different messages types within different rules with same keyexpr,
which would produce the same result as having all message types
within the same rule, i.e downsampling on the whole set of messages
instead of doing so seperately for each type.
@oteffahi oteffahi self-assigned this Feb 26, 2025
Copy link

PR missing one of the required labels: {'dependencies', 'bug', 'new feature', 'internal', 'enhancement', 'breaking-change', 'documentation'}

@oteffahi oteffahi added new feature Something new is needed breaking-change Indicates that the issue implies a breaking change (be it at compile time or at runtime) labels Feb 26, 2025
@oteffahi
Copy link
Contributor Author

oteffahi commented Feb 26, 2025

Clarification regarding my commit message for 963eb84: two rules on the same keyexpr would have the last rule in the list overwrite the previous one, which further supports why message types need to be moved out of the rules list.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
breaking-change Indicates that the issue implies a breaking change (be it at compile time or at runtime) new feature Something new is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant