Hi Arvind, In the logs, I can find the Hive version is 3.1.3000.7.2.16.0-233. It's a CDP hive version. The exception was thrown from the creation of HiveConf. It seems a restriction added only in CDP Hive. To work around this check, you can try setting "hive.in.test" to true in the hive-site.xml used by Impala.
Regards, Quanlong On Wed, Mar 29, 2023 at 5:47 PM Arvind Dige <arvind.d...@ellicium.com> wrote: > Hi Quanlong, > > Please find the logs on the link below, This is publicly accessible. > > https://drive.google.com/file/d/1meM3JzVk9bYzrFvrYlz9Qw56dvXAS9Rs/view?usp=sharing > > Thanks, > Arvind D > > On Wed, Mar 29, 2023 at 2:43 PM Arvind Dige <arvind.d...@ellicium.com> > wrote: > > > Hi Team, > > > > I have successfully built Impala-4.2.0 and am currently integrating it > > with apache hadoop-3.1.1 and hive-3.1.3 with mapreduce engine. > > I am able to start hadoop daemons & hive service with metastore and hive > > server. > > But while starting Impala cluster, I found that Impalad is failing with > > an error as "mr execution engine is not supported". > > The curious thing is why impalad is using mr execution engine? > > Kindly help me to get it resolved. > > > > Thanks & Regards, > > Arvind Dige > > > > > > -- > Privileged/Confidential information may be contained in this message and > may be subject to legal privilege. Access to this e-mail by anyone other > than the intended is unauthorized. If you are not the intended recipient > (or responsible for delivery of the message to such person), you may not > use, copy, distribute or deliver to anyone this message (or any part of > its > contents ) or take any action in reliance on it. In such case, you should > destroy this message, and notify us immediately. If you have received this > email in error, please notify us immediately by e-mail or telephone and > delete the e-mail from any computer. If you or your employer does not > consent to internet e-mail messages of this kind, please notify us > immediately by e-mail. All reasonable precautions have been taken to > ensure > no viruses are present in this e-mail. As our company cannot accept > responsibility for any loss or damage arising from the use of this e-mail > or attachments we recommend that you subject these to your virus checking > procedures prior to use. The views, opinions, conclusions and other > information expressed in this electronic mail are not given or endorsed by > the company unless otherwise indicated by an authorized representative > independent of this message. >
