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

ASF GitHub Bot commented on NIFI-4289:
--------------------------------------

Github user mans2singh commented on the issue:

    https://github.com/apache/nifi/pull/2101
  
    @MikeThomsen - 
    
    Thanks for your review comments.
    
    I've updated the version and rebased the code.  
    
    Regarding the error - InfluxDB uses line protocol for writing data (I've 
mentioned that in the capabilities section of the processor) - 
[https://docs.influxdata.com/influxdb/v1.4/write_protocols/line_protocol_tutorial/]
 to for writing data.  
    
    I have integration/unit test that use the protocol for good and bad format 
scenarios -
    
    - integration test - 
[https://github.com/apache/nifi/pull/2101/files#diff-6aa4a2accea7ae7b489e2a219fb777f2]
    - unit tests - 
[https://github.com/apache/nifi/pull/2101/files#diff-9f4273a51b147a9e22085ef842726664]
    
    If you are using the flow file generator with the line protocol - the 
timestamp (last field) is a number - so please use `${now():toNumber()}` rather 
than `${now():toString()}` as shown in the sample measurement below:
    `water,country=US,city=sf rain=1,humidity=0.6 ${now():toNumber()}`
    
    Please let me know of you have any additional comments/recommendations or 
if there is anything else required.
    
    Thanks


> Implement put processor for InfluxDB
> ------------------------------------
>
>                 Key: NIFI-4289
>                 URL: https://issues.apache.org/jira/browse/NIFI-4289
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.3.0
>         Environment: All
>            Reporter: Mans Singh
>            Assignee: Mans Singh
>            Priority: Minor
>              Labels: insert, measurements,, put, timeseries
>
> Support inserting time series measurements into InfluxDB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to