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

If no clusters are specified, the namespace should by default use current cluster #3571

Merged
merged 3 commits into from Feb 14, 2019

Conversation

merlimat
Copy link
Contributor

Motivation

When creating a new namespace, by default assign it to the current cluster instead of leaving the cluster section as empty.

This will make the behavior easier and less confusing for users when creating a namespace that is not meant to use geo-replication.

@merlimat merlimat added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label Feb 11, 2019
@merlimat merlimat added this to the 2.3.0 milestone Feb 11, 2019
@merlimat merlimat self-assigned this Feb 11, 2019
@merlimat
Copy link
Contributor Author

run integration tests

@merlimat
Copy link
Contributor Author

run java8 tests

@merlimat
Copy link
Contributor Author

run cpp tests

@merlimat
Copy link
Contributor Author

run java8 tests

@merlimat merlimat merged commit 48e4a0b into apache:master Feb 14, 2019
@merlimat merlimat deleted the default-cluster-on-new-ns branch February 14, 2019 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants