Workaround issue with missing dynamic mapping in tines package#12082
Merged
jsoriano merged 0 commit intoelastic:mainfrom Dec 16, 2024
Merged
Workaround issue with missing dynamic mapping in tines package#12082jsoriano merged 0 commit intoelastic:mainfrom
jsoriano merged 0 commit intoelastic:mainfrom
Conversation
andrewkroh
added
bugfix
🚀 Benchmarks reportTo see the full report comment with |
andrewkroh
added
the
Team:Security-Service Integrations
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
3 tasks
Member
Author
|
Fix in kibana: elastic/kibana#204104 |
efd6
approved these changes
Dec 15, 2024
Contributor
There was a problem hiding this comment.
nit
Also, please update the commit message body to work with non-markdown.
No dynamic mapping was being generated for
tines.audit_log.inputs.inputs.options.*, and this package uses the
tines.audit_log.inputs.inputs.options field directly, without having any
mapping for it or its sub-properties.
The workaround ensures that there is a mapping for
tines.audit_log.inputs.inputs.* that serves for
tines.audit_log.inputs.inputs.options as well as for its subobjects.
The configured dynamic mapping was not being generated due to some issue in
Fleet that we are investigating.
We detected this issue while refactoring field mappings tests in
elastic-package, more about this in elastic/elastic-package#2214[1].
[1]https://github.com/elastic/elastic-package/pull/2214#issuecomment-2536692641
💚 Build Succeeded
History
cc @jsoriano |
|
|
Package tines - 1.14.1 containing this change is available at https://epr.elastic.co/package/tines/1.14.1/ |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
…ic#12082) No dynamic mapping was being generated for tines.audit_log.inputs.inputs.options.*, and this package uses the tines.audit_log.inputs.inputs.options field directly, without having any mapping for it or its sub-properties. The workaround ensures that there is a mapping for tines.audit_log.inputs.inputs.* that serves for tines.audit_log.inputs.inputs.options as well as for its subobjects. The configured dynamic mapping was not being generated due to some issue in Fleet that we are investigating. We detected this issue while refactoring field mappings tests in elastic-package, more about this in elastic/elastic-package#2214[1]. [1]elastic/elastic-package#2214 (comment) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
…ic#12082) No dynamic mapping was being generated for tines.audit_log.inputs.inputs.options.*, and this package uses the tines.audit_log.inputs.inputs.options field directly, without having any mapping for it or its sub-properties. The workaround ensures that there is a mapping for tines.audit_log.inputs.inputs.* that serves for tines.audit_log.inputs.inputs.options as well as for its subobjects. The configured dynamic mapping was not being generated due to some issue in Fleet that we are investigating. We detected this issue while refactoring field mappings tests in elastic-package, more about this in elastic/elastic-package#2214[1]. [1]elastic/elastic-package#2214 (comment) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
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
4 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
No dynamic mapping was being generated for
tines.audit_log.inputs.inputs.options.*, and this package uses the
tines.audit_log.inputs.inputs.options field directly, without having any
mapping for it or its sub-properties.
The workaround ensures that there is a mapping for
tines.audit_log.inputs.inputs.* that serves for
tines.audit_log.inputs.inputs.options as well as for its subobjects.
The configured dynamic mapping was not being generated due to some issue in
Fleet that we are investigating.
We detected this issue while refactoring field mappings tests in
elastic-package, more about this in elastic/elastic-package#2214[1].
[1]elastic/elastic-package#2214 (comment)
Checklist
changelog.ymlfile.How to test this PR locally
logs-tines.audit_logs@packagecomponent template includes a dynamic mapping for these fields.Related issues