[
https://issues.apache.org/jira/browse/USERGRID-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226285#comment-14226285
]
David Johnson commented on USERGRID-255:
----------------------------------------
It appears that you can stop ES from storing the JSON source of the document
being indexed
And you can stop ES from storing the fields of the document being stored.
Regarding the document source:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-source-field.html
Regarding the fields:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html
Some related discussion on StackOverflow:
http://stackoverflow.com/questions/17103047/why-do-i-need-storeyes-in-elasticsearch
> Verify we're not storing document source in Elastic Search
> ----------------------------------------------------------
>
> Key: USERGRID-255
> URL: https://issues.apache.org/jira/browse/USERGRID-255
> Project: Usergrid
> Issue Type: Story
> Components: Stack
> Reporter: Todd Nine
> Assignee: David Johnson
>
> From Todd: When I was testing our indexing schema changes, I noticed our
> document source was appearing in ES. We should verify if this is happening in
> production, and if so, turn this off on the client side. Since we store all
> data in Cassandra, we do not need to also store it into ES. This means we can
> index more in ES and use a lot less disk space, so it's very important
> operationally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
