Performance implications for elasticsearch when specifying fields that won't be in the indexed documents?

Elastic Stack Elasticsearch
1

I'm working on switching to using the ECS toolchain for our indices (mostly logs).

The usage notes for the generator say:

If your indices will never populate particular ECS fields, there's no need to include those field definitions in your index mappings.

I'm considering implementing this, but would like to know:

Are there performance/storage/etc. implications for elasticsearch when defining more fields than will be used in the documents in the index?

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.