You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/04 19:10:00 UTC

[jira] [Work logged] (BEAM-12925) JdbcIo readRows does not handle null numerical values properly

     [ https://issues.apache.org/jira/browse/BEAM-12925?focusedWorklogId=659815&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-659815 ]

ASF GitHub Bot logged work on BEAM-12925:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Oct/21 19:09
            Start Date: 04/Oct/21 19:09
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on pull request #15566:
URL: https://github.com/apache/beam/pull/15566#issuecomment-933773763


   LGTM. We need to mention this in release notes for Beam 2.34.0. I'll update CHANGES.md


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 659815)
    Time Spent: 1h 50m  (was: 1h 40m)

> JdbcIo readRows does not handle null numerical values properly
> --------------------------------------------------------------
>
>                 Key: BEAM-12925
>                 URL: https://issues.apache.org/jira/browse/BEAM-12925
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-jdbc
>    Affects Versions: 2.32.0
>            Reporter: Chris Gray
>            Priority: P2
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Numerical values that are SQL NULL in the database are converted to 0 when read by `readRows`.  This appears to be caused by SchemaUtil.java not checking `ResultSet::wasNull` at line 253 in version 2.32.0.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)