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 2017/11/06 01:07:00 UTC

[jira] [Commented] (DRILL-5934) How to deploy drill by sub-component?

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

Paul Rogers commented on DRILL-5934:
------------------------------------

At present, Drill is a monolith and requires all components and jars to operate. This is one reason that the JDBC jar is so large when it includes the ability to start an embedded Drillbit.

> How to deploy drill by sub-component?
> -------------------------------------
>
>                 Key: DRILL-5934
>                 URL: https://issues.apache.org/jira/browse/DRILL-5934
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Yi Zhao
>
> I know drill is great to manage multiple data sources. But its size is quite big, more than 200MB. If I need to support `mongodb` and `mysql`, whether I can get a package only requires `mongodb` and `mysql` related dependencies? That will reduce the size of the deploy artifact.



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