[
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511311#comment-16511311
]
ASF GitHub Bot commented on NIFI-5226:
--------------------------------------
Github user timhallinflux commented on the issue:
https://github.com/apache/nifi/pull/2743
PutInfluxDB was created as single purpose tool -- accepting line protocol
only. It does not read CSVs, AVROs, JSONs out of the box. If developer wants to
use it with NiFi, s/he has to extend it and write their own parsers. That is
ok...and it does support a direct integration.
However, PutInfluxDBRecord addresses the problem of reading the data. It
simplifies data parsing and handling using the concept of Records (
https://blogs.apache.org/nifi/entry/record-oriented-data-with-nifi )
It more naturally works with Nifi objects and the fields, tags are
configurable from within the Nifi IDE...which delivers a much more integrated
experience.
For example: Reading Twitter with PutInfluxDB is not possible without
coding/external configuration. On the contrary, reading Twitter JSON via
PutInfluxDBRecord is no-dev effort and leverages the tools within NiFi itself.
Still, the two classes can coexist depending on the type of work that needs
to be done. I'm in favor of moving ahead with the PutInfluxDBRecord
> 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
> Fix For: 1.7.0
>
>
> 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)
