Create a keyspace (HTTP)
|
For details about additional languages, see: |
Creates a new keyspace in a database.
Keyspaces are used to store collections and tables in Hyper-Converged Database (HCD).
Result
Creates the specified keyspace.
If the command succeeds, the response indicates the success.
Example successful response:
{
"status": {
"ok": 1
}
}Signature
Use the createKeyspace command.
curl -sS -L -X POST "API_ENDPOINT/v1" \
--header "Token: APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"createKeyspace": {
"name": "KEYSPACE_NAME",
"options": {
"replication": REPLICATION_STRATEGY,
}
}
}'Parameters
| Name | Type | Summary |
|---|---|---|
|
|
The name of the keyspace to create. If a keyspace with the name already exists, a new keyspace isn’t created, and the command succeeds. |
|
|
Optional. Specifies the options for data replication across database nodes. For an example, see Create a keyspace and specify replication options. |
Examples
The following examples demonstrate how to create a keyspace.
Create a keyspace
curl -sS -L -X POST "API_ENDPOINT/v1" \
--header "Token: APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"createKeyspace": {
"name": "KEYSPACE_NAME"
}
}'Create a keyspace and set it as the working keyspace for the database
This option only applies to the clients.
Create a keyspace and specify replication options
For more information about data replication, see Data replication.
Example using SimpleStrategy:
curl -sS -L -X POST "API_ENDPOINT/v1" \
--header "Token: APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"createKeyspace": {
"name": "KEYSPACE_NAME",
"options": {
"replication": {
"class": "SimpleStrategy", "replication_factor": 3
}
}
}
}'Example using NetworkTopologyStrategy:
curl -sS -L -X POST "API_ENDPOINT/v1" \
--header "Token: APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"createKeyspace": {
"name": "KEYSPACE_NAME",
"options": {
"replication": {
"class": "NetworkTopologyStrategy", "datacenter1": 3, "datacenter2": 2
}
}
}
}'