So if I want to avoid double-storing fields that will never be retrieved individually (only as part of source) then I should do index: no and store: no?
On Jun 20, 2012, at 9:23 AM, Igor Motov email@example.com wrote:
- Indexing 15 fields instead of 500 will definitely reduce index size and memory footprint.
- You can control how documents are retrieved by specifying the list of fields on your search/get request.
- If you will store fields as well as source, you will essentially store fields twice. If you are storing source, you don't have to store individual fields, es can pull them from source. However, it comes at obvious run time cost - es will have to pull and parse entire source even when you want to retrieve only one field. Depending on your traffic and use cases this can be perfectly fine or completely unacceptable.
On Tuesday, June 19, 2012 2:40:17 PM UTC-4, David Kullmann wrote:
Ivan and Igor:
Great, thank you for your help! I have a follow up question:
My goal is to reduce the system resource requirements for my ElasticSearch server. I have many documents with 500 fields each, however, I only need about 15 feeds to be "searchable" but I need the _source to be retrieved still. I was wondering if this is the correct way to think about how the server manages memory (RAM):
If I store all but 15 fields and index the 15 fields I need searchable, the size of the "index" will be smaller
In the scenario in #1 above, the full document will still be retrieved as _source even though the fields are set to "store"
In the scenario in #1 above, I lose any performance when using ES as a data storage system because _source will still be stored the same was regardless of how the individual fields are stored
Is that correct? If so - please let me know, if not, please help me understand what I'm missing. Thanks!
On Tuesday, May 15, 2012 7:31:32 PM UTC-4, Ivan Brusic wrote:
Config mappings should be able to handle dynamic mappings. I never
tried since I switched to index templates when I started using dynamic
If not, you can use dynamic mappings for a specific index + type
combination with index templates:
Just do not supply a wildcard for the template name.
On Tue, May 15, 2012 at 1:23 PM, David Kullmann
It's hard to tell from the documentation - can I add dynamic mapping in a
config file for a specific index + type combination?