If the JAVA_HOME is set in a terminal session (like a screen session), switching might not pick up the changes. Usually, logging into a new session (with an updated bash profile, if you use bash) should pick up the correct Java and obviate the need for a cluster restart.
-----Original Message----- From: Ben Knorr [mailto:[email protected]] Sent: Tuesday, August 05, 2014 9:00 AM To: [email protected] Subject: Re: Apache Drill Installation : select * from sys.drillbits Failing I had an issue with this previously. I had opendk installed and got this issue. I switched to Oracle JDK, and still had the issue. It seemed that restarting Drill wasn't enough to recognize the switch in java versions. I shut down the cluster (for other reasons), and once I brought it back up, everything worked fine. On Tue, Aug 5, 2014 at 9:43 AM, Jacques Nadeau <[email protected]> wrote: > Message tells you. You need to install jdk. > On Aug 5, 2014 7:02 AM, "mufy" <[email protected]> wrote: > > > Any idea what could be possibly causing this? > > > > 0: jdbc:drill:zk=mufeed-drill1:5181,mufeed-dr> select * from > sys.drillbits; > > Query failed: Failure while setting up query. JDK Java compiler not > > available - probably you're running a JRE, not a JDK > > [8fbd4c3b-aa9f-45e4-9172-d124498f587e] > > > > Error: exception while executing query: Failure while trying to get > > next result batch. (state=,code=0) > > > > > > --- > > Mufeed Usman > > My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | > > My Social Cause <http://www.vision2016.org.in/> | My Blogs : > > LiveJournal <http://mufeed.livejournal.com> > > >
