Database Reference
In-Depth Information
reconciler
reconciler
Name of the class that will reconcile conflicting column versions. The only valid value at this
time is
Timestamp
.
comment
comment
Any human-readable comment in the form of a string.
rows_cached
rows_cached
The number of rows to cache.
preload_row_cache
preload_row_cache
Set this to
true
to automatically load the row cache.
key_cache_size
key_cache_size
The number of keys to pull into the cache.
read_repair_chance
read_repair_chance
Valid values are a number between 0.0 and 1.0.
Here's an example:
[default@Keyspace1] create column family MyRadCF with
column_type='Standard' and comparator='UTF8Type' and rows_cached=40000
3ae948aa-ae14-11df-a254-e700f669bcfc
Transitioning from 0.6 to 0.7
The cassandra.yamlile in the confdirectory appears to be the replacement for storage-conf.xml,
the configuration file from version 0.6 and earlier. But this YAML file is intended only for users
upgrading their config files from XML to YAML. Instead, use the Thrift API calls prefixed with
system_
to configure your keyspaces and column families, as shown previously.
If you do have an existing storage-conf.xmlile from using version 0.6, you will first need to
convert it to YAML using the bin/conig-convertertool, which can generate a cassandra.yaml
file from a storage-conf.xml. There is an operation exposed through JMX in the
org.apache.cassandra.service.StorageServiceMBean
called
loadSchemaFromYAML
,
which you can invoke to force Cassandra to load your schema changes from the cassandra.yaml
file in your seed node. New nodes in your cluster will get schema updates as they are started. The
seed node is not special here. You can run this method against any one node (though running it
against more than one node is not recommended), and all nodes will receive the schema changes
