Hi @Sokka , I think its possible, can you try the below? """<workflow-app name="Workflow" xmlns="uri:oozie:workflow:0.5"> <start to="hive-04f4"/> <kill name="Kill"> <message>Error al realizar la acción. Mensaje de error [${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <!-- First Hive action to read data --> <action name="hive-04f4" cred="hive2"> <hive2 xmlns="uri:oozie:hive2-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <jdbc-url>jdbc:hive2://host:10000/default</jdbc-url> <script>${wf:appPath()}/hive-04f4.sql</script> <!-- Set output property to be used in next action --> <capture-output/> </hive2> <ok to="loop-decision"/> <error to="Kill"/> </action> <!-- Decision node to determine whether to execute next action --> <decision name="loop-decision"> <switch> <!-- If output is not null, execute next action --> <case to="hive-1c24">${wf:actionData('hive-04f4')['output'] != null}</case> </switch> <!-- If output is null, end the workflow --> <default to="End"/> </decision> <!-- Second Hive action to write data --> <action name="hive-1c24" cred="hive2"> <hive2 xmlns="uri:oozie:hive2-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <jdbc-url>jdbc:hive2://host:10000/default</jdbc-url> <script>${wf:appPath()}/hive-1c24.sql</script> <!-- Use output from previous action as input parameter --> <param>input=${wf:actionData('hive-04f4')['output']}</param> </hive2> <ok to="join"/> <error to="Kill"/> </action> <!-- Join node to synchronize paths after the second action --> <join name="join" to="loop-decision"/> <end name="End"/> </workflow-app>""" The <decision> node (loop-decision) contains a <switch> element with a single <case> element to check if the output of the first Hive action (hive-04f4) is not null. If it's not null, it proceeds to execute the second Hive action (hive-1c24). If it is null, it goes to the <default> path, which ends the workflow.   Regards, Chethan YM ... View more

Hi, I do not think query id will be present in jdbc driver logs( I have not tested it), It will be present in impalad INFO logs( server side). If you already tested and found query id is not present in driver logs then we cannot make it work other than getting the id from server logs. Get the query id in server logs and search it in driver logs for confirmation. Regards, Chethan YM     ... View more

Hi,   The error message you provided, "Server not found in Kerberos database (7) - LOOKING_UP_SERVER," is indicating an issue with the Kerberos authentication process. This error usually occurs when the Kerberos client is unable to find the server's principal in the Kerberos database.   Below is the article to troubleshoot kerberos related issues: https://community.cloudera.com/t5/Customer/Troubleshooting-Kerberos-Related-Issues-Common-Errors-and/ta-p/76192   > Please check if Ensure that DNS is correctly configured for both the client and the server. The client should be able to resolve the hostname of the server to the correct IP address. > Make sure the clocks of the client, server, and KDC are synchronized. Time differences beyond the tolerance set in Kerberos configuration can cause authentication failures. > Ensure that the Key Distribution Center (KDC) is reachable and operational. > Verify that the krb5.conf file on the client machine is correctly configured with the appropriate realms, KDCs, and other Kerberos settings.     Regards, Chethan YM   ... View more

Hi @hebamahmoud  You mean even after configuring the KUDU-HMS integration you are still facing the same issue/error? Can you confirm? Have you followed the given workaround on all HMS servers? https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/runtime-release-notes/topics/rt-pvc-known-issues-kudu.html   If that does not work can you try below and check?   CM > kudu > configuration> kudu service Advanced Configuration Snippet (Safety Valve) ==> --trusted_user_acl=impala,hive and restart the kudu services,   Regards, Chethan YM   ... View more

Hi, I do not think we have such option to create a view along with query option, you can follow any one of below: > Set the query option at session level before running the query. > Add this query option globally in impala configurations -> "default_query_options" section. > Add it in impala admission control pool for a specific pool where this query runs, edit the pool and add the property into "Default query options" section.   Regards, Chethan YM     ... View more