-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Transform] remove transform remote connect #54179
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
This sounds good to me! |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Mar 25, 2020
…ote cluster client node role (elastic#54217) With the addition of a formal role for nodes indicating remote cluster connection, the transform specific attribute `node.attr.transform.remote_connect` is no longer necessary. closes elastic#54179
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Mar 25, 2020
…ote cluster client node role (elastic#54217) With the addition of a formal role for nodes indicating remote cluster connection, the transform specific attribute `node.attr.transform.remote_connect` is no longer necessary. closes elastic#54179
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The late addition: #53924
introduces the ability to query for nodes that can connect to remote clusters.
This makes
TRANSFORM_REMOTE_ENABLED_NODE_ATTR
introduced in #52712 superflous. Because #52712 targets7.7
, which means unreleased, it makes sense to remove the setting for 7.7 to circumvent a deprecation cycle.This should go in, into
7.7
despite FF, the change is low risk./CC @jasontedor @droberts195
(There seems no appropriate label, using >non-issue for now as its unreleased und should not be picked up for release notes.)
The text was updated successfully, but these errors were encountered: