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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2022/01/11 18:27:00 UTC

[jira] [Commented] (BEAM-12837) JdbcIO Microsoft Sql Types are not supported

    [ https://issues.apache.org/jira/browse/BEAM-12837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473024#comment-17473024 ] 

Beam JIRA Bot commented on BEAM-12837:
--------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> JdbcIO Microsoft Sql Types are not supported
> --------------------------------------------
>
>                 Key: BEAM-12837
>                 URL: https://issues.apache.org/jira/browse/BEAM-12837
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-jdbc
>    Affects Versions: 2.32.0
>         Environment: Production
>            Reporter: Ranjan Dahal
>            Priority: P3
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> While working with JdbcIO Sql Server data store, I encountered an issue where a data type DATETIMEOFFSET was not supported when reading data as Beam Row. The Beam field converter only looks for JdbcType and ignores the microsoft.sql.Types which makes is impossible for genuine data type to be processed. The list of non supported types are as follows:
> - microsoft.sql.Types.SMALLDATETIME  // -150 represents TSQL smalldatetime type
> - microsoft.sql.Types.DATETIME  // -151 represents TSQL datetime type
> - microsoft.sql.Types.DATETIMEOFFSET  // -155 represents TSQL Datetimeoffset type
>  
> All above types should be treated as if they are TIMESTAMP. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)