o365: Set subobjects false to conflict fields #13925
Merged
Conversation
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
chemamartinez
added
Integration:o365
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Contributor
|
/test |
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
audit |
2114.16 | 1404.49 | -709.67 (-33.57%) | 💔 |
To see the full report comment with /test benchmark fullreport
💚 Build Succeeded
History
|
|
efd6
approved these changes
May 18, 2025
|
Package o365 - 2.15.2 containing this change is available at https://epr.elastic.co/package/o365/2.15.2/ |
anupratharamachandran
pushed a commit
to anupratharamachandran/integrations
that referenced
this pull request
Jun 2, 2025
Fix a mapping conflict in Elasticsearch when ingesting documents with the Parameters or ModifiedProperties fields. These fields may sometimes be strings or arrays of strings instead of objects, which conflicts with the existing mapping that defines them as objects. Once a document with an object-type field is ingested, Elasticsearch will reject subsequent documents where the same field is of a different type. To resolve this, the PR sets subobjects: false in the mapping for these fields. This change allows Elasticsearch to handle both object and non-object values for these fields without triggering a mapping conflict.
5 tasks
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
Fix a mapping conflict in Elasticsearch when ingesting documents with the
ParametersorModifiedPropertiesfields. These fields may sometimes be strings or arrays of strings instead of objects, which conflicts with the existing mapping that defines them as objects. Once a document with an object-type field is ingested, Elasticsearch will reject subsequent documents where the same field is of a different type.To resolve this, the PR sets
subobjects: falsein the mapping for these fields. This change allows Elasticsearch to handle both object and non-object values for these fields without triggering a mapping conflict.Checklist
changelog.ymlfile.