[
https://issues.apache.org/jira/browse/NIFI-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462836#comment-16462836
]
ASF GitHub Bot commented on NIFI-5130:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2666
@michaelandrepearce so I pushed about 30k events into InfluxDB using some
artifacts from @mans2singh's PRs and ran `select * from /*/` on the database.
Let it run twice and the result sets were different in size. Is each iteration
of the processor supposed to be a new chunk or is it supposed to chunk the
entire result set of that select statement each run?
> 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)
