drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chun Chang <cch...@maprtech.com>
Subject Re: Drill Test Framework configuration file update
Date Mon, 23 Nov 2015 23:40:14 GMT
We definitely could make it backward compatible. But I feel forcing the
change may not be a bad thing.

On Mon, Nov 23, 2015 at 3:32 PM, Sudheesh Katkam <skatkam@maprtech.com>
wrote:

> +1
>
> Note that if this breaking change goes in, all current users must update
> the config file to have this new property.
>
> > On Nov 23, 2015, at 3:21 PM, Chun Chang <cchang@maprtech.com> wrote:
> >
> > I think it's a good change to parameterize the whole connection string.
> > This also allows us to easily switch to other data sources.
> >
> > +1
> >
> > On Mon, Nov 23, 2015 at 3:08 PM, rahul challapalli <
> > challapallirahul@gmail.com> wrote:
> >
> >> Drillers,
> >>
> >> In the extended set of tests [1], we are directly connecting to a single
> >> drillbit through jdbc instead of talking to zookeeper. This was done as
> a
> >> workaround for DRILL-3171. Since the fix for DRILL-3171 has been
> committed
> >> now, I am updating the framework to use zookeeper. As part of this
> change,
> >> I intend to introduce the below config parameter. This parameter also
> >> allows us to switch between connecting to a single drillbit vs
> connecting
> >> through zookeeper. Let me know your thoughts
> >>
> >> CONNECTION_STRING=jdbc:drill:zk\=10.10.100.190:5181/zk_root/cluster_id
> >>
> >> [1] https://github.com/mapr/drill-test-framework
> >>
> >> - Rahul
> >>
>
>

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