Description and usage of PutDruidRecord processor:

Sends records to Druid for Indexing. Leverages Druid Tranquility Controller service.

Tags:

druid, timeseries, olap, ingest, put, 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.

Name

Default Value

Allowable Values

Description

Record Reader

Controller Service API: 


RecordReaderFactory

Implementations: 


XMLReader


GrokReader


JsonPathReader


CSVReader


ScriptedReader


JsonTreeReader


AvroReader


SyslogReader


Syslog5424Reader


 Specifies the Controller Service to use for parsing incoming data and determining the data's schema.

Record Writer

Controller Service API: 


RecordSetWriterFactory

Implementations: 

FreeFormTextRecordSetWriter


XMLRecordSetWriter


JsonRecordSetWriter


CSVRecordSetWriter


AvroRecordSetWriter


ScriptedRecordSetWriter


 The Record Writer to use in order to serialize the data to outgoing relationships.

Tranquility Service

Controller Service API: 


DruidTranquilityService

Implementation: 

DruidTranquilityController


 Tranquility Service to use for sending events to Druid.

Relationships:

Name

Description
success FlowFiles are routed to this relationship when they are successfully processed by Druid
dropped FlowFiles are routed to this relationship when they are outside of the configured time window, timestamp format is invalid, etc...
failure FlowFiles are routed to this relationship when they cannot be parsed or otherwise processed by Druid

Reads Attributes:

None specified.

Writes Attributes:

Name

Description
record.count The number of messages that were sent to Druid for this FlowFile. FlowFiles on the success relationship will have a value of this attribute that indicates the number of records successfully processed by Druid, and the FlowFile content will be only the successful records. This behavior applies to the failure and dropped relationships as well.

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.