Delete Cassandra (NoSQL)
SynopsisThis operator deletes data from a Cassandra table. The input example set is expected to have an ID attribute which is used to define the rows that will be deleted from Cassandra.
The Delete Cassandra operator is used to delete data from a Cassandra table.
The data to be deleted is defined by the ID attribute of the provided example set. If the selected table contains a compound primary key, additional attributes can be added to the key with the parameter 'additional_primary_keys'.
- input (IOObject)
The example set that defines which data should be deleted from the Cassandra database.
- connection (Connection)
This input port expects a Connection object if any. See the parameter connection entry for more information.
- output (IOObject)
The passed through example set.
- connection (Connection)
This output port delivers the Connection object from the input port. If the input port is not connected the port delivers nothing.
- connection_source This parameter indicates how the connection should be specified. It gives you two options, predefined and repository. The parameter is not visible if the connection input port is connected. Range: selection
- connection_entry This parameter is only available when the connection source parameter is set to repository. This parameter is used to specify a repository location that represents a connection entry. The connection can also be provided using the connection input port. Range: string
- connection This parameter is only available when the connection source parameter is set to predefined. The connection details for the Cassandra connection can be specified here. If you have already configured a Cassandra connection, you can select it from the drop-down list. If you have not configured a Cassandra connection yet, select the Cassandra icon right to the drop-down list. Create a new Cassandra connection in the Manage connections box. The contact points and keyspace name are mandatory. Range: configurable
The consistency level for the Cassandra query. The consistency level
defines how many Cassandra nodes have to respond to the query in
order to be successful.
Possible levels are: ONE, TWO, THREE, QUORUM, ALL, ANY
- ONE: A write must be written at least to one node.
- TWO: A write must be written at least to two nodes.
- THREE: A write must be written at least to three nodes.
- QUORUM: A write must be written at least on a quorum of nodes. A quorum is calculated as (rounded down to a whole number): (replication_factor / 2) + 1. For example, with a replication factor of 3, a quorum is 2 (can tolerate 1 node down). With a replication factor of 6, a quorum is 4 (can tolerate 2 nodes down).
- ALL: A write must be written on all nodes in the cluster for that row key.
- ANY: A write must be written to at least one node
- table_name Specify the table from which data should be deleted. Range: string
- batch_size Define the maximum number of rows which should be deleted with one request. Range: integer
- primary_key_attributes If the selected Cassandra table has a compound primary key this parameter allows you to add more attributes to the primary key. Range: enumeration