[
https://issues.apache.org/jira/browse/HIVE-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299861#comment-14299861
]
Hive QA commented on HIVE-7998:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12695746/HIVE-7998.1.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 7411 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.templeton.TestWebHCatE2e.getHiveVersion
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2602/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2602/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-2602/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12695746 - PreCommit-HIVE-TRUNK-Build
> 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
> 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)
