[ https://issues.apache.org/jira/browse/NIFI-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678537#comment-16678537 ]
ASF GitHub Bot commented on NIFI-5780: -------------------------------------- Github user patricker commented on a diff in the pull request: https://github.com/apache/nifi/pull/3156#discussion_r231596320 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/AbstractExecuteSQL.java --- @@ -82,6 +84,16 @@ .identifiesControllerService(DBCPService.class) .build(); + public static final PropertyDescriptor SQL_PRE_QUERY = new PropertyDescriptor.Builder() + .name("sql-pre-query") + .displayName("SQL pre-query") --- End diff -- Can you make this `SQL Pre-Query`? Same for `SQL Post-Query`. > Add pre and post statements to ExecuteSQL and ExecuteSQLRecord > -------------------------------------------------------------- > > Key: NIFI-5780 > URL: https://issues.apache.org/jira/browse/NIFI-5780 > Project: Apache NiFi > Issue Type: Improvement > Affects Versions: 1.8.0 > Reporter: Deon Huang > Assignee: Deon Huang > Priority: Minor > > Sometimes we might need to set up session relate configuration before or > after query. > For example: > Pre query can be used for session relate setting like our use case Teradata > Query Banding. > Same feature (pre query and post query) is added to SelectHiveQL in > https://issues.apache.org/jira/browse/NIFI-5044 > Planning to add this feature to ExecuteSQL and ExecuteSQLRecord processors. > If pre or post statement fail, will not produce resultset flowfile. -- This message was sent by Atlassian JIRA (v7.6.3#76005)