Question regarding Customizing fields.yml

Hi there,

Just wanted to know what the general guidelines/best practices are regarding fields.yml which is used for creating index template.

The out-of-box fields.yml has hundreds of fields and we are not even using most of it.

1- Is it a good practice to remove the unwanted fields and actually add our own custom fields into fields.yml ?.

2- Can the out-of-box fields.yml cause performance issue since there are so many fields. Does ES internally really care about the unused fields. (fields with no data).?

3- If we do customize, then are "|pattern|fields" the correct config properties to set.


I wouldn't recommend messing with the out-of-the-box fields.yml. Instead I'd recommend creating your own and then using|pattern|fields.


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