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 2019/01/04 14:46:00 UTC

[jira] [Work logged] (BEAM-6367) Beam SQL JDBC driver breaks DriverManager#getConnection for other JDBC sources

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

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

                Author: ASF GitHub Bot
            Created on: 04/Jan/19 14:45
            Start Date: 04/Jan/19 14:45
    Worklog Time Spent: 10m 
      Work Description: kanterov commented on issue #7417: [BEAM-6367] Fix JdbcDriver breaking DriverManager#getConnection
URL: https://github.com/apache/beam/pull/7417#issuecomment-451463095
 
 
   R: @apilloud 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

    Worklog Id:     (was: 181147)
    Time Spent: 20m  (was: 10m)

> Beam SQL JDBC driver breaks DriverManager#getConnection for other JDBC sources
> ------------------------------------------------------------------------------
>
>                 Key: BEAM-6367
>                 URL: https://issues.apache.org/jira/browse/BEAM-6367
>             Project: Beam
>          Issue Type: Bug
>          Components: dsl-sql
>    Affects Versions: 2.9.0
>            Reporter: Gleb Kanterov
>            Assignee: Gleb Kanterov
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {code}
>     DriverManager.getConnection("jdbc:baaaaaad");
> {code}
> throws NullPointerException from Beam instead of SQLException "No suitable driver found"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)