`dse advrep channel update`

Updates a replication channel configuration by specifying a new value for one or more options.

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

Synopsis

dse advrep channel update
    --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) ] [ --transmission-enabled (true|false) ]
[ --priority CHANNEL_PRIORITY ]

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 <keyspace_name>

The source cluster keyspace to replicate.

Required.

--source-table <source_table_name>

The source table to replicate.

Required.

--source-id <id>

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

--source-id-column <source_id>

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

--destination <destination>

The destination where the replication is sent. The user names the destination.

Required.

--destination-keyspace <keyspace_name>

The destination keyspace to which replication is sent.

--destination-table <table_name>

The destination table to which 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 (true|false)

Whether to enable the source table for replication collection on creation.

--transmission-enabled true | false

Whether the data collector for the table should be replicated to the destination.

--priority <channel_priority>

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

Examples

Update a replication source channel configuration:

dse advrep --verbose channel update --source-keyspace demo --source-table sensor_readings --destination mydest --lifo-order

Result

---------------------------------------------------------------------------------------------------------------------------------------------------------
|dc       |keyspace|table           |collecting|transmitting|replication order|priority|dest ks|dest table      |src id |src id col|dest   |dest enabled|
---------------------------------------------------------------------------------------------------------------------------------------------------------
|Cassandra|demo    |sensor_readings |true      |true        |LIFO             |2       |demo   |sensor_readings |source1|source_id |mydest |true        |
---------------------------------------------------------------------------------------------------------------------------------------------------------

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 update`

Synopsis

Examples

Was this helpful?

Give Feedback