Skip to content
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

[Auditbeat] file.origin and file.origin.raw multi-fields are both keyword #12423

Closed
andrewkroh opened this issue Jun 4, 2019 · 1 comment · Fixed by #15630
Closed

[Auditbeat] file.origin and file.origin.raw multi-fields are both keyword #12423

andrewkroh opened this issue Jun 4, 2019 · 1 comment · Fixed by #15630

Comments

@andrewkroh
Copy link
Member

As of #10544 both file.origin and file.origin.raw are both keyword type. The idea behind having a multi-field is to allow one of the fields to be analyzed to help with searching.

To fix the issue we should remove file.origin.raw and add file.origin.text that is text. This would follow the ECS convention.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

adriansr added a commit to adriansr/beats that referenced this issue Mar 2, 2020
The `raw` part of the multifield was unnecessary because it was keyword
like the base field. Replaced with `file.origin.text` of type text as
ECS recommends.

Fixes elastic#12423
adriansr added a commit that referenced this issue Mar 3, 2020
)

The `raw` part of the multifield was unnecessary because it was keyword
like the base field. Replaced with `file.origin.text` of type text as
ECS recommends.

Fixes #12423
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants