nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Bende (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-1973) Allow ExecuteSQL to use flow file content as SQL query
Date Tue, 07 Jun 2016 21:31:21 GMT

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

Bryan Bende updated NIFI-1973:
------------------------------
    Fix Version/s: 0.7.0

> Allow ExecuteSQL to use flow file content as SQL query
> ------------------------------------------------------
>
>                 Key: NIFI-1973
>                 URL: https://issues.apache.org/jira/browse/NIFI-1973
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>             Fix For: 1.0.0, 0.7.0
>
>
> Currently the SQL SELECT query used by ExecuteSQL is specified by a required processor
property. This property does accept Expression Language (EL), so it is possible if the query
is in the flow file contents, that an ExtractText processor could be used to put the query
in an attribute, then the Select Query property in ExecuteSQL could reference the attribute
using Expression Language.
> However that seems like an unnecessary extra step, especially when users have data flows
that generate SQL statements, or when their flow accepts files containing SQL statements.
> An improvement to the ExecuteSQL processor could be to make the Select Query property
not required, and if it is empty, the contents of the flow file will be used as the query
value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message