incubator-drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Xiao Meng <>
Subject Re: Recent Commits - things to watch out for if you're upgrading
Date Wed, 11 Jun 2014 23:23:49 GMT

I've tried it both in embedded mode and distributed mode and works fine for
me now.

For the distributed mode, we need to set the as zookeeper {
 class: ""

One question:

> In daemon/distributed mode, you can also store them in HBase if you have
that available as part of your cluster.
So do we need to write the plugin for HBase? I did not see any class in

Hope it will help for the other people.

BTW, can someone give the edit permission on the wiki? I can put this into
wiki. My user name is xiaom.



On Wed, Jun 11, 2014 at 12:36 PM, Jacques Nadeau <> wrote:

> Hey Guys,
> I've had a couple of questions about the commits that went in last night.
>  Some things changed in configuration that people should be aware of.  They
> are as follows:
> - drill-override.conf is basically empty.  A sample drill-override is
> available as well to see what some settings are that are available.  You
> should move to this setup only migrate any settings that you have changed
> from previous defaults.
> - If you use your old settings, you'll likely to encounter a Zookeeper
> exception.  This is because the drill.exec.zk.root no longer supports have
> a leading slash (e.g. /drill).  To make it work, you need to either follow
> the recommendation above or remove the leading slash.
> - views, storage plugins and system settings are persisted across drillbit
> restarts.
> - view are persisted in writable workspaces (default one is dfs.tmp) as
> json files called viewname.view.drill.
> - Storage plugins and other drill settings are stored in a Drill PStores (a
> persistent store for settings information).  In embedded mode they are
> persisted to the local file system.  By default, in daemon/distributed
> mode, they are stored in zookeeper.  In daemon/distributed mode, you can
> also store them in HBase if you have that available as part of your
> cluster.
> - In order to configure storage plugins, you need to use the web ui at
> http://localhost:8047
> - By default, Drill is initially populated with
> bootstrap-storage-plugins.json in your classpath (Drill packages one in one
> of the jars or you can put your own earlier in the classpath).  Once the
> first node comes up and populates the storage plugin configuration, Drill
> no longer uses or considers this file.
> Let me know if there are other questions or issues that come up.  Also, be
> sure to do a full clean build with this so you don't have any old/new file
> conflicts.
> thanks,
> Jacques

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message