[
https://issues.apache.org/jira/browse/NIFI-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725887#comment-15725887
]
ASF GitHub Bot commented on NIFI-3029:
--------------------------------------
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1213#discussion_r91107893
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
---
@@ -120,6 +120,15 @@
.addValidator(StandardValidators.NON_NEGATIVE_INTEGER_VALIDATOR)
.build();
+ public static final PropertyDescriptor MAX_FRAGMENTS = new
PropertyDescriptor.Builder()
+ .name("Maximum Number of Fragments")
+ .description("The maximum number of fragments. If not
specified, there is no maximum. " +
+ "This prevents OutOfMemoryError when this processor
ingests huge table.")
+ .defaultValue("1000")
--- End diff --
Since this is a new property and it is optional, the default behavior
should be the same as if the property were not there (so the behavior does not
change for flows created before the property was available). I'm thinking the
default value should be empty.
> QueryDatabaseTable supports max fragments property
> --------------------------------------------------
>
> Key: NIFI-3029
> URL: https://issues.apache.org/jira/browse/NIFI-3029
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.1.0
> Reporter: Byunghwa Yun
> Priority: Minor
>
> When QueryDatabaseTable ingests huge table that has ten billion data at the
> first time, NiFi throws OutOfMemoryError.
> Because QueryDatabaseTable creates too many fragments in memory event setting
> the MaxRowsPerFlowFile property.
> So I suggest QueryDatabaseTable supports max fragments property.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
