[ https://issues.apache.org/jira/browse/HIVE-15053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167925#comment-16167925 ]
Zoltan Haindrich commented on HIVE-15053: ----------------------------------------- [~Ferd] the classpath scanning thing did cause problems earlier - I think it is safe to assume that all jdbc drivers nowadays has this functionality - this was part of a doc for java6. I did looked around; and concluded that all relevant jdbc drivers are supported - [see here|https://issues.apache.org/jira/browse/HIVE-15053?focusedCommentId=15609340&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15609340] > Beeline#addlocaldriver - reduce classpath scanning > -------------------------------------------------- > > Key: HIVE-15053 > URL: https://issues.apache.org/jira/browse/HIVE-15053 > Project: Hive > Issue Type: Improvement > Reporter: Zoltan Haindrich > Assignee: Zoltan Haindrich > Attachments: HIVE-15053.1.patch, HIVE-15053.1.patch, > HIVE-15053.1.patch, HIVE-15053.2.patch, HIVE-15053.3.patch > > > There is a classpath scanning machinery inside {{ClassNameCompleter}}. > I think the sole purpose of these things is to scan for jdbc drivers...(but > not entirely sure) > if it is indeed looking for jdbc drivers..then possibly this can be removed > without any issues because modern jdbc drivers usually advertise their driver > as a service-loadable class for {{java.sql.Driver}} > http://www.onjava.com/2006/08/02/jjdbc-4-enhancements-in-java-se-6.html > Auto-Loading of JDBC Driver -- This message was sent by Atlassian JIRA (v6.4.14#64029)