[
https://issues.apache.org/jira/browse/BEAM-12837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437482#comment-17437482
]
Beam JIRA Bot commented on BEAM-12837:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: beam-community
> Affects Versions: 2.32.0
> Environment: Production
> Reporter: Ranjan Dahal
> Priority: P2
> Labels: stale-P2
> 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.3.4#803005)
