[
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545340#comment-16545340
]
ASF GitHub Bot commented on NIFI-5226:
--------------------------------------
Github user ivankudibal commented on the issue:
https://github.com/apache/nifi/pull/2743
@MikeThomsen -- we've written 3 examples of how this processor can be used.
With the examples I believe the PR review will be faster and gives you user
perspective. I've shared access to a private repo having the examples at
gitlab. I hope your username at gitlab is MikeThomsen too.
> Implement a Record API based PutInfluxDB processor
> --------------------------------------------------
>
> Key: NIFI-5226
> URL: https://issues.apache.org/jira/browse/NIFI-5226
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Bonitoo4Influxdata Engineering
> Priority: Major
> Labels: influx, processor, timeseries
>
> Implement a new processor that uses the Record API to put data into InfluxDB.
> PutInfluxDBRecord features:
> * Input can be any built-in or custom implemented NiFi RecordReader (json,
> avro, csv, InfluxLineProtocolReader...)
> * Configurable mapping between NiFi Records and InfluxDB measurement, field
> and tags
> * Configurable timestamp precision
> * Reusable connection settings (InfluxDB url, password) for more processors
> via InfluxDBService controller
> * Advanced InfluxDB client settings
> *
> ** Gzip compression
> ** Batching, jitter, flush settings
> InfluxDBService features:
> * InfluxDBService allows sharing connection configuration among more NiFi
> processors.
> * SSL support
> InfluxLineProtocolReader features
> * InfluxLineProtocolReader parses the InfluxDB Line Protocol into NiFi
> Record. This allows processing, filtering and partitioning data in NiFi
> obtained from Telegraf agents, IoT devices, InfluxDB subscriptions and other
> InfluxDB Line protocol devices.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
