You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2015/02/03 23:57:35 UTC

[jira] [Updated] (HIVE-7998) Enhance JDBC Driver to not require class specification

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

Brock Noland updated HIVE-7998:
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0
           Status: Resolved  (was: Patch Available)

Thank you very much! I committed this to trunk!

> Enhance JDBC Driver to not require class specification
> ------------------------------------------------------
>
>                 Key: HIVE-7998
>                 URL: https://issues.apache.org/jira/browse/HIVE-7998
>             Project: Hive
>          Issue Type: New Feature
>          Components: JDBC
>            Reporter: Prateek Rungta
>            Assignee: Alexander Pivovarov
>            Priority: Trivial
>             Fix For: 1.2.0
>
>         Attachments: HIVE-7998.1.patch
>
>
> The hotspot VM offers a way to avoid having to specify the driver class explicitly when using the JDBC driver. 
> The DriverManager methods getConnection and getDrivers have been enhanced to support the Java Standard Edition Service Provider mechanism. JDBC 4.0 Drivers must include the file META-INF/services/java.sql.Driver. This file contains the name of the JDBC drivers implementation of java.sql.Driver. For example, to load the my.sql.Driver class, the META-INF/services/java.sql.Driver file would contain the entry: `my.sql.Driver`
>  
> Applications no longer need to explictly load JDBC drivers using Class.forName(). Existing programs which currently load JDBC drivers using Class.forName() will continue to work without modification.
> via http://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)