You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/06 15:21:21 UTC

[jira] [Commented] (NIFI-1973) Allow ExecuteSQL to use flow file content as SQL query

    [ https://issues.apache.org/jira/browse/NIFI-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316633#comment-15316633 ] 

ASF GitHub Bot commented on NIFI-1973:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/498

    NIFI-1973 Allow ExecuteSQL to use flow file content as SQL query

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-1973

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #498
    
----
commit 5ae16ec261428d19acd20acc67c25f414146854a
Author: Matt Burgess <ma...@apache.org>
Date:   2016-06-06T15:19:32Z

    NIFI-1973 Allow ExecuteSQL to use flow file content as SQL query

----


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