CassandraSessionProviderService
Implementation: CassandraSessionProvider
Specifies the Cassandra connection providing controller service to be used to connect to Cassandra cluster. | Cassandra Contact Points | 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 | 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) |
SSL Context Service | SSL Context Service | | Controller Service API: SSLContextService Implementations: StandardRestrictedSSLContextService StandardSSLContextService | The SSL Context Service used to provide client certificate information for TLS/SSL connections. |
Client Auth | Client Auth | REQUIRED | | 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 | | | Username to access the Cassandra cluster Supports Expression Language: true (will be evaluated using variable registry only) |
Password | Password | | | Password to access the Cassandra cluster Sensitive Property: true Supports Expression Language: true (will be evaluated using variable registry only) |
Consistency Level | Consistency Level | ONE | - ANY
- ONE
- TWO
- THREE
- QUORUM
- ALL
- LOCAL_QUORUM
- EACH_QUORUM
- SERIAL
- LOCAL_SERIAL
- LOCAL_ONE
| The strategy for how many replicas must respond before results are returned. |
Compression Type | Compression Type | NONE | | Enable compression at transport-level requests and responses |
Character Set | Character Set | UTF-8 | | Specifies the character set of the record data. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
CQL select query | CQL select query | | | CQL select query Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Max Wait Time | Max Wait Time | 0 seconds | | The maximum amount of time allowed for a running CQL select query. Must be of format <duration> <TimeUnit> where <duration> is a non-negative integer and TimeUnit is a supported Time Unit, such as: nanos, millis, secs, mins, hrs, days. A value of zero means there is no limit. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Fetch size | Fetch size | 0 | | The number of result rows to be fetched from the result set at a time. Zero is the default and means there is no limit. Supports Expression Language: true (will be evaluated using variable registry only) |
Max Rows Per Flow File | Max Rows Per Flow File | 0 | | The maximum number of result rows that will be included in a single FlowFile. This will allow you to break up very large result sets into multiple FlowFiles. If the value specified is zero, then all rows are returned in a single FlowFile. Supports Expression Language: true (will be evaluated using variable registry only) |
Output Batch Size | qdbt-output-batch-size | 0 | | The number of output FlowFiles to queue before committing the process session. When set to zero, the session will be committed when all result set rows have been processed and the output FlowFiles are ready for transfer to the downstream relationship. For large result sets, this can cause a large burst of FlowFiles to be transferred at the end of processor execution. If this property is set, then when the specified number of FlowFiles are ready for transfer, then the session will be committed, thus releasing the FlowFiles to the downstream relationship. NOTE: The maxvalue.* and fragment.count attributes will not be set on FlowFiles when this property is set. Supports Expression Language: true (will be evaluated using variable registry only) |
Output Format | Output Format | Avro | | The format to which the result rows will be converted. If JSON is selected, the output will contain an object with field 'results' containing an array of result rows. Each row in the array is a map of the named column to its value. For example: { "results": [{"userid":1, "name":"Joe Smith"}]} |
Timestamp Format Pattern for JSON output | timestamp-format-pattern | yyyy-MM-dd HH:mm:ssZ | | Pattern to use when converting timestamp fields to JSON. Note: the formatted timestamp will be in UTC timezone. |
Relationships:
Name | Description |
---|
retry | A FlowFile is transferred to this relationship if the operation cannot be completed but attempting it again may succeed. |
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:
Name | Description |
---|
executecql.row.count | The number of rows returned by the CQL query |
fragment.identifier | If 'Max Rows Per Flow File' is set then all FlowFiles from the same query result set will have the same value for the fragment.identifier attribute. This can then be used to correlate the results. |
fragment.count | If 'Max Rows Per Flow File' is set then this is the total number of FlowFiles produced by a single ResultSet. This can be used in conjunction with the fragment.identifier attribute in order to know how many FlowFiles belonged to the same incoming ResultSet. If Output Batch Size is set, then this attribute will not be populated. |
fragment.index | If 'Max Rows Per Flow File' is set then the position of this FlowFile in the list of outgoing FlowFiles that were all derived from the same result set FlowFile. This can be used in conjunction with the fragment.identifier attribute to know which FlowFiles originated from the same query result set and in what order FlowFiles were produced |
State management:
This component does not store state.Restricted:
This component is not restricted.Input requirement:
This component allows an incoming relationship.System Resource Considerations:
None specified.