microsoft_defender_endpoint: fix handling of empty array fields - #9338
Merged
Conversation
efd6
added
Integration:microsoft_defender_endpoint
efd6
force-pushed
the
9320-microsoft_defender_endpoint
branch
from
March 12, 2024 05:49
4a2e904 to
ab343bd
Compare
When the evidence field in the input is a zero length array some processors fail due to direct access of subfields. It appears that sometimes this field is sent as an array rather than an object when empty, rather than as a null. So remove all empty arrays and objects at the beginning of the pipeline.
efd6
force-pushed
the
9320-microsoft_defender_endpoint
branch
from
March 12, 2024 05:53
ab343bd to
1d05cf5
Compare
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @efd6 |
|
0.0% Duplication on New Code
efd6
marked this pull request as ready for review
March 12, 2024 06:52
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
Package microsoft_defender_endpoint - 2.24.1 containing this change is available at https://epr.elastic.co/search?package=microsoft_defender_endpoint |
gizas
pushed a commit
that referenced
this pull request
Mar 13, 2024
When the evidence field in the input is a zero length array some processors fail due to direct access of subfields. It appears that sometimes this field is sent as an array rather than an object when empty, rather than as a null. So remove all empty arrays and objects at the beginning of the pipeline.
qcorporation
pushed a commit
that referenced
this pull request
Feb 3, 2025
When the evidence field in the input is a zero length array some processors fail due to direct access of subfields. It appears that sometimes this field is sent as an array rather than an object when empty, rather than as a null. So remove all empty arrays and objects at the beginning of the pipeline.
qcorporation
pushed a commit
that referenced
this pull request
Feb 4, 2025
When the evidence field in the input is a zero length array some processors fail due to direct access of subfields. It appears that sometimes this field is sent as an array rather than an object when empty, rather than as a null. So remove all empty arrays and objects at the beginning of the pipeline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
When the evidence field in the input is a zero length array some processors fail due to direct access of subfields. It appears that sometimes this field is sent as an array rather than an object when empty, rather than as a null. So remove all empty arrays and objects at the beginning of the pipeline.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots