You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Alexander Behm (JIRA)" <ji...@apache.org> on 2017/10/04 03:27:00 UTC

[jira] [Created] (IMPALA-6011) Remove use of Guava Hasher to avoid class conflicts with other components

Alexander Behm created IMPALA-6011:
--------------------------------------

             Summary: Remove use of Guava Hasher to avoid class conflicts with other components
                 Key: IMPALA-6011
                 URL: https://issues.apache.org/jira/browse/IMPALA-6011
             Project: IMPALA
          Issue Type: Improvement
          Components: Frontend
    Affects Versions: Impala 2.11.0
            Reporter: Alexander Behm
            Assignee: Alexander Behm
            Priority: Critical


As we've seen in IMPALA-6009 several components that Impala depends on do not shade Guava and so we have several (sometime incompatible) versions of Guava in various jars in Impala's classpath. 

A particularly tricky one is the use of Hasher which has undergone API changes (see comments in IMPALA-6009). I think we should not use Hasher since we only use it to compute an MD5 to avoid the problems with conflicting Guava versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)