`dse advrep channel create`

Creates a replication channel for change data to flow between source clusters and destination clusters.

A replication channel is a defined channel of change data between source clusters and destination clusters.

This command is supported only on nodes configured for DSE Advanced Replication.

Synopsis

dse advrep channel create
    --source-keyspace <keyspace_name>
    --source-table <source_table_name>
    --source-id <source_id_name>
    --source-id-column <source_id_column_name>
    --destination <destination>
    --destination-keyspace <destination_keyspace_name>
    --destination-table <destination_table_name>
[ --fifo-order | --lifo-order ] [ --collection-enabled (true|false) ]
[ --priority <channel_priority> ] [ --transmission-enabled (true|false) ]

Syntax legend

Syntax conventions Description

Syntax conventions	Description
Italic, bold, or `< >`	Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value. In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: `<datatype2` In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and `solrconfig` files, such as `@<xml_entity>='<xml_entity_type>'`.
`[ ]`	Square brackets surround optional command arguments. Do not type the square brackets.
`( )`	Parentheses identify a group to choose from. Do not type the parentheses.
`\|`	A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.
`...`	Indicates that you can repeat the syntax element as often as required.
`'`	Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as `'<<schema> ... </schema>>'`
`{ }`	Map collection. Curly braces enclose maps (`{ <key_datatype>:<value_datatype> }`) or key value pairs (`{ <key>:<value> }`). A colon separates the key and the value.
`;`	Ends a CQL statement.
`--`	Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Italic, bold, or < >

Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value.

In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: <datatype2

In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and solrconfig files, such as @<xml_entity>='<xml_entity_type>'.

[ ]

Square brackets surround optional command arguments. Do not type the square brackets.

( )

Parentheses identify a group to choose from. Do not type the parentheses.

|

A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.

...

Indicates that you can repeat the syntax element as often as required.

'

Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as '<<schema> ... </schema>>'

{ }

Map collection. Curly braces enclose maps ({ <key_datatype>:<value_datatype> }) or key value pairs ({ <key>:<value> }). A colon separates the key and the value.

;

Ends a CQL statement.

--

Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

--source-keyspace

Provide the name of the source cluster keyspace to replicate.

Required.

--source-table

Provide the name of the source table to replicate.

Required.

--source-id

Provide a unique identifier for all data that comes from a particular source node.

--source-id-column

Specify the column that identifies the source ID in the destination table.

--destination

Specify the user-defined name of the destination where the replication is sent.

Required.

--destination-keyspace

Specify the destination keyspace where replication is sent.

--destination-table

Specify the destination table where replication is sent.

--fifo-order, --lifo-order

Specify the replication order for the channel:

--fifo-order (default): First in, first out. Replicates changes in the order they were made, oldest to newest.
--lifo-order: Last in, first out. Replicates the most recent changes first, then works backward to older changes.

--collection-enabled

Boolean indicating whether to enable the source table for replication collection on creation.

--transmission-enabled

Boolean indicating whether to replicate data collector for the table to the destination.

--priority

Specify the order in which the source table log files are transmitted.

Examples

Create a replication source channel:

dse advrep channel create --source-keyspace foo --source-table bar \
--source-id source1 --source-id-column source_id --destination mydest \
--destination-keyspace foo --destination-table bar --collection-enabled true --priority 1

Result

Created channel dc=Cassandra keyspace=foo table=bar to mydest

The source datacenter is the datacenter in which the command is run. The keyspace and table names on the destination can be different than on the source, but in this example they are the same. You can also set the source-id and source-id-column differently from the global setting.

`dse advrep channel create`

Synopsis

Examples

Was this helpful?

Give Feedback