[
https://issues.apache.org/jira/browse/DRILL-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134688#comment-15134688
]
Jacques Nadeau commented on DRILL-3581:
---------------------------------------
Yeah, I saw that. Given a complete run on both unit and regression, it looks
like Hadoop and HBase's clients don't use the deprecated apis. If it turns out
we need them for the clients when testing something else, we can move
GuavaPatcher into the execution path (and not just the hbase test path). See
code here:
https://github.com/apache/drill/blob/master/contrib/storage-hbase/src/test/java/org/apache/drill/hbase/GuavaPatcher.java
> Google Guava version is so old it causes incompatibilities with other libs
> --------------------------------------------------------------------------
>
> Key: DRILL-3581
> URL: https://issues.apache.org/jira/browse/DRILL-3581
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Affects Versions: 1.1.0
> Environment: Linux, JDK 1.8
> Reporter: Joseph Barefoot
> Assignee: Steven Phillips
> Fix For: 1.6.0
>
>
> Drill is currently using Guava version 14.0.1, which was released March 2013.
> https://github.com/apache/drill/blob/master/pom.xml
> Many other java projects use newer versions, however this conflicts with the
> Drill JDBC driver since a couple of APIs it uses are incompatible with the
> newer guava versions. In particular:
> https://github.com/apache/drill/blob/master/common/src/main/java/org/apache/drill/common/util/PathScanner.java
> (The public StopWatch class constructor has been removed in favor of factory
> methods)
> Although this seems minor, it prevents easily using Drill from a java
> application, since again many other open source libs will be using the latest
> Guava version (18).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
