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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0, 0.7.0, 1.0.0-Beta
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 06/Jun/16 13:45
• Updated: 04/Aug/16 21:29
• Resolved: 07/Jun/16 21:30

Description

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.

Issue Links

• links to: GitHub Pull Request #498