[ 
https://issues.apache.org/jira/browse/SQOOP-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144831#comment-14144831
 ] 

Josh Elser commented on SQOOP-1540:
-----------------------------------

bq. The tests time out because the tablet servers fail when invoking a thrift 
0.9.1 method.

This isn't really accurate. The TabletServers fail to start entirely because 
they're running 0.9.1 generated code which will not work with libthrift 0.9.0 
on the classpath. They will throw an exception, fail to properly start and hang 
themselves.

bq. ... manipulates the classpath of the MiniAccumuloCluster ...

MiniAccumuloCluster has been under flux for a bit in Accumulo. 1.6.0 added some 
new APIs that let us control the classpath used by the MiniAccumuloCluster 
processes (as opposed to always using the classpath from the invoker). To avoid 
breakage with 1.5 (which used thrift 0.9.0 and didn't have issue with hive-exec 
shading in thrift-0.9.0), the entire thing has to be done via reflection which 
is why the patch needs to be more than just a few lines.

> Accumulo unit tests fail with Accumulo 1.6.1 because of conflicts in 
> libthrift libraries
> ----------------------------------------------------------------------------------------
>
>                 Key: SQOOP-1540
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1540
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.5
>         Environment: Sqoop with Accumulo 1.6.1+
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>             Fix For: 1.4.6
>
>         Attachments: SQOOP-1540.diff
>
>
> Accumulo 1.6.1 has started the use of thrift 0.9.1 version and uses 0.9.1 
> specific methods in the tablet server.
> But Hive is still using 0.9.0 version and this causes the miniAccumuloCluster 
> to pick up the 0.9.0 jar file.   The tests time out because the tablet 
> servers fail when invoking a thrift 0.9.1 method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to