[
https://issues.apache.org/jira/browse/NIFI-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943288#comment-15943288
]
ASF subversion and git services commented on NIFI-3596:
-------------------------------------------------------
Commit ced6708d4bca6d179e5f9fbc0b2324102879d21e in nifi's branch
refs/heads/master from [~pvillard]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ced6708 ]
NIFI-3596 - added attributes to GenerateTableFetch processor
Signed-off-by: Matt Burgess <[email protected]>
Updated test to check selected column names
Signed-off-by: Matt Burgess <[email protected]>
This closes #1596
> GenerateTableFetch - Add attributes to generated flow files to ease SQL query
> overwrite
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-3596
> URL: https://issues.apache.org/jira/browse/NIFI-3596
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Trivial
> Fix For: 1.2.0
>
>
> The GenerateTableFetch processor will generate a SQL query based on the
> provided parameters but, if the specific DB adapter is not available, it
> might be necessary to overwrite the SQL query in the ExecuteSQL processor. To
> do that it would be nice to have each part of the query as attributes to take
> advantage of expression language.
> Current workaround (when using GenerateTableFetch against a DB2 database for
> example) is to have an intermediary ExtractText processor and have a regex
> extracting each part of the generated query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
