[
https://issues.apache.org/jira/browse/HIVE-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Pivovarov updated HIVE-7998:
--------------------------------------
Description:
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 explicitly 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
was:
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
Labels: (was: TODOC1.2)
Release Note: Applications no longer need to explicitly load JDBC drivers
using Class.forName()
> 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 explicitly 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)
