Description and usage of PutCassandraRecord processor:

This is a record aware processor that reads the content of the incoming FlowFile as individual records using the configured ‘Record Reader’ and writes them to Apache Cassandra using native protocol version 3 or higher.

Tags:

cassandra, cql, put, insert, update, set, record

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the Expression Language Guide, and whether a property is considered “sensitive”, meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the nifi.properties file has an entry for the property nifi.sensitive.props.key.

Name

Default Value

Allowable Values

Description

Cassandra Connection Provider

Controller Service API: 


CassandraSessionProviderService

Implementation: 

CassandraSessionProvider


Specifies the Cassandra connection providing controller service to be used to connect to Cassandra cluster.
Cassandra Contact Points Contact points are addresses of Cassandra nodes. The list of contact points should be comma-separated and in hostname:port format. Example node1:port,node2:port,.... The default client port for Cassandra is 9042, but the port(s) must be explicitly specified.

Supports Expression Language: true (will be evaluated using variable registry only)


Keyspace The Cassandra Keyspace to connect to. If no keyspace is specified, the query will need to include the keyspace name before any table reference, in case of 'query' native processors or if the processor exposes the 'Table' property, the keyspace name has to be provided with the table name in the form of <KEYSPACE>.<TABLE>

Supports Expression Language: true (will be evaluated using variable registry only)


Table name

The name of the Cassandra table to which the records have to be written.

Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)


Client Auth REQUIRED * WANT
* REQUIRED
* NONE
Client authentication policy when connecting to secure (TLS/SSL) cluster. Possible values are REQUIRED, WANT, NONE. This property is only used when an SSL Context has been defined and enabled.
Username Username to access the Cassandra cluster

Supports Expression Language: true (will be evaluated using variable registry only)


Password Password to access the Cassandra cluster

Sensitive Property: true


Supports Expression Language: true (will be evaluated using variable registry only)


Record Reader

Controller Service API: 


RecordReaderFactory

Implementations: 


AvroReader


SyslogReader


ScriptedReader


XMLReader


GrokReader


Syslog5424Reader


CSVReader


JsonTreeReader


JsonPathReader


Specifies the type of Record Reader controller service to use for parsing the incoming data and determining the schema

Batch size

100 Specifies the number of 'Insert statements' to be grouped together to execute as a batch (BatchStatement)

Supports Expression Language: true (will be evaluated using variable registry only)


Consistency Level SERIAL * SERIAL
* LOCAL_SERIAL
The strategy for how many replicas must respond before results are returned.
Batch Statement Type LOGGED * LOGGED
* UNLOGGED
* COUNTER
Specifies the type of 'Batch Statement' to be used.
SSL Context Service

Controller Service API: 


SSLContextService

Implementations: 

StandardRestrictedSSLContextService


StandardSSLContextService


The SSL Context Service used to provide client certificate information for TLS/SSL connections.

Relationships:

Name

Description

success A FlowFile is transferred to this relationship if the operation completed successfully.
failure A FlowFile is transferred to this relationship if the operation failed.

Reads Attributes:

None specified.

Writes Attributes:

None specified.

State management:

This component does not store state.

Restricted:

This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

None specified.