You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2022/05/25 20:25:00 UTC

[jira] [Updated] (NIFI-10057) Support MSSQL's DATETIMEOFFSET type in ExecuteSQL processors

     [ https://issues.apache.org/jira/browse/NIFI-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-10057:
--------------------------------
    Status: Patch Available  (was: In Progress)

> 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
>          Time Spent: 10m
>  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)