[
https://issues.apache.org/jira/browse/NIFI-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623893#comment-17623893
]
ASF subversion and git services commented on NIFI-10503:
--------------------------------------------------------
Commit 2d5a8b8b0d43759bba0adfa3caa26a83bceab15b in nifi's branch
refs/heads/main from Andrew Lim
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2d5a8b8b0d ]
NIFI-10503 Changed flow file references to FlowFile in GenerateTableFetch
processor docs
Signed-off-by: Nathan Gough <[email protected]>
This closes #6577.
> GenerateTableFetch processor has multiple references to "flow file" instead
> of "FlowFile"
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-10503
> URL: https://issues.apache.org/jira/browse/NIFI-10503
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI, Documentation & Website
> Reporter: Andrew M. Lim
> Assignee: Andrew M. Lim
> Priority: Trivial
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The property "Output Empty FlowFile on Zero Results" has the description:
> Depending on the specified properties, an execution of this processor may not
> result in any SQL statements generated. When this property is true, an empty
> *flow file* will be generated (having the parent of the incoming *flow file*
> if present) and transferred to the 'success' relationship. "When this
> property is false, no output *flow files* will be generated.
> Additionally, the usage docs has this in the description:
> "Generates SQL select queries that fetch "pages" of rows from a table. The
> partition size property, along with the table's row count, determine the size
> and number of pages and generated FlowFiles. In addition, incremental
> fetching can be achieved by setting Maximum-Value Columns, which causes the
> processor to track the columns' maximum values, thus only fetching rows whose
> columns' values exceed the observed maximums. This processor is intended to
> be run on the Primary Node only. This processor can accept incoming
> connections; the behavior of the processor is different whether incoming
> connections are provided: - If no incoming connection(s) are specified, the
> processor will generate SQL queries on the specified processor schedule.
> Expression Language is supported for many fields, but no *flow file*
> attributes are available. However the properties will be evaluated using the
> Variable Registry. - If incoming connection(s) are specified and no *flow
> file* is available to a processor task, no work will be performed. - If
> incoming connection(s) are specified and a *flow file* is available to a
> processor task, the *flow file's* attributes may be used in Expression
> Language for such fields as Table Name and others. However, the Max-Value
> Columns and Columns to Return fields must be empty or refer to columns that
> are available in each specified table."
> and this in the Additional Details:
> "GenerateTableFetch uses its properties and the specified database connection
> to generate *flow files* containing SQL statements that can be used..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
