[
https://issues.apache.org/jira/browse/NIFI-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-10502:
------------------------------------
Description:
Throughout the NiFi UI and documentation, we try to consistently refer to
FlowFile as one word.
I noticed that the following processors have a "Max Rows Per Flow File"
property which is inconsistent:
* ExecuteSQL
* ExecuteSQLRecord
* QueryDatabaseTable
* QueryDatabaseTableRecord
* -SelectHiveQL-
* -SelectHive3QL-
* -ScanHBase-
was:
Throughout the NiFi UI and documentation, we try to consistently refer to
FlowFile as one word.
I noticed that the following processors have a "Max Rows Per Flow File"
property which is inconsistent:
* ExecuteSQL
* ExecuteSQLRecord
* QueryDatabaseTable
* QueryDatabaseTableRecord
* SelectHiveQL
* SelectHive3QL
* ScanHBase
> "Max Rows Per Flow File" property in processors should be "Max Rows Per
> FlowFile"
> ---------------------------------------------------------------------------------
>
> Key: NIFI-10502
> URL: https://issues.apache.org/jira/browse/NIFI-10502
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Andrew M. Lim
> Assignee: Daniel Stieglitz
> Priority: Trivial
>
> Throughout the NiFi UI and documentation, we try to consistently refer to
> FlowFile as one word.
> I noticed that the following processors have a "Max Rows Per Flow File"
> property which is inconsistent:
> * ExecuteSQL
> * ExecuteSQLRecord
> * QueryDatabaseTable
> * QueryDatabaseTableRecord
> * -SelectHiveQL-
> * -SelectHive3QL-
> * -ScanHBase-
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
