Hi @rizalt  The error is because you have not provided keytab path here the command should look like below: > klist -k example.keytab To create the keytab you can refer any of below steps: $ ktutil ktutil: addent -password -p myusername@FEDORAPROJECT.ORG -k 42 -f Password for myusername@FEDORAPROJECT.ORG: ktutil: wkt /tmp/kt/fedora.keytab ktutil: q Then kinit -kt /tmp/kt/fedora.keytab myusername@FEDORAPROJECT.ORG Note: Replace the username and REALM as per your cluster configurations. Regards, Chethan YM ... View more

2.  An alternative is to write a script (e.g., Bash) that interacts with Hive and potentially your desired output format. ... View more

@vlallana, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more

@Anderosn  1. If the content of your flow file is too large to be inserted into a single CLOB column, you can split it into smaller chunks and insert each chunk into the database separately. 2. Instead of storing the content in a CLOB column, you can consider storing it in a BLOB (Binary Large Object) column in your database. BLOB columns can store binary data, including large files, without the size limitations of CLOB columns. 3. Store the content of the flow file in an external storage system (e.g., HDFS, Amazon S3) and then insert the reference (e.g., file path or URL) into the database. This approach can be useful if the database has limitations on the size of CLOB or BLOB columns 4. If ExecuteScript is not approved, consider using an external script or application to perform the insertion into the database. You can trigger the script or application from NiFi using ExecuteProcess or InvokeHTTP processors   Regards, Chethan YM   ... View more

This is how to resolve this problem: To resolve this issue, set this property to 0 and restart Impala: CM > Impala > Configuration > Impala Daemon command-line safety valve: -idle_client_poll_period_s=0 This is a startup flag, not a query option. Its default value is 30 seconds and that is why the session in the above excerpt was closed after 30 secs. By setting it to 0, Impala will not periodically check the client connection. The client connections will remain open until they are explicitly closed on the client applications' side. ... View more