-
Notifications
You must be signed in to change notification settings - Fork 474
cloudflare: drop empty event sets #5406
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
Conversation
e680107
to
0ba3d74
Compare
🌐 Coverage report
|
@@ -10,6 +10,8 @@ processors: | |||
- json: | |||
field: event.original | |||
target_field: json | |||
- drop: | |||
if: ctx.json?.result != null && ctx.json.result.isEmpty() |
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.
Not sure if this ever happens?
Shouldn't the event be dropped even if result object is null ?
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.
From the issue, the empty case has a result: []
. If we drop when result == null
we will lose all documents since the actual events don't have a result
field.
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
Package cloudflare - 2.4.1 containing this change is available at https://epr.elastic.co/search?package=cloudflare |
What does this PR do?
Drop empty event sets.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots