-
Notifications
You must be signed in to change notification settings - Fork 227
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
feat: drop messages for which datalog doesn't exists #719
base: main
Are you sure you want to change the base?
Conversation
// Create a dynamic filter if dynamic_filters are enabled for this connection | ||
let filter_idxs = match filter_idxs { | ||
Some(v) => v, | ||
None if connection.dynamic_filters => { | ||
if filter_idxs.is_empty() { | ||
// Create a dynamic filter if dynamic_filters are enabled for this connection | ||
if connection.dynamic_filters { | ||
let (idx, _cursor) = datalog.next_native_offset(topic); | ||
vec![idx] | ||
filter_idxs = vec![idx]; | ||
} else { | ||
warn!(topic, "no datalog found for topic, dropping message"); |
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.
hmm with this we would be returning (0, 0)
would that be valid?
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.
it was the existing behaviour, so didn't change it. If we return error, we have to add a check again so we don't disconnect the client.
Type of change
Checklist:
cargo fmt
CHANGELOG.md
if it's relevant to the users of the library. If it's not relevant mention why.