@MintberryCrunch FYI ➤ In a Public Cloud Environment using Azure Operational Database (HBase), snapshot copy failures with a Permission denied error while acquiring a SAS token for get-acl on / typically stem from missing Access Control List (ACL) permissions on the root of the storage container, even if Azure Role-Based Access Control (RBAC) roles are correctly assigned. ➤ The AccessControlException at the root directory (/) indicates the driver is attempting to validate permissions at the top level before proceeding with the operation. ➤ Recommended Troubleshooting Steps 1. Grant the "Storage Blob Delegator" Role: Add this role to the Managed Identity used by the HBase service to ensure it can generate User Delegation SAS tokens. 2. Inspect ACLs via Storage Explorer: Use Azure Storage Explorer to right-click the root of the container and select Manage ACLs. Confirm the identity has at least Execute permissions. 3. Verify Firewall Settings: Confirm that "Allow trusted Microsoft services to access this storage account" is enabled in the Storage Account's Networking tab. 4. Check for Sticky Bits: Use the Azure CLI command az storage fs access show to see if the sticky bit is enabled on the target path.   ... View more

@gurumoorthyk adding to Smruthi's update, Iceberg + Hive+ Spark2 is not supported in CDP 7.1.9, it's officially supported from CDP 7.3.1. We don't need to add any jars explicitly in 7.3.1. By default, service[Impala,spark3, Hive] classpaths will have the required iceberg jars. In CDP 7.1.9, you can use Iceberg with Impala and Spark 3, but with limited functionalities. It does not require any classpath manipulation. Doc: https://docs.cloudera.com/cdp-public-cloud/cloud/cdp-iceberg/topics/iceberg-in-cdp.html FYI: [You can check the commands below in your env] [root@host1 jars]# pwd [You can see impala & spark3 classpaths by default has the iceberg jars] /opt/cloudera/parcels/ [root@ccycloud-1.nightly-71x-kl.root.comops.site jars]# find ../ -name *iceberg-hive-runtime* ../lib/oozie/oozie-sharelib-yarn/lib/sqoop/iceberg-hive-runtime-1.3.0.7.1.9.1003-449.jar ../lib/hive/lib/atlas-hive-plugin-impl/iceberg-hive-runtime-1.3.0.7.1.9.1003-449.jar ../lib/impala/lib/iceberg-hive-runtime-1.3.0.7.1.9.1003-449.jar ====>impala classpath ../lib/atlas/hook/hive/atlas-hive-plugin-impl/iceberg-hive-runtime-1.3.0.7.1.9.1003-449.jar ../jars/iceberg-hive-runtime-1.3.0.7.1.9.1003-449.jar [root@host1 jars]# find ../ -name *iceberg-spark* find ../.. -name *iceberg-spark* ../../SPARK3-3.5.4.3.5.7191000.0-30-1.p0.68499982/lib/spark3/iceberg/iceberg-spark-runtime-3.5_2.12-1.3.0.3.5.7191000.0-30.jar.  =====>SPARK3 Classpath ../../CDH-7.1.9-1.cdh7.1.9.p1003.74501001/lib/oozie/oozie-sharelib-yarn/lib/spark3/iceberg-spark-runtime-3.3_2.12-1.3.0.3.3.7191000.1-138.jar ../../CDH-7.1.9-1.cdh7.1.9.p1003.74501001/jars/iceberg-spark-runtime-3.3_2.12-1.3.0.3.3.7191000.1-138.jar ... View more

Pinging directly will not work as it is behind the firewall.  We need to use curl pointing to the proxy to connect to cloudera.com at the OS level (could be any internet hostname) My previous responses tested using curl calling our proxy server at the OS level where NiFi is running and it is working. Only NiFi using Configuration service (Proxy server: HTTP) seems to broken with 2.7.2.  Before the upgrade from 1.26 to 2.7.2, NiFi worked connecting to cloudera using our own proxy server. ... View more

@zhouweibo  As mentioned previously, please provide the DDL, sample data, and corresponding SQL to reproduce the problem. With this information, we can reproduce the problem locally and  offer an exact working solution.  ... View more

Hi @haridjh I tried to delete the VC using `cdp de delete-vc --vc-id...  --cluster-id...` and got an error result of auth failed: (Status Code: 403; Error Code: PERMISSION_DENIED; Service: de; Operation: deleteVc; Request ID: 94ac6721-5242-43d2-963b-c5b907ca030c;)   ... View more

@Pashazadeh  Apache NiFI 2.0.x was a technical milestone/preview releases that underwent many changes before the first GA release with NiFi 2.1.x.  I would not expect a change in behavior going forward, unless some bug is introduced or the community agrees on a change in functionality/behavior.   While I don't have a specific answer to what bug resulted in the difference in behavior you encountered, here are some changes that affected the JsonRecordSetWriter. NIFI-14331 NIFI-13963 / NIFI-13843 NIFI-12670 If you still have your NiFi 2.0.0 running, you could run your flow using a convertRecord with same record readers and writers and then compare the output content with what you see with 2.7.1 output.  Maybe that can help figure out what is happening and if either of those bugs affecting earlier NiFi 2.x versions is related. Thanks, Matt ... View more

Hello @shubham_rai  Could you please provide an update on this? Was the hive on Tez not restarted, or was a false stale entry present on the hive on Tez? Was a restart required or stale entry icon was gone on its own? Did you find any error in CM server logs? Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. ... View more

Thanks for responding with a resolution that worked for you, @Pedro_E. I'll mark your response as a solution.  ... View more