Member since
02-07-2019
2746
Posts
241
Kudos Received
31
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2330 | 08-21-2025 10:43 PM | |
| 2676 | 04-15-2025 10:34 PM | |
| 6970 | 10-28-2024 12:37 AM | |
| 2422 | 09-04-2024 07:38 AM | |
| 4416 | 06-10-2024 10:24 PM |
05-05-2026
08:02 AM
We are evolving our community content to ensure you always find the most relevant and up-to-date information, particularly as search and AI-driven tools become central to finding answers.
What We Did:
A large number of older posts, primarily from 2019 and earlier, have been moved to a read-only archive. These posts are no longer open for new replies, and they have been removed from standard community search and navigation to prioritize current discussions.
Why We Did It:
As our community has grown, older content sometimes surfaced with outdated product information or contains broken links. This archiving ensures that active discussions accurately reflect today’s products and workflows, addressing challenges like legacy threads competing with new conversations for visibility.
How It Benefits You:
By prioritizing recent and relevant content, we enable better, more accurate discovery. This strategic change ensures that both community search and external AI-powered tools are guided to the most reliable, up-to-date answers first.
Next Steps: If an archived post raises a new question, please start a new discussion and reference the original thread to ensure you receive a current response.
... View more
04-23-2026
10:29 PM
1 Kudo
Hello Community!
We recently updated a few community labels to align with the new product naming conventions (largely removing abbreviations) to better align with changes at the organizational level. This is part of an effort to make our product portfolio clearer, more consistent, and easier to navigate—whether you're exploring features, searching for help, or engaging in discussions here in the community.
Why the change?
As our products evolve, it’s important that their names reflect what they do and how they fit into the bigger picture. These updates help us:
Create a more unified product experience
Reduce confusion across documentation and support channels
Make it easier for you to find the right information quickly
You might have noticed some unexpected notifications related to these updates in the community. Due to the label changes tied to product renaming, some subscription notifications were unintentionally triggered.
We’re really sorry for the confusion this may have caused—and we appreciate your patience while we sorted it out. Everything should now be back on track.
What’s changed?
Here’s a quick look at the updated product names:
Old Product Name
New Product Name
Cloudera Data Platform (CDP)
Cloudera
CDP Private Cloud
Cloudera on premises
CDP Public Cloud
Cloudera on cloud
Cloudera Data Engineering (CDE)
Cloudera Data Engineering
Cloudera Data Platform Private Cloud (CDP-Private)
Cloudera on premises
Cloudera Data Science Workbench (CDSW)
Cloudera AI Workbench
Cloudera Data Warehouse (CDW)
Cloudera Data Warehouse
Cloudera DataFlow (CDF)
Cloudera Data Flow
Cloudera Hue
Cloudera Data Explorer
Cloudera Machine Learning (CML)
Cloudera AI
Cloudera Octopai
Cloudera Data Lineage
Cloudera Operational DB
Cloudera Operational Database
Cloudera Streaming Analytics (CSA)
Cloudera Streaming Analytics
Data Visualization
Cloudera Data Visualization
What’s Next?
No action is needed on your part! We appreciate your patience while we tidied things up. If you have any questions or notice anything unusual, just drop a comment below or reach out to our support team.
Best Regards, Cloudera Community Team
... View more
Labels:
04-23-2026
04:21 AM
1 Kudo
Hi @dylee Welcome to cloudera community! just wanted add some more details to @vafs response: you are encountering at https://archive.cloudera.com/cdp-public/ is expected behavior. Cloudera has changed how its repositories are structured and accessed, particularly for CDP (Cloudera Data Platform). The path cdp-public is not a browsable directory. To verify access and proceed with your trial installation, please refer to the following details regarding the repository structure and authentication: 1. The Repository Path has Changed For modern CDP installations, Cloudera often uses a different path structure. If you are looking for Cloudera Manager or Runtime artifacts, the URLs typically include a /p/ (private/protected) or a specific version prefix. Example for Cloudera Manager 7: https://archive.cloudera.com/p/cm7/ Example for Runtime: https://archive.cloudera.com/p/cdh7/ (Note that CDP Private Cloud Base artifacts are often under the cdh7 path). 2. Authentication Requirements (The "Paywall") Since February 2021, Cloudera moved its software behind a paywall. Even for trial environments, you generally cannot access the repositories without valid credentials. Trial Credentials: When you signed up for the CDP trial, you should have received a License Key or a set of Remote Repository Credentials (username/password). Verification: You cannot "browse" the root of the archive in a browser to verify access. Instead, you must test a specific file download using your trial credentials. If you do not have credentials, you can request them via the Cloudera Trial Portal or contact your Cloudera Account Manager. Test Command: curl -u <your_username>:<your_password> https://archive.cloudera.com/p/cm7/7.x.x/allkeys.asc If your issue has been resolved, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
04-20-2026
04:54 AM
1 Kudo
@RohanBajaj This is a very old thread with a very old version of Apache NiFi from the very early days of NiFi's introduction of the load balancing capability through the connections. I recommend you start a new community question with the specifics of any issue you are having to get the best possible assistance from the community members. Thank you, Matt
... View more
03-25-2026
06:18 AM
Hi @Karma12 , Could you please help us with the following details to investigate the query performance further: • The profile of slow query • The expected completion time for this query • The Impala coordinator logs corresponding to the query execution These will help us analyze the execution plan and identify any bottlenecks.
... View more
03-19-2026
05:37 AM
@Vishesh Sorry, but there is not enough information to give a definitive cause for your issue. There is typically full stack traces to go with these types of logged exceptions which can tell us more, but even then it may not be enough information still. As i mentioned before there are numerous improvements between Apache NIFi 1.23 and the last Apache NIFi 1.x release version 1.28. I'd strongly encourage you to upgrade to see if your issue persists. You may be hitting this bug NIFI-12232 which was addressed in versions 1.26+. 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. Thank you, Matt
... View more
02-22-2026
10:56 PM
@jI-mi, Did the response help answer your question? If so, please consider marking it as the solution so others can easily find it later.
... View more
02-14-2026
09:45 AM
Hello @Hasib1971, Are you still facing an issue or that was what solved your error? If you still have an issue, please open a new thread so we can help you there.
... View more
01-30-2026
07:22 AM
@gurumoorthyk have you found the answer to your question. If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
01-30-2026
01:38 AM
This Error refers to Hadoop ACLs The Azure ACL and RBAC was correctly assigned. The snapshot location must reside within the same directory as the HBase directory. The HBase user seems to have only access to this directory. For example, we used something like the following path: > abfss://storagefs@mystorageaccount.dfs.core.windows.net/cod-ouiftSmthLikeThis/hbase/.hbase-snapshot This confusion was caused by the default backup location set to the logs container during the environment creation. Follow-up questions: 1. Where is an official documentation or guidelines location addressing this topic? 2. What backups are stored in the default location? Only the cluster backups? 3. How can the Hadoop configuration be modified to allow the use of a different container for storing manual backups? 4. How can we give HBase the rights to access different storage locations?
... View more