Hi John,

For the ZKClusterID, can you try setting it like this: /drillprod/drillprod

Thanks,
Krystal

On Mon, May 16, 2016 at 8:14 AM, Parth Chandra <pchan...@maprtech.com>
wrote:

> Hi John
>
>   Can you try passing the ZKClusterID parameter to the driver. See example
> here:
>
>     https://drill.apache.org/docs/using-a-connection-string/
>
>    DRIVER=MapR Drill ODBC Driver;AdvancedProperties=
> {HandshakeTimeout=0;QueryTimeout=0;
> TimestampTZDisplayTimezone=utc;ExcludedSchemas=sys,
> INFORMATION_SCHEMA;};Catalog=DRILL;Schema=;
> ConnectionType=ZooKeeper;ZKQuorum=192.168.39.43:5181;
> ZKClusterID=drillbits1
> Thanks
>
> Parth
>
> On Sat, May 14, 2016 at 9:15 AM, John Omernik <j...@omernik.com> wrote:
>
> > All -
> >
> > I am using the MapR ODBC driver. I can get it to connect in direct mode,
> > however, I can't get it to connect in Zookeeper mode.  I think I know
> why.
> >
> > To start off, I am using a different zk.root in my drill-override. This
> > allows me to have truly unique drill clusters on the same physical
> > clusters. This works well for most things, however, what I have found,
> is I
> > believe the ODBC driver assumes a hard coded zk.root. (drill).
> >
> > For example, my cluster name is "drillprod" and my zk.root is "drillprod"
> > So, to connect via JDBC I use URL=
> >
> >
> "jdbc:drill:zk:hadoopmapr4:5181,hadoopmapr5:5181,hadoopmapr6:5181/drillprod"
> >
> > This works
> >
> > However, I set the ZKClusterID  to be drillprod in ODBC and I get
> >
> > Failure occurred while trying to connect to zk=
> > hadoopmapr4.brewingintel.com:5181,hadoopmapr5.brewingintel.com:5181,
> > hadoopmapr6.brewingintel.com:5181/drill/drillprod
> >
> >
> > If set the ZKQuorum to be "hadoopmapr4.brewingintel.com:5181,
> > hadoopmapr5.brewingintel.com:5181,
> > hadoopmapr6.brewingintel.com:5181/drillprod"
> >
> >
> > Then I get this error:
> >
> >
> > Failure occurred while trying to connect to zk=
> > hadoopmapr4.brewingintel.com:5181,hadoopmapr5.brewingintel.com:5181,
> > hadoopmapr6.brewingintel.com:5181/drillprod/drill/drillprod
> >
> >
> > The Znode: /drill/drillprod doesn't exist, neither does
> > /drillprod/drill/drillprod. The correct one, for this use case is
> > "/drillprod/drillprod"
> >
> >
> > But I can't seem to get the ODBC driver to check there, as it appears to
> > hard code a /drill rather than allow me to specify the zk.root as the
> > drill-override.conf does.
> >
> >
> > Please advise
> >
> >
> > John
> >
>

Reply via email to