[
https://issues.apache.org/jira/browse/NIFI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554536#comment-14554536
]
Toivo Adams commented on NIFI-293:
----------------------------------
Maybe I should start eating own dog food. (NIFI-322)
And start implementing ExecuteSQL processor (as described above).
Unless someone already started work or have desire to do so.
For example query can be:
SELECT * FROM orders WHERE orderId = '${order.id}'
where ${order.id} is FlowFile attribute.
Result will serialized using Avro.
Avro gives as possibility to have query Resultset metadata (column name and
types) included in FlowFile.
Also Avro should allow streaming.
Should I create separate Jira task?
There might more details which are different from Put* / Get* processors
and I intend to implement only ExecuteSQL currently.
Thanks
Toivo
> 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)
