[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662133#comment-16662133
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user ivankudibal commented on the issue:

https://github.com/apache/nifi/pull/2743
  
@MikeThomsen 


> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579979#comment-16579979
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user ivankudibal commented on the issue:

https://github.com/apache/nifi/pull/2743
  
@MikeThomsen any update?


> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537811#comment-16537811
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2743
  
@timhallinflux not at the moment. It's a huge commit, and I've been too 
busy to get into it.


> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537757#comment-16537757
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user timhallinflux commented on the issue:

https://github.com/apache/nifi/pull/2743
  
@MikeThomsen -- any update here?


> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[Bonitoo4Influxdata Engineering (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16519421#comment-16519421
 ] 

Bonitoo4Influxdata Engineering commented on NIFI-5226:
--

Hi [~joewitt] , the contribution was made by Jakub Bednar from Bonitoo 
corporation. I've, in the role of CEO, on behalf of the corporation just signed 
the corporate CLA and have sent it to secretary@  .. I believe this helps 
address your concern. Regards, Ivan

> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[Joseph Witt (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517322#comment-16517322
 ] 

Joseph Witt commented on NIFI-5226:
---

this looks like a good contribution.  [~bonitoo-engineers] please be sure the 
contribution is being made by you and not any specific company.  contributions 
to apache projects are made by individuals - not corporations.  Just want to be 
sure we're not getting ourselves into a situation that complicates 
copyright/licensing/etc...  Thanks

> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[Andy LoPresto (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517314#comment-16517314
 ] 

Andy LoPresto commented on NIFI-5226:
-

Once there is more review traction, we can assign to a fix version. Removing 
1.7.0 for now. 

> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493366#comment-16493366
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2743
  
@mans2singh @timhallinflux can y'all jump in on this and give some feedback 
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
> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492591#comment-16492591
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

Github user bednar commented on the issue:

https://github.com/apache/nifi/pull/2743
  
Hi NiFi team, this pull request is now ready to get reviewed. 

The script to help reviewing/testing this PR is available in the sources: 
`nifi-nar-bundles/nifi-influxdb-bundle/InfluxDBIntegrationTests.sh`

Jakub



> 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)

[jira] [Commented] (NIFI-5226) Implement a Record API based PutInfluxDB processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492513#comment-16492513
 ] 

ASF GitHub Bot commented on NIFI-5226:
--

GitHub user bednar opened a pull request:

https://github.com/apache/nifi/pull/2743

NIFI-5226: Implement a Record API based PutInfluxDB processor

- Added PutInfluxDBRecord for put data to InfluxDB by Apache NiFi Record API
- Added InfluxLineProtocolReader for parsing InfluxDB Line Protocol to 
Apache NiFi Record
- Added InfluxDBService for sharing connection settings to InfluxDB
- Upgraded influxdb-java to 2.10

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [x] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bonitoo-io/nifi nifi-5226

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2743.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2743


commit cd713cae8fff3c9036edb01519256a8458b2d12a
Author: Jakub Bednář 
Date:   2018-05-28T08:09:16Z

NIFI-5226: Implement a Record API based PutInfluxDB processor

- Added PutInfluxDBRecord for put data to InfluxDB by Apache NiFi Record API
- Added InfluxLineProtocolReader for parsing InfluxDB Line Protocol to 
Apache NiFi Record
- Added InfluxDBService for sharing connection settings to InfluxDB
- Upgraded influxdb-java to 2.10




> 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)