This repository has been archived by the owner on Oct 29, 2024. It is now read-only.
Re-add cluster-client #411
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Cluster client could be used for InfluxDB Enterprise or old InfluxDB 0.11 cluster.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #354 removed the cluster support as requested in issue #339.
It was removed is due to open-source InfluxDB no longer support cluster with equivalent node.
But for users of InfluxDB enterprise or older InfluxDB version (0.11), it still make sense. This PR re-add the cluster in the client module with warning this is should NOT be used with open-source influxdb-relay based cluster.
This PR the the alternative to #396 which re-add the same functionality but not in the same module.
This PR re-add in client module, because its not legacy as it's still valid for InfluxDB enterprise.
The PR #396, re-add in influxdb011, because on the open-source version it's a legacy cluster.
@aviau you can choose one of the PRs and close the other (they are mutually exclusive).