[
https://issues.apache.org/jira/browse/NIFI-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700678#comment-14700678
]
Aldrin Piri commented on NIFI-853:
----------------------------------
One small concern as per the Javadoc
(http://docs.oracle.com/javase/7/docs/api/java/sql/BatchUpdateException.html)
{quote}
After a command in a batch update fails to execute properly and a
BatchUpdateException is thrown, the driver may or may not continue to process
the remaining commands in the batch. If the driver continues processing after a
failure, the array returned by the method BatchUpdateException.getUpdateCounts
will have an element for every command in the batch rather than only elements
for the commands that executed successfully before the error. In the case where
the driver continues processing commands, the array element for any command
that failed is Statement.EXECUTE_FAILED.
{quote}
My impression is that some additional checking would be needed from what you
have in the patch to address where a driver continues on, iterating across the
returned array should its size be equal to the initial number of commands
initiated.
> Create Processors to put JSON data to a Relational Database
> -----------------------------------------------------------
>
> Key: NIFI-853
> URL: https://issues.apache.org/jira/browse/NIFI-853
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-853-Added-processors-ConvertFlatJSONToSQL-PutSQ.patch,
> 0002-NIFI-853-Made-updates-to-processors.patch
>
>
> Most of the discussion/design for these processors happened in the comments
> of NIFI-293, which was the initial ticket for implementing JDBC functionality
> in NiFi, but was closed in a previous version, so this ticket was created to
> do the work.
> The idea is to have a processor that will take in FlowFiles whose contents
> are arbitrary SQL INSERT/UPDATE commands. The commands can be parameterized
> with the parameters' values and types in FlowFile attributes.
> We then should have a processor that converts a JSON document into a SQL
> command to either update or insert data into a database table. We will also
> want some other processors in the future probably to handle other data types,
> such as converting XML, CSV, Avro, etc. into SQL commands.
> This breakout gives us a nice coherence to the "do only one thing and do it
> well" principle by separating the logic of handling all of the incoming
> formats from the logic of updating the database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
