[
https://issues.apache.org/jira/browse/NIFI-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698299#comment-14698299
]
Aldrin Piri commented on NIFI-853:
----------------------------------
I could see either flowfile or attributes work for the SQL. I've been
compiling some notes on my interactions with the patch set. Overall, it's been
a great contribution and I think will go a long way. The important thing is to
figure out what extent the SQL coverage is going for and doing that well.
There is obviously a lot of functionality with DBs we are not going to cover,
and that is okay. Having said all that, I was able to create a test flow and
churn some JSON objects out to my tables. I left off yesterday trying to break
things and enumerate the various failure cases. Still have a good bit more
work to do on that front. I think when these items make it into a release they
are going to be quite popular, so really want to make sure we perform our due
diligence plus some in the release process.
> 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)
