[
https://issues.apache.org/jira/browse/NIFI-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845116#comment-16845116
]
ASF subversion and git services commented on NIFI-6100:
-------------------------------------------------------
Commit 81ddd02ca89cc068a6367eaeae575bac5c5e2ad5 in nifi's branch
refs/heads/master from Aaron Leon
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=81ddd02 ]
NIFI-6100 Use setBytes in JdbcCommon for binary types
This closes #3410
Signed-off-by: Mike Thomsen <[email protected]>
> JdbcCommon does not support binary types for Phoenix
> -----------------------------------------------------
>
> Key: NIFI-6100
> URL: https://issues.apache.org/jira/browse/NIFI-6100
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Aaron Leon
> Priority: Critical
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The current implementation uses java.sql.PreparedStatement.setBinaryStream,
> which throws SQLFeatureNotSupportedException when used with
> org.apache.phoenix.jdbc.PhoenixPreparedStatement. A better alternative is to
> use setBytes. There will be no performance hit since the binary value is
> already read into memory in the current implementation, and it is implemented
> in PhoenixPreparedStatement so this will fix compatibility with Phoenix. It
> is also noted that PhoenixPreparedStatement should probably implement
> setBinaryStream anyways, so ideally a PR will be sent to Phoenix as well.
> https://github.com/apache/nifi/blob/rel/nifi-1.7.0/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java#L832
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
