[ISSUE] (TEPHRA-150) Tephra Guava version

[Thomas D'Silva (JIRA)]

Thomas D'Silva created an issue

Tephra / TEPHRA-150 Tephra Guava version Issue Type: New Feature Assignee: Poorna Chandra Created: 18/Nov/15 3:54 PM Priority: Major Reporter: Thomas D'Silva Phoenix uses guava version 12.0.1 (which is the same version that HBase uses), while tephra requires 13.0.1 or else our transaction tests fail when trying to create a zookeeper client which is needed to create the transaction manager. ava.lang.NoClassDefFoundError: com/google/common/util/concurrent/Service$Listener at org.apache.twill.internal.zookeeper.DefaultZKClientService.<init>(DefaultZKClientService.java:98) at org.apache.twill.zookeeper.ZKClientService$Builder.build(ZKClientService.java:101) at org.apache.phoenix.query.BaseTest.setupTxManager(BaseTest.java:525) at org.apache.phoenix.query.BaseTest.checkClusterInitialized(BaseTest.java:548) at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:608) at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:604) at org.apache.phoenix.end2end.BaseHBaseManagedTimeIT.doSetup(BaseHBaseManagedTimeIT.java:54) Would it be possible to use version 12.0.1? This would make deployment of the transaction manager on our cluster easier. Add Comment

This message was sent by Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc)

[Thomas D'Silva (JIRA)]

Thomas D'Silva commented on an issue

Re: Tephra Guava version James Taylor Poorna Chandra

Add Comment

Tephra / TEPHRA-150 Tephra Guava version

Phoenix uses guava version 12.0.1 (which is the same version that HBase uses), while tephra requires 13.0.1 or else our transaction tests fail when trying to create a zookeeper client which is needed to create the transaction manager. ava.lang.NoClassDefFoundError: com/google/common/util/concurrent/Service$Listener

at org.apache.twill.internal.zook...

[James Taylor (JIRA)]

James Taylor commented on an issue

Re: Tephra Guava version Curious too, Poorna Chandra, how you deal with this wrt HBase on the server side? We've run into issues in the past when our Guava jar doesn't match the HBase one (and HBase is in turn dependent on the version of Guava in HDFS).

Add Comment

[Alvin Wang (JIRA)]

Alvin Wang commented on an issue

Re: Tephra Guava version Thomas D'Silva: Currently there are libraries which depend on tephra-core, tephra-hbase-compat-* using Guava 13.0.1 which prevents us from using any other version of Guava. James Taylor: I'm not the most familiar with this issue, but I don't think we have any special handling for this in CDAP. Would like Poorna Chandra to comment.

Add Comment

[Poorna Chandra (JIRA)]

Poorna Chandra commented on an issue

Re: Tephra Guava version HBase co-processor code does not use any guava-13 features. Hence things work fine on server side. Thomas D'Silva Is the above exception only while running test cases? In that case can you add a direct guava-13 test dependency to your pom? This should load guava-13 only for running tests. Let's see if that works.

Add Comment

[James Taylor (JIRA)]

James Taylor commented on an issue

Re: Tephra Guava version Although this surfaced in testing, it's not a test-only issue as we'd see the same error in a real environment when we start the transaction manager client. I think we'll be ok by including the newer Guava version on the client side, but relying on the Guava version used by HBase on the server side. Feel free to close this.

Add Comment

[Poorna Chandra (JIRA)]

Poorna Chandra commented on an issue

Re: Tephra Guava version Twill's Zookeeper client implementation used by Tephra depends on Guava 13 specific classes. If we have to downgrade the Guava version, then we'll need a new release of Twill. Since we can workaround this issue by updating the client Guava version, I'm going to close this JIRA now.

Add Comment

[Poorna Chandra (JIRA)]

Poorna Chandra resolved an issue as Won't Fix

Tephra / TEPHRA-150 Tephra Guava version

Change By: Poorna Chandra Status: Open Resolved Resolution: Won't Fix

Add Comment