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.

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

Increase the fields limit #3275

Merged
merged 1 commit into from
Jan 3, 2017
Merged

Conversation

tsg
Copy link
Contributor

@tsg tsg commented Jan 3, 2017

Elasticsearch has a default limit of 1000 fields starting with 5.x.
Metricbeat already defines a bit over that in it's current mapping. In most
deployments, these fields won't be actually used all at the same time, so
the effects of increasing the limit shouldn't be that large (can still affect
the cluster state processing).

Longer term we'll need a better solution for this.

@tsg tsg added the review label Jan 3, 2017
@ruflin
Copy link
Contributor

ruflin commented Jan 3, 2017

We should add a CHANGELOG entry for this to make people that use their own templates or send data through LS aware of this.

Elasticsearch has a default limit of 1000 fields starting with 5.x.
Metricbeat already defines a bit over that in it's current mapping. In most
deployments, these fields won't be actually used all at the same time, so
the effects of increasing the limit shouldn't be that large (can still affect
the cluster state processing).

Longer term we'll need a better solution for this.
@tsg tsg force-pushed the increase_fields_limit branch from 0cf3836 to 83b0573 Compare January 3, 2017 09:39
@tsg
Copy link
Contributor Author

tsg commented Jan 3, 2017

Changelog updated.

@monicasarbu monicasarbu merged commit 1f2be4b into elastic:master Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants