In general 3 files are needed: 1) Linux shell-script to invoke 2) Sql file with impala queries/commands 3) Keytab Those 3 files should be uploaded to the workflow deployment folder of the Oozie wf, and references as: <workflow-app name="logdirs" xmlns="uri:oozie:workflow:0.4"> <start to="invalidate_oozie"/> <action name="invalidate_oozie" cred=""> <shell xmlns="uri:oozie:shell-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <exec>${SHELL_SCRIPT}</exec> <env-var>PYTHON_EGG_CACHE=./python-eggs</env-var> <file>${SHELL_SCRIPT}#${SHELL_SCRIPT}</file> <file>${KEYTAB_FILE}#${KEYTAB_FILE}</file> <file>${SQL_FILE}#${SQL_FILE}</file> <capture-output/> </shell> <ok to="end"/> <error to="kill"/> </action> <kill name="kill"> <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/> </workflow-app> Later replace the variables when invoking the workflow. Then those 3 files will be avialble/reachable for the shell-script under the $PWD path. So kinit -kt <keytab_file> -V <username> can be done from the linux shell-script as kinit -kt $PWD/<keytab_file> -V <username> and impala invoked as: impala-shell -f $PWD/<sql_file> In reallity, because the script is invoked from the PWD path, $PWD variable could be ommited. The important is to include the 3 files in the Shell action to make them available on runtime.
... View more
