Member since
11-17-2021
1123
Posts
254
Kudos Received
29
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 540 | 11-05-2025 10:13 AM | |
| 325 | 10-16-2025 02:45 PM | |
| 649 | 10-06-2025 01:01 PM | |
| 576 | 09-24-2025 01:51 PM | |
| 475 | 08-04-2025 04:17 PM |
06-24-2025
09:00 PM
@WMichael As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.
... View more
06-20-2025
12:27 PM
@csm09 As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.
... View more
06-19-2025
02:48 PM
1 Kudo
Provenance/lineage is not currently visible from the Flow Designer. This is intended because the Flow Designer UI is for flow design regardless of whether there is a Test Session or deployment active. Provenance and lineage is associated with actual data running through a deployment, so to view these you'll need to navigate to the Cloudera Flow Management (NiFi) canvas from the deployment view once your flow has been deployed. From the canvas you can proceed as the video instructs and hopefully it looks familiar at that point.
... View more
06-13-2025
10:54 PM
@NaveenSagar Welcome to the Cloudera Community! To help you get the best possible solution, I have tagged our NiFi experts @MattWho @SAMSAL who may be able to assist you further. Please keep us updated on your post, and we hope you find a satisfactory solution to your query.
... View more
06-10-2025
10:52 PM
Dear Mike, Thank you for your support. I would like to highlight that I do not have internet access within CDSW, as our Cloudera environment is fully air-gapped. From your previous message, I understand that you are suggesting I create a custom Docker image and run it accordingly. I have already created a custom Docker image — however, I would appreciate it if you could review it and provide your feedback. Additionally, could you clarify your expectations regarding the base operating system for the container image? and the Base image? For your reference, we are using CDSW version 1.10.5. Best wishes, Salim ### **Description of the Docker Image** This Docker image is a **customized environment** tailored for Cloudera Data Science Workbench (CDSW) in an **air-gapped (offline)** setting. It includes the following components: 1. **Base Image**: - Starts with `docker.repository.cloudera.com/cdsw/engine:8` , ensuring compatibility with CDSW. 2. **Operating System**: - **Ubuntu 20.04 LTS**, a lightweight and stable Linux distribution. 3. **MySQL 8.0.4**: - A milestone release of MySQL, installed from pre-downloaded `.deb` packages (no internet required). 4. **Python 3.8.18**: - Compiled from source to ensure version compatibility. 5. **Node.js 22.16.0**: - Installed via a pre-extracted binary archive. 6. **Grafana Enterprise 11.6.0**: - Installed using a `.deb` package for enterprise-grade monitoring. 7. **Ollama**: - A pre-downloaded binary for running large language models locally. 8. **Python Packages**: - Installed **offline** from a pre-downloaded `requirements.txt` file and local wheels (`.whl` or `.tar.gz`) . 9. **Exposed Ports**: - MySQL (3306), Python apps (8000), Grafana (3000), and Ollama (11434). --- ### **Requirements to Build the Image** To build this image in an **air-gapped environment**, you must pre-download and include the following: 1. **Pre-downloaded Dependencies**: - **MySQL 8.0.4 `.deb` packages** (from Cloudera or MySQL archives). - **Python 3.8.18 source tarball** (from [python.org](https://www.python.org/ftp/python/3.8.18/)). - **Node.js 22.16.0 Linux x64 binary** (from [nodejs.org](https://nodejs.org/dist/v22.16.0/)). - **Grafana Enterprise 11.6.0 `.deb` package** (from Grafana’s enterprise download page). - **Ollama binary** (from [ollama.ai/download](https://ollama.ai/download)). 2. **Offline Python Packages**: - Use `pip download -r requirements.txt -d python_packages/` in an online environment to fetch all dependencies locally . 3. **Directory Structure**: Ensure the following files/directories exist in the build context: ```bash . ├── Dockerfile ├── requirements.txt ├── ollama # Pre-downloaded Ollama binary └── dependencies/ ├── mysql-8.0.4/ # MySQL .deb packages ├── python/ # Python 3.8.18 source ├── node-v22.16.0-linux-x64.tar.xz ├── grafana-enterprise-11.6.0.deb └── python_packages/ # Pre-downloaded Python wheels ``` 4. **Build Command**: Run: ```bash docker build -t custom-cdsw:latest . ``` 5. **Push to Private Registry (Optional)**: For CDSW integration, push the image to a registry accessible by CDSW: ```bash docker tag custom-cdsw:latest <your-registry>/custom-cdsw:latest docker push <your-registry>/custom-cdsw:latest ``` --- ### **Key References** - Docker images contain application code, libraries, tools, and dependencies . - Use `docker inspect` to view details about the image . - Dockerfiles are often shared in repositories for transparency . Let me know if you need further clarification!
... View more
06-10-2025
05:35 AM
@agriff I did not know that you were using the Apache NiFi 2.x release. The component list I provided is from the Apache NiFi 1.x release. NiFi 2.x switched from having numerous client version Kafka based processors to single Kafka based processors that now use a KafkaConnectionService controller service component to define the kafka client version. In Apache NiFi the only connection service included is for theKafka 3 Client. The Kafka client 3 I understand to be backwards compatible to Kafka 2.6, but sounds like you are having success with using it for Kafka 2.5. Glad to hear you were able to resolve yoru underlying schema issue. Setting Bulletins level on a processor has absolutely nothing to do with log levels written to the nifi-app.log. It only controls what level bulletins are created within the NiFi UI. To change logging within the NiFi logs, you will need to modify the logback.xml configuration file found in the NiFi conf directory. 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
06-09-2025
11:57 AM
Hello @mburgess @MattWho do you have any insights here? Thanks!
... View more
06-05-2025
01:40 PM
Hello- The error you have provided: "ODBC: ERROR [HY000] [Microsoft][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct." - is quite obscure. The following could cause it: a. outdated ODBC Driver b. intermittent network issue c. misconfigured or malfunctioning Load Balancer. d. invalid certificate(s) on one or few Impala coordinators (behind the Load Balancer). - each of the above or some combination of those. In order for us to help you with troubleshooting, please open a case with Cloudera Support. Thank you.
... View more
06-05-2025
12:51 PM
@Steja Welcome to the Cloudera Community! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.
... View more