Skip to content

[DOCS] Correct important note for xpack.transform.enabled #52194

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

Merged

Conversation

droberts195
Copy link
Contributor

Because transforms get assigned to an arbitrary data node it
is important that the transforms plugin is enabled on every
data node.

Because transforms get assigned to an arbitrary data node it
is important that the transforms plugin is enabled on every
data node.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

@droberts195 droberts195 changed the title [DOCS] Correct important node for xpack.transform.enabled [DOCS] Correct important note for xpack.transform.enabled Feb 11, 2020
Copy link

@hendrikmuhs hendrikmuhs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@droberts195 droberts195 merged commit 1a099fa into elastic:master Feb 11, 2020
@droberts195 droberts195 deleted the correct_transform_enabled_docs branch February 11, 2020 12:54
droberts195 added a commit that referenced this pull request Feb 11, 2020
Because transforms get assigned to an arbitrary data node it
is important that the transforms plugin is enabled on every
data node.
droberts195 added a commit that referenced this pull request Feb 11, 2020
Because transforms get assigned to an arbitrary data node it
is important that the transforms plugin is enabled on every
data node.
droberts195 added a commit that referenced this pull request Feb 11, 2020
Because transforms get assigned to an arbitrary data node it
is important that the transforms plugin is enabled on every
data node.
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.

4 participants