[
https://issues.apache.org/jira/browse/NIFI-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464057#comment-16464057
]
ASF GitHub Bot commented on NIFI-5130:
--------------------------------------
Github user MikeThomsen commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2666#discussion_r186126226
--- Diff:
nifi-nar-bundles/nifi-influxdb-bundle/nifi-influxdb-processors/src/main/java/org/apache/nifi/processors/influxdb/ExecuteInfluxDBQuery.java
---
@@ -189,9 +209,10 @@ public void onTrigger(final ProcessContext context,
final ProcessSession session
try {
long startTimeMillis = System.currentTimeMillis();
- QueryResult result = executeQuery(context, database, query,
queryResultTimeunit);
+ int chunkSize =
Integer.valueOf(context.getProperty(INFLUX_DB_QUERY_CHUNK_SIZE).evaluateAttributeExpressions(outgoingFlowFile).getValue());
--- End diff --
You can use `asInteger()` or `asLong()` here instead of using
`Integer.valueOf` and `getValue()`
> 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)
