[
https://issues.apache.org/jira/browse/NIFI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940063#comment-14940063
]
Scott commented on NIFI-1011:
-----------------------------
Ah good spot, I didn't see that issue. I've written up a patch on my local
system that converst all byte[] types to base64 and streams them the schema in
the same way a string type is handled.
looking above, I suggest a) do nothing and b) throw an error are not suitable
options, as if they have been included there must be a need to get the data out
of the database, and with the advent of base64 encode/decode processors it
seems the obvious choice.
> ExecuteSQL does not support Binary, VarBinary or LongVarBinary data types.
> --------------------------------------------------------------------------
>
> Key: NIFI-1011
> URL: https://issues.apache.org/jira/browse/NIFI-1011
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.3.0
> Environment: All
> Reporter: Scott
>
> When trying to get a VarBinary or Binary column there is an
> ArrayIndexOutOfRangeException thrown. This is because in / nifi-nar-bundles /
> nifi-standard-bundle / nifi-standard-processors / src / main / java / org /
> apache / nifi / processors / standard / util / JdbcCommon.java the data types
> are not supported.
> I suggest adding them as Base64 encoded strings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
