phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1250) guava dependency out-dated causing NoSuchMethod error
Date Tue, 16 Sep 2014 16:31:34 GMT


Sean Busbey commented on PHOENIX-1250:

To quote [JBoss|]:

javadoc of Guava 14.0 mentioned:
"Deprecated. Where possible, use the try-with-resources statement if using JDK7 or Closer
on JDK6 to close one or more Closeable objects. This method is deprecated because it is easy
to misuse and may swallow IO exceptions that really should be thrown and handled. See Guava
issue 1118 for a more detailed explanation of the reasons for deprecation and see Closing
Resources for more information on the problems with closing Closeable objects and some of
the preferred solutions for handling it correctly. This method is scheduled to be removed
in Guava 16.0."

> guava dependency out-dated causing NoSuchMethod error
> -----------------------------------------------------
>                 Key: PHOENIX-1250
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: CentOS, Phoenix 4.1, HBase 0.98.5
>            Reporter: Jerry Chabot
>            Assignee: Gabriel Reid
>         Attachments: PHOENIX-1250.patch
> Phoenix has a dependency on Guava 12.0.1 (released in 2012). My project uses Guava 16.0.1.
The latest version is 18. Apparently, the Closeables.closeQuitely(Closeable) no longer exists
in 16.0.1 and later. Possibly earlier versions. 
> I get the error below when attempting to get a connection. This is blocking any attempts
to integrate Phoenix because I cannot downgrade our project dependency to a 2 year old version.

> Please review all project dependencies and consider uprading to more recent versions.
> java.sql.SQLException: java.lang.NoSuchMethodError:;)V
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(
> 	at org.apache.phoenix.query.DelegateConnectionQueryServices.createTable(
> 	at org.apache.phoenix.schema.MetaDataClient.createTableInternal(
> 	at org.apache.phoenix.schema.MetaDataClient.createTable(
> 	at org.apache.phoenix.compile.CreateTableCompiler$2.execute(
> 	at org.apache.phoenix.jdbc.PhoenixStatement$
> 	at org.apache.phoenix.jdbc.PhoenixStatement$
> 	at
> 	at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(
> 	at org.apache.phoenix.jdbc.PhoenixStatement.executeUpdate(
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl$
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl$
> 	at
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.init(
> 	at org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(
> 	at org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.connect(
> 	at org.apache.phoenix.jdbc.PhoenixDriver.connect(
> 	at java.sql.DriverManager.getConnection(
> 	at java.sql.DriverManager.getConnection(

This message was sent by Atlassian JIRA

View raw message