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

[feat/cli] keyspace options in configuration and un-nesting #634

Merged
merged 2 commits into from
Oct 15, 2015

Conversation

thibaultcha
Copy link
Member

Reopening of #589 against feat/commented-config this time.

Possibility to configure the replication strategy used by the created
keyspace and its options.

Added options:

######
## Keyspace options. Set those before running Kong or any migration.
## Those settings will be used to create a keyspace with the desired options
## when first running the migrations.
## See http://docs.datastax.com/en/cql/3.1/cql/cql_reference/create_keyspace_r.html

######
## The name of the replica placement strategy class for the new keyspace.
## Can be "SimpleStrategy" or "NetworkTopologyStrategy".
# replication_strategy: SimpleStrategy

######
## For SimpleStrategy only.
## The number of replicas of data on multiple nodes.
# replication_factor: 1

######
## For NetworkTopologyStrategy only.
## The number of replicas of data on multiple nodes in each data center.
# data_centers:
#   dc1: 2
#   dc2: 3

Implements #543 and #350

Possibility to configure the replication strategy used by the created
keyspace and its options.

Implements #543 and #350
DAO properties are no nested in `properties` property anymore.
@thibaultcha thibaultcha added the pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) label Oct 15, 2015
@thibaultcha thibaultcha merged this pull request into feat/commented-config Oct 15, 2015
@thibaultcha thibaultcha deleted the feat/keyspace-options branch October 15, 2015 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant