I have a partner who has used an external JSON SERDE jar to create hive tables (org.openx.data.jsonserde.JsonSerDe) … and the Drill installation cannot access the hive tables without that JAR in place.
I’m going to recommend not using the Hive table at all … accessing the json docs directly from Drill. — David On Dec 1, 2014, at 1:34 PM, Steven Phillips <[email protected]> wrote: > Sorry, I misread your email. I have no idea if that particular env.sh file > is sourced when drillbit is started up. I thought you were referring to > drill-env.sh. That is really the recommend file for putting drill related > environment changes. > > Might I ask why you need to modify the drill classpath? The only reason I > can think of for doing this is if you are adding UDFs, or have implemented > your own storage plugin. > > On Mon, Dec 1, 2014 at 1:21 PM, Steven Phillips <[email protected]> > wrote: > >> Yes, drill-env.sh would be the place to put this, regardless of how Drill >> is deployed. >> >> On Mon, Dec 1, 2014 at 1:08 PM, David Tucker <[email protected]> wrote: >> >>> >>> I can see the mechanics for adding additional jars to the invocation of >>> the drillbit via the DRILL_CLASSPATH environment variable (used in >>> $DRILL_HOME/bin/drill-config.sh). >>> >>> For drill deployments within a MapR cluster (where the mapr-drill package >>> is installed, so the drillbit is managed by the mapr-warden service), is it >>> reasonable to add the DRILL_CLASSPATH setting to $MAPR_HOME/conf/env.sh to >>> ensure that it is properly available to the service ? >>> >>> — David >>> >>> >> >> >> -- >> Steven Phillips >> Software Engineer >> >> mapr.com >> > > > > -- > Steven Phillips > Software Engineer > > mapr.com
