[
https://issues.apache.org/jira/browse/NIFI-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428128#comment-15428128
]
ASF GitHub Bot commented on NIFI-2591:
--------------------------------------
Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/883
I was thinking about this and I had a new idea for a solution. What if I
added code that tried to read a new, optional, attribute of the format
`sql.args.N.format`. For the moment it would be just for binary data, with
values like 'hex' or 'ascii' (something like that). But it could be expanded
down the road to also support things like a more flexible version of my
Timestamp PR so users could optionally provide their own Timestamp format.
> PutSQL has no handling for Binary data types
> --------------------------------------------
>
> Key: NIFI-2591
> URL: https://issues.apache.org/jira/browse/NIFI-2591
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Peter Wicks
>
> PutSQL does not call out binary types for any special treatment, so they end
> up being routed through stmt.setObject.
> The problem is that upstream processors have formatted the binary data as a
> string and the JDBC driver doesn't know what to do with a string going into a
> binary field.
> Investigation into the AvroToJSON processor shows that if users are trying to
> load data exported from a source system as Avro Binary that Avro encodes the
> binary data into ASCII (One byte per character).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
