-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Mapping cleanup for Signals Migration Saved Object #154949
Conversation
These fields are captured in schema elsewhere (and validated there as well). This effort is part of @elastic/security-teamelastic#6268.
After deleting this field, test failures reminded me that we use this as a sortField when checking the migration status, so we need the field in some capacity. This previously worked despite the field being `index: false` because elasticsearch is able to sort on doc_values (https://www.elastic.co/guide/en/elasticsearch/reference/current/doc-values.html) However, in order to make this sorting more efficient, and because we'll never be able to remove `index: false` moving forward, I'm removing it here. This implicitly adds a mapping for this field.
💚 Build Succeeded
Metrics [docs]Saved Objects .kibana field count
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @rylnd |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
cc @rudolf |
Summary
These fields are captured in schema elsewhere (and validated there as well).
This effort is part of elastic/security-team#6268.