[
https://issues.apache.org/jira/browse/NIFI-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540988#comment-16540988
]
ASF subversion and git services commented on NIFI-5349:
-------------------------------------------------------
Commit f4b2aae48ae32d2d8c7dbe89d342a749bdc32575 in nifi's branch
refs/heads/support/nifi-1.7.x from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f4b2aae ]
NIFI-5349: Fixed EL handling in Initial Max Value props for DB Fetch processors
Signed-off-by: Pierre Villard <[email protected]>
This closes #2822.
> DB Fetch processors do not support Expression Language for Initial Max Value
> ----------------------------------------------------------------------------
>
> Key: NIFI-5349
> URL: https://issues.apache.org/jira/browse/NIFI-5349
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.8.0, 1.7.1
>
>
> As part of NIFI-2881, support for expression language was introduced for
> many/most fields in the DB Fetch processors (GenerateTableFetch,
> QueryDatabaseTable). However for the Initial Max Value properties
> (user-defined properties of the form initial.maxvalue.<column>), the
> documentation is inconsistent as to whether it supports EL, and if EL is
> present it is not evaluated.
> The DB Fetch processors should be updated to fully support (and correctly
> document) the Initial Max Value capability. Note that the scope of EL
> evaluation may differ between GenerateTableFetch and QueryDatabaseTable, as
> the former accepts incoming flow files (via NIFI-2881) but the latter does
> not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
