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

Cherry-pick #5319 to 6.0: Do not require template if index change and template disabled #5334

Merged
merged 1 commit into from
Oct 6, 2017

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Oct 5, 2017

Cherry-pick of PR #5319 to 6.0 branch. Original message:

If the elasticsearch index name is changed, its required to set a template. The error message was also shown when template itself are disabled. This is now changed that if templates are disabled, no error is returned.

Closes #5308

…c#5319)

* Do not require template if index change and template disabled

If the elasticsearch index name is changed, its required to set a template. The error message was also shown when template itself are disabled. This is now changed that if templates are disabled, no error is returned.

Closes elastic#5308

* Add Changelog

(cherry picked from commit ce9e47b)
@ruflin ruflin force-pushed the backport_5319_6.0 branch from 3aace3c to 97f102c Compare October 5, 2017 10:19
@ruflin
Copy link
Member Author

ruflin commented Oct 5, 2017

Failing tests should not be related.

@tsg tsg merged commit 316417a into elastic:6.0 Oct 6, 2017
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…c#5319) (elastic#5334)

* Do not require template if index change and template disabled

If the elasticsearch index name is changed, its required to set a template. The error message was also shown when template itself are disabled. This is now changed that if templates are disabled, no error is returned.

Closes elastic#5308

* Add Changelog

(cherry picked from commit b56accf)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants