[jira] [Updated] (KUDU-741) Isolate the Java client dependencies

["Mike Percy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated KUDU-741:
----------------------------
    Parent: KUDU-435

> Isolate the Java client dependencies
> ------------------------------------
>
>                 Key: KUDU-741
>                 URL: https://issues.apache.org/jira/browse/KUDU-741
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: M5
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>
> I talked to [~busbey] this morning about his C6 work on classpath isolation. The current effort is being tracked in CDH-16182. Related upstream jiras are HADOOP-11656 (long read) and HBASE-13517.
> Our current dependencies for the kudu-client module, excluding tests, are:
>  - guava 12
>  - protobuf 2.5
>  - netty 3.8
>  - async 1.4 (for Deferreds)
>  - slf4j 1.6
> Our kudu-mapreduce module additionally depends on:
>  - log4j
>  - slf4j-log4j12
>  - hadoop-client
> Note that the mapreduce module also uses guava internally.
> If we're going to use the ServiceLoader in order to load our client implementation after extracting the interfaces (eg KUDU-724), there might be some additional difficulties.



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