[
https://issues.apache.org/jira/browse/NIFI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361143#comment-14361143
]
Mark Payne commented on NIFI-293:
---------------------------------
I think we also would want to consider here a GetSQL or GetJDBC processor (or
whatever name is better than those). The idea here is that it would be
configured with a SQL query similar to the ExecuteSQL processor discussed
above. However, it would be a 'source' processor and not take in a FlowFile.
This would be different in that it would need to monitor for changes to the
database. Perhaps we would allow for two optional properties to configure the
column that is the ID and a column that is a "last updated" column. That way,
we can detect any updated rows, as well as new rows, and generate a FlowFile
for each row that is added or updated.
> 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)
