All sinks require the following variables to be set
Application prefix for sink metrics.
- Example value:
application_ - Type:
required
Message log-message schema class
- Example value:
com.gotocompany.schema.MessageClass - Type:
required
Message log-key schema class
- Example value:
com.gotocompany.schema.KeyClass - Type:
required
Message raw data type
- Example value:
JSON - Type:
required - Default:
PROTOBUF
The type of raw message to read from
- Example value:
LOG_MESSAGE - Type:
required - Default:
LOG_MESSAGE
Allow unknown fields in proto schema
- Example value:
true - Type:
required - Default:
false
This configuration is used in conjunction with SINK_CONNECTOR_SCHEMA_PROTO_ALLOW_UNKNOWN_FIELDS_ENABLE. If SINK_CONNECTOR_SCHEMA_PROTO_ALLOW_UNKNOWN_FIELDS_ENABLE is set to true, then this configuration is used to validate the unknown fields in the proto message.
Supported values are MESSAGE, MESSAGE_ARRAY_FIRST_INDEX, MESSAGE_ARRAY_FULL. This configuration is used to validate the unknown fields in the proto message. Check will be done recursively for the nested messages.
The choice of the value depends on the use case and trade off between performance and strong consistency.
Use cases:
* MESSAGE - Only check non repeated-message fields.
* MESSAGE_ARRAY_FIRST_INDEX - Check any message type and first index of repeated message fields.
* MESSAGE_ARRAY_FULL - Check any message type and all elements of repeated message field.
Scenario:
* schema :
message Person { string name = 1; int32 age = 2; repeated Pet pets = 3; } message Pet { string name = 1; int32 age = 2; }
* payload :
{ "name": "person1", "age": 10, "pets": [ { "name": "dog1", "age": 2, }, { "name": "dog2", "age": 3, "color": "brown" } ] }
* MESSAGE - It will not validate the unknown field color in the repeated message field pets.
* MESSAGE_ARRAY_FIRST_INDEX - Validation returns true since the color (unknown field) field is not present in the first element of repeated message field pets.
* MESSAGE_ARRAY_FULL - Message will be validated for the unknown field color in all elements of repeated message field pets. Validation returns false since the unknown field is present in the second element of repeated message field pets.
- Example value:
MESSAGE - Type:
required - Default:
MESSAGE
Enable instrumentation for unknown fields validation. Instrumentation itself will introduces some overhead, so it should be enabled when needed.
- Example value:
true - Type:
required - Default:
false
Defines whether to add Kafka metadata fields like topic, partition, offset, timestamp in the input proto messge.
- Example value:
true - Type:
optional - Default:
false
Defines which Kafka metadata fields to add in the Http request payload body, along with their data types.
- Example value:
message_offset=integer,message_topic=string - Type:
optional
Defines whether to send the default values in the request body for fields which are not present or null in the input Proto message
- Example value:
false - Type:
optional - Default value:
false
URL of the StatsD host
- Example value:
localhost - Type:
optional - Default value
: localhost
Port of the StatsD host
- Example value:
8125 - Type:
optional - Default value
: 8125
Global tags for StatsD metrics. Tags must be comma-separated.
- Example value:
team=engineering,app=myapp - Type:
optional