Kudu Sink properties reference

The properties listed in this reference must be added to the connector configuration with the following prefix:

parameter.[***CONNECTOR NAME***] Parameters:

In addition to the properties listed here, this connector also accepts certain properties of the Kafka Connect framework as well as the properties of the NiFi Stateless Sink connector. When creating a new connector using the SMM UI, all valid properties are presented in the default configuration template. You can view the configuration template to get a full list of valid properties. In addition, for more information regarding the accepted properties not listed here, you can review the Apache Kafka documentation and the Stateless NiFi Sink properties reference.

Date Format

Description: Specifies the format to use when reading Date fields from JSON.
Default Value: yyyy-MM-dd
Accepted Values
Required: true

Handle Schema Drift

Description: Specifies whether to handle Schema Drift. If set to true, when fields with names that are not in the target Kudu table are encountered, the Kudu table is altered to include new columns for those fields. If set to false, fields that only exist in the input data are skipped.
Default Value: false
Accepted Values: true, false
Required: true

Ignore Null

Description: Ignore NULL on Kudu Put Operation. If set to true, only non-null columns get updated.
Default Value: false
Accepted Values: true, false
Required: true

Kafka Message Data Format

Description: Specifies the format of the messages the connector receives from Kafka.
Default Value: AVRO
Accepted Values: AVRO, JSON
Required: true

Kerberos Keytab for Kudu

Description: The fully-qualified filename of the kerberos keytab associated with the principal for accessing Kudu.
Default Value: The location of the default keytab which is empty and can only be used for unsecure connections
Accepted Values
Required: true

Kerberos Keytab for Schema Registry

Description: The fully-qualified filename of the kerberos keytab associated with the principal for accessing Schema Registry.
Default Value: The location of the default keytab which is empty and can only be used for unsecure connections.
Accepted Values
Required: true

Kerberos Principal for Kudu

Description: The Kerberos principal used for authenticating to Kudu.
Default Value: default
Accepted Values
Required: true

Kerberos Principal for Schema Registry

Description: The Kerberos principal used for authenticating to Schema Registry.
Default Value: default
Accepted Values
Required: true

Kudu Kerberos Service Name

Description: The SASL protocol name to use for authenticating with Kerberos. Must match the Kudu service principal name.
Default Value: kudu
Accepted Values
Required: false

Kudu Masters

Description: The comma separated addresses of the Kudu masters to connect to. For example: localhost: 7051,localhost:7151,localhost:7251.
Default Value
Accepted Values
Required: true

Kudu Operation Type

Description: Specifies what Kudu operation gets executed.
Default Value: INSERT
Accepted Values: INSERT, INSERT_IGNORE, UPSERT, UPDATE, DELETE, UPDATE_IGNORE, DELETE_IGNORE
Required: true

Lowercase Field Names

Description: Specifies whether to convert column names to lowercase when finding indexes of Kudu table columns.
Default Value: false
Accepted Values: true, false
Required: true

Schema Access Strategy

Description

Specifies the strategy used for determining the schema of the Kafka record. The value you set here depends on the data format set in

Kafka Message Data
              Format

.

If set to Schema Registry, the schema is read from Schema Registry. This setting can be used with both AVRO and JSON formats.

If set to Infer Schema, the schema is inferred based on the input file. This setting can only be used if Kafka Message Data Format is JSON.

If set to Embedded Schema, the schema embedded in the input is used. This setting can only be used ifKafka Message Data Format is AVRO.

Default Value

Schema Registry

Accepted Values

Schema Registry, Infer Schema, Embedded Schema

Required

true

Schema Branch

Description: The name of the branch to use when looking up the schema in Schema Registry. Schema Branch and Schema Version cannot be specified at the same time. If one is specified, the other needs to be removed from the configuration. If Schema Registry is not used, this property must be completely removed from the configuration.
Default Value
Accepted Values
Required: false

Schema Name

Description: The schema name to look up in Schema Registry. If the Schema Access Strategy property is set to Schema Registry, this property must contain a valid schema name. If Schema Registry is not used, this property must be completely removed from the configuration JSON.
Default Value
Accepted Values
Required: false

Schema Registry URL

Description: The URL of the Schema Registry server. If Schema Registry is not used, use the default value.
Default Value: http://localhost:7788/api/v1
Accepted Values
Required: true

Schema Version

Description: The version of the schema to look up in Schema Registry. If Schema Registry is used and a schema version is not specified, the latest version of the schema is retrieved. Schema Branch and Schema Version cannot be specified at the same time. If one is specified, the other needs to be removed from the configuration. If Schema Registry is not used, this property must be completely removed from the configuration.
Default Value
Accepted Values
Required: false

Table Name With Schema

Description: The schema and name of the Kudu Table to put data into. For example: default.mytable. When using Impala: impala::default.mytable.
Default Value
Accepted Values
Required: true

Time Format

Description: Specifies the format to use when reading Time fields from JSON.
Default Value: HH:mm:ss
Accepted Values
Required: true

Timestamp Format

Description: Specifies the format to use when reading Timestamp fields from JSON. The value must match the Java Simple Date Format. (For example, MM/dd/yyyy HH:mm:ss for a two-digit month, followed by a two-digit day, followed by a four-digit year, all separated by forward slashes. This is followed by a two-digit hour in 24-hour format, followed by a two-digit minute, followed by a two-digit second, all separated by colons. The resulting timestamp looks like this: 01/01/2017 18:04:15.)
Default Value: yyyy-MM-dd HH:mm:ss.SSS
Accepted Values
Required: true

Truststore Filename for Schema Registry

Description: The fully-qualified filename of a truststore. This truststore is used to establish a secure connection with Schema Registry using TLS.
Default Value: The location of the default truststore which is empty and can only be used for unsecure connections
Accepted Values
Required: true

Truststore Password for Schema Registry

Description: The password used to access the contents of the truststore configured in the Truststore Filename for Schema Registry property.
Default Value: password
Accepted Values
Required: true

Truststore Type for Schema Registry

Description: The type of the truststore configured in the Truststore Filename for Schema Registry property.
Default Value
Accepted Values: BCFKS, PKCS12, JKS
Required: true