Oozie shell action environment and .impalarc

nbest — Fri, 16 Sep 2022 09:43:53 GMT

I have an Oozie shell action that calls impala-shell and has been working fine. I wanted to set some defaults in ~/.impalarc which works fine from the shell but doesn't seem to get applied during workflow execution. When I look at the environment variable values in the shell action log it says:

. . .

USER=etl-user:

. . .

HOME=/home/:

. . .

USER looks right but I expect HOME to be either /home/$USER or /home/etl-user.

Does this influence where impala-shell looks for .impalarc when running under an Oozie shell action?

I was hoping to get this done by distributing my .impalarc to ~etl-user on all of the cluster nodes and not chenge the workflow definition but no joy.

The objective is to change the default --impalad=host:port argument to point at the Impala high availabilty proxy that we have set up.

Re: Oozie shell action environment and .impalarc

Robert Justice — Thu, 22 Oct 2015 19:59:31 GMT

Neil, You could scp the .impalarc to the /home directory on all nodemanager nodes and make sure this was readable by all. Thanks, Robert Justice

question Oozie shell action environment and .impalarc in Archives of Support Questions (Read Only)

Oozie shell action environment and .impalarc

Re: Oozie shell action environment and .impalarc