Supports Expression Language: true (will be evaluated using variable registry only)SSL Context Service | SSL Context Service | | Controller Service API: SSLContextService Implementations: StandardSSLContextService StandardRestrictedSSLContextService | The SSL Context Service used to provide client certificate information for TLS/SSL connections. This service only applies if the Elasticsearch endpoint(s) have been secured with TLS/SSL. |
Character Set | Character Set | UTF-8 | | Specifies the character set of the document data. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Username | Username | | | Username to access the Elasticsearch cluster Supports Expression Language: true (will be evaluated using variable registry only) |
Password | Password | | | Password to access the Elasticsearch cluster Sensitive Property: true Supports Expression Language: true (will be evaluated using variable registry only) |
Connection Timeout | elasticsearch-http-connect-timeout | 5 secs | | Max wait time for the connection to the Elasticsearch REST API. Supports Expression Language: true (will be evaluated using variable registry only) |
Response Timeout | elasticsearch-http-response-timeout | 15 secs | | Max wait time for a response from the Elasticsearch REST API. Supports Expression Language: true (will be evaluated using variable registry only) |
Proxy Configuration Service | proxy-configuration-service | | Controller Service API: ProxyConfigurationService Implementation: StandardProxyConfigurationService | Specifies the Proxy Configuration Controller Service to proxy network requests. If set, it supersedes proxy settings configured per component. Supported proxies: SOCKS, HTTP + AuthN In case of SOCKS, it is not guaranteed that the selected SOCKS Version will be used by the processor. |
Proxy Host | elasticsearch-http-proxy-host | | | The fully qualified hostname or IP address of the proxy server Supports Expression Language: true (will be evaluated using variable registry only) |
Proxy Port | elasticsearch-http-proxy-port | | | The port of the proxy server Supports Expression Language: true (will be evaluated using variable registry only) |
Proxy Username | proxy-username | | | Proxy Username Supports Expression Language: true (will be evaluated using variable registry only) |
Proxy Password | proxy-password | | | Proxy Password Sensitive Property: true Supports Expression Language: true (will be evaluated using variable registry only) |
Record Reader | put-es-record-record-reader | | Controller Service API: RecordReaderFactory Implementations: CEFReader SyslogReader ReaderLookup ProtobufReader Syslog5424Reader CSVReader GrokReader WindowsEventLogReader ScriptedReader AvroReader ParquetReader JsonPathReader ExcelReader JsonTreeReader YamlTreeReader XMLReader | Specifies the Controller Service to use for parsing incoming data and determining the data's schema. |
Record Writer | put-es-record-record-writer | | Controller Service API: RecordSetWriterFactory Implementations: JsonRecordSetWriter RecordSetWriterLookup AvroRecordSetWriter XMLRecordSetWriter FreeFormTextRecordSetWriter CSVRecordSetWriter ParquetRecordSetWriter ScriptedRecordSetWriter | After sending a batch of records, Elasticsearch will report if individual records failed to insert. As an example, this can happen if the record doesn't match the mappingfor the index it is being inserted into. This property specifies the Controller Service to use for writing out those individual records sent to 'failure'. If this is not set, then the whole FlowFile will be routed to failure (including any records which may have been inserted successfully). Note that this will only be used if Elasticsearch reports that individual records failed and that in the event that the entire FlowFile fails (e.g. in the event ES is down), the FF will be routed to failure without being interpreted by this record writer. If there is an error while attempting to route the failures, the entire FlowFile will be routed to Failure. Also if every record failed individually, the entire FlowFile will be routed to Failure without being parsed by the writer. |
Log all errors in batch | put-es-record-log-all-errors | false | | After sending a batch of records, Elasticsearch will report if individual records failed to insert. As an example, this can happen if the record doesn't match the mapping for the index it is being inserted into. If this is set to true, the processor will log the failure reason for the every failed record. When set to false only the first error in the batch will be logged. |
Identifier Record Path | put-es-record-id-path | | | A RecordPath pointing to a field in the record(s) that contains the identifier for the document. If the Index Operation is "index" or "create", this property may be left empty or evaluate to an empty value, in which case the document's identifier will be auto-generated by Elasticsearch. For all other Index Operations, the field's value must be non-empty. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
@timestamp Record Path | put-es-record-at-timestamp-path | | | A RecordPath pointing to a field in the record(s) that contains the @timestamp for the document. If left blank the @timestamp will be determined using the main @timestamp property Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
@timestamp Value | put-es-record-at-timestamp | | | The value to use as the @timestamp field (required for Elasticsearch Data Streams) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Index | put-es-record-index | | | The name of the index to insert into Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Type | put-es-record-type | | | The type of this document (required by Elasticsearch versions < 7.0 for indexing and searching). This must be unset or '_doc' for Elasticsearch 7.0+. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Index Operation | put-es-record-index-op | index | | The type of the operation used to index (create, index, update, upsert, delete) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Suppress Null Values | suppress-nulls | Never Suppress | - Never Suppress
- Always Suppress
- Suppress Missing Values
| Specifies how the writer should handle a null field |
Date Format | Date Format | | | Specifies the format to use when reading/writing Date fields. If not specified, the default format 'yyyy-MM-dd' is used. If specified, the value must match the Java Simple Date Format (for example, MM/dd/yyyy for a two-digit month, followed by a two-digit day, followed by a four-digit year, all separated by '/' characters, as in 01/25/2017). Supports Expression Language: true (will be evaluated using variable registry only) |
Time Format | Time Format | | | Specifies the format to use when reading/writing Time fields. If not specified, the default format 'HH:mm:ss' is used. If specified, the value must match the Java Simple Date Format (for example, HH:mm:ss for a two-digit hour in 24-hour format, followed by a two-digit minute, followed by a two-digit second, all separated by ':' characters, as in 18:04:15). Supports Expression Language: true (will be evaluated using variable registry only) |
Timestamp Format | Timestamp Format | | | Specifies the format to use when reading/writing Timestamp fields. If not specified, the default format 'yyyy-MM-dd HH:mm:ss' is used. If specified, 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 '/' characters; and then 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 ':' characters, as in 01/25/2017 18:04:15). Supports Expression Language: true (will be evaluated using variable registry only) |
Dynamic Properties:
Supports Sensitive Dynamic Properties: No
Dynamic Properties allow the user to specify both the name and value of a property.
Name | Value | Description |
---|
A URL query parameter | The value to set it to | Adds the specified property name/value as a query parameter in the Elasticsearch URL used for processing Supports Expression Language: true (will be evaluated using variable registry only) |
Relationships:
Name | Description |
---|
retry | A FlowFile is routed to this relationship if the database cannot be updated but attempting the operation again may succeed |
success | All FlowFiles that are written to Elasticsearch are routed to this relationship |
failure | All FlowFiles that cannot be written to Elasticsearch are routed to this relationship |
Reads Attributes:
None specified.Writes Attributes:
Name | Description |
---|
record.count | The number of records in an outgoing FlowFile. This is only populated on the 'success' relationship. |
failure.count | The number of records found by Elasticsearch to have errors. This is only populated on the 'failure' relationship. |
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.