You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2016/03/31 18:28:25 UTC

[jira] [Updated] (DRILL-4561) Rationalize jar structure to minimize client dependencies

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

Paul Rogers updated DRILL-4561:
-------------------------------
    Issue Type: Task  (was: Improvement)

> Rationalize jar structure to minimize client dependencies 
> ----------------------------------------------------------
>
>                 Key: DRILL-4561
>                 URL: https://issues.apache.org/jira/browse/DRILL-4561
>             Project: Apache Drill
>          Issue Type: Task
>          Components:  Server
>            Reporter: Paul Rogers
>            Priority: Minor
>
> In building the YARN Application Master (AM), we have need to include the bit of code that tracks Drill-bit registrations in ZK. Doing so needs at least two Drill Jars:
> org.apache.drill.exec/drill-java-exec
> org.apache.drill/drill-protocol
> Even with these, a Maven project fails to include some dependencies, resulting in missing classes:
> Exception in thread "main" java.lang.NoSuchMethodError: com.google.common.base.Stopwatch.createStarted()
> Two suggestions:
> 1. Adjust jars so that client code (such as to read ZK) is in a single jar.
> 2. Ensure Maven dependencies pull in required additional jars.



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