[
https://issues.apache.org/jira/browse/NIFI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288097#comment-14288097
]
Ricky Saltzer commented on NIFI-293:
------------------------------------
Hi Joseph -
I was thinking the processor would behave more like a "Put" processor, where
you could do some sort of _UPDATE_ or _INSERT_ , and then either allow the
original FlowFile to continue, or terminate. If the SQL query were to fail for
some reason, this would result in a failed FlowFile, which the user can then
handle.
I guess there could also be a JDBC processor that behaves more like a "Get"
processor, so that you could construct a _SELECT_ query to obtain a value to
attach to the FlowFile's attributes.
Cheers
Ricky
> Add a JDBC Processor for executing arbitrary SQL queries
> --------------------------------------------------------
>
> Key: NIFI-293
> URL: https://issues.apache.org/jira/browse/NIFI-293
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Ricky Saltzer
>
> This could be very useful for a variety of tasks, such as updating a value in
> a PostgreSQL table, or adding a new partition to Hive.
> Ideally, SQL commands could be generated using the NiFi expression language
> using FlowFile attributes.
> The processor should as generic as possible so that any of the popular JDBC
> drivers can be used (e.g. PostgreSQL, Hive, Impala).
> I'm still new to how processors are architected, but it seems that using a
> pre-defined service in the _services.xml_ file (like the distributed map
> cache) would be the most efficient way to share a connection pool across
> multiple JDBC processors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
