You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2018/06/28 18:46:00 UTC

[jira] [Assigned] (NIFI-5349) DB Fetch processors do not support Expression Language for Initial Max Value

     [ https://issues.apache.org/jira/browse/NIFI-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess reassigned NIFI-5349:
----------------------------------

    Assignee: Matt Burgess

> 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
>
> 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)