[
https://issues.apache.org/jira/browse/NIFI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706704#comment-14706704
]
Joseph Witt commented on NIFI-293:
----------------------------------
No problem Dan. Your making important points and being entirely reasonable
about it.
What do you propose is a good solution at this stage?
I agree the names are suboptimal though I don't have a good counter in mind. I
do think it would be nice if ExecuteSQL was 'the one'. That some DML
statements return scalars and that some return rows would be nice if that was
just a property on the processor. I say that though not having done the
legwork to know what the current relationships and properties are.
I am generally opposed to changing the name of the processor class to simply
prevent confusion. We learned long ago that the naming of processors is an
imperfect art. We do have precedence to deprecate processors but that should
be principally due to them being rendered unnecessary by other better
processors in terms of function.
Thanks
Joe
> 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
> Attachments: AvroWriter.java
>
>
> 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)
