You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/03 13:12:00 UTC

[jira] [Commented] (NIFI-5130) ExecuteInfluxDBQuery processor chunking support

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

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

Github user MikeThomsen commented on the issue:

    https://github.com/apache/nifi/pull/2666
  
    @michalmisiewicz so if I understand the Jira ticket correctly, the purpose of this ticket is to make it possible to stream out everything that matches the query, not just one large result payload. Is that right?


> ExecuteInfluxDBQuery processor chunking support
> -----------------------------------------------
>
>                 Key: NIFI-5130
>                 URL: https://issues.apache.org/jira/browse/NIFI-5130
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Michał Misiewicz
>            Priority: Minor
>
> Many production InfluxDB installation has limited number of rows returned in a single query (by default 10k). In case of huge collections, 10k rows can correspond to less than 1 minute of events, which make usage of ExecuteInfluxDBQuery processor inconvenient. I suggest adding support for chunking queries. Chunking can be used to return results in a stream of smaller batches (each has a partial results up to a chunk size) rather than as a single response. Chunking query can return an unlimited number of rows.



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