[
https://issues.apache.org/jira/browse/NIFI-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547526#comment-17547526
]
ASF subversion and git services commented on NIFI-10057:
--------------------------------------------------------
Commit 639ab328c9e717e259740133a5571b9ab7123f0d in nifi's branch
refs/heads/dependabot/maven/nifi-nar-bundles/nifi-standard-services/nifi-hbase_1_1_2-client-service-bundle/org.apache.hadoop-hadoop-common-3.2.3
from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=639ab328c9 ]
NIFI-10057: Add support for SQL Server's DATETIMEOFFSET type to ExecuteSQL
processors
Signed-off-by: Pierre Villard <[email protected]>
This closes #6080.
> Support MSSQL's DATETIMEOFFSET type in ExecuteSQL processors
> ------------------------------------------------------------
>
> Key: NIFI-10057
> URL: https://issues.apache.org/jira/browse/NIFI-10057
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.17.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently ExecuteSQL and ExecuteSQLRecord do not support SQL Server's
> DATETIMEOFFSET type as it returns a [non-standard
> constant|https://docs.oracle.com/javase/8/docs/api/constant-values.html#java.sql.Types.ARRAY]
> (-155) for the type. However the driver does return the value as a Timestamp
> so it would be nice for NiFi to support the -155 type by handling it as a
> timestamp (we do something similar for some of Oracle's custom timestamp
> types).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
