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.

Sign up for GitHub

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

Jump to bottom

[Cases] Define source of truth for Elasticsearch data format #152756

Open
jonathan-buttner opened this issue Mar 6, 2023 · 2 comments
Open

[Cases] Define source of truth for Elasticsearch data format #152756

jonathan-buttner opened this issue Mar 6, 2023 · 2 comments
Labels
Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@jonathan-buttner
Copy link
Contributor

Now that the saved object mapping files do not include the fields that are not indexed its not easy to determine exactly what is stored in elasticsearch for each type of object. An interim solution is to add the removed fields to the mappings as comments. A full solution would be to add types that represent how each saved object is structured in elasticsearch. Having types on the server side is required for the versioned HTTP APIs work anyway.

PR to remove unnecessary fields: #151511
@jonathan-buttner jonathan-buttner added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Cases Cases feature labels Mar 6, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@jonathan-buttner jonathan-buttner mentioned this issue Mar 6, 2023
Merged
jonathan-buttner added a commit that referenced this issue Mar 6, 2023
@jonathan-buttner
[Cases] Adding comments indicating which fields are not indexed (#152763
be430bc 
)

This PR adds comments to the various mapping files that had fields
removed as part of removing fields that should not be indexed.

This PR removed the fields from being mapped:
#151511

This serves to indicate which fields are stored in elasticsearch even
though they are not mapped. Once we have resolved this issue:
#152756 we can remove these
comments.
bmorelli25 pushed a commit to bmorelli25/kibana that referenced this issue Mar 10, 2023
@jonathan-buttner @bmorelli25
[Cases] Adding comments indicating which fields are not indexed (elas…
91a4096 
…tic#152763)

This PR adds comments to the various mapping files that had fields
removed as part of removing fields that should not be indexed.

This PR removed the fields from being mapped:
elastic#151511

This serves to indicate which fields are stored in elasticsearch even
though they are not mapped. Once we have resolved this issue:
elastic#152756 we can remove these
comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @jonathan-buttner