is your environment setting:
> > >
> > > 1) Secure MapR cluster.
> > >
> > > 2) Running drill-1.12.0 installed from MapR released RPM.
> > >
> > > 3) Re-using the configuration from drill-1.10.0.
> > >
> > >
> > > Thanks,
> &
> > 1) Secure MapR cluster.
> >
> > 2) Running drill-1.12.0 installed from MapR released RPM.
> >
> > 3) Re-using the configuration from drill-1.10.0.
> >
> >
> > Thanks,
> > Sorabh
> >
> >
> > From
ion from drill-1.10.0.
>
>
> Thanks,
> Sorabh
>
>
> From: John Omernik
> Sent: Friday, February 9, 2018 6:40:02 AM
> To: user
> Subject: Re: MapR Drill 1.12 Mismatch between Native and Library Versions
>
> I've made progress. I've pulled out th
From: John Omernik
Sent: Friday, February 9, 2018 6:40:02 AM
To: user
Subject: Re: MapR Drill 1.12 Mismatch between Native and Library Versions
I've made progress. I've pulled out the drill-yarn rpm, and realized there
was a drill.tar.gz file in there. I had a hunc
I've made progress. I've pulled out the drill-yarn rpm, and realized there
was a drill.tar.gz file in there. I had a hunch with the work that Paul
Rogers was doing on Drill on Yarn, that this was a executor package and
thus had the MapR stuff, but also the complete MapR stuff so it could be
downloa
So already, you have given me some things to work with. Knowing that there
may links to jars/3rdparty was very helpful. In opening that folder on
drill-1.12.0 I found there were no links/files related to mapr. In my
drill-1.10.0 version (both of them from MapR) there were three files,
maprfs, map
Can you also share the contents of (1) MapR build version on the cluster
nodes (cat /opt/mapr/MapRBuildVersion) (2) Drill RPM version installed (rpm
-qa |grep -i mapr-drill)
And also verify if the maprfs and maprdb jars inside
$DRILL_HOME/jars/3rdparty are links to the corresponding jars in
/opt/m
It might be to do with the way you've installed Drill.
If you've built and deployed Drill, odds are that the client will be different.
With the RPM installation, however, the installer has symlinks to make the
mapr-client libraries required by Drill be pointing to the libraries available
in /op
