Member since
02-01-2022
281
Posts
103
Kudos Received
60
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1120 | 05-15-2025 05:45 AM | |
| 4947 | 06-12-2024 06:43 AM | |
| 7918 | 04-12-2024 06:05 AM | |
| 5814 | 12-07-2023 04:50 AM | |
| 3202 | 12-05-2023 06:22 AM |
12-07-2023
04:50 AM
1 Kudo
@Fayza Nice work. If you can, you should try to remove ReplaceText. You should be able to get the payload exactly how you want it in text input box for GenerateFlowFile.
... View more
12-06-2023
05:42 AM
You need to send a flowfile to InvokeHttp that has the content you want. Make this flow to test: GenerateFlowfile (body of flowfile is the JSON payload), route to InvokeHttp. Your post headers are added to InvokeHttp in similar manner as to how you did "Body Content".
... View more
12-06-2023
05:15 AM
@Fayza Without seeing any error it is impossible for us to solve a specific problem. That said, I have some suggestions. 1. Always make sure you have a working api call. For example: Use Postman. You need to 100% know the call is working, auth, headers, proper format, proper payload, etc. This also makes sure the receiving end is open (networking, firewall, etc). 2. Test invokteHTTP without routing fail,retry,no-retry back to the processor. I use an output port for everything other than response. In testing, you need to know what happened. Inspect flowfile attributes inside of fail,retry, no-retry, to get more details. When i know my flow works, i may auto terminate, or re-route failure back to processor again, but NOT during testing/creation of the flow. 3. Last but not least, make sure that nifi host(s) are able to reach the endpoint. I suspect this is the issue you are bumping into. If you get invokeHttp talking to the endpoint, you should be seeing more details as to what if any errors are in the mutation payload.
... View more
12-05-2023
06:22 AM
1 Kudo
@neters Correct, this button should only restart the required services, NOT the entire cluster. The next screen should present more details before a final button to kick it off.
... View more
12-01-2023
06:05 AM
@I_Mesh01 This error is stating that your topic schema and flink schema do not match. I cant see much above related to the shape of the data or the schema, but this is what you should be looking at. Conflict in data/column types, missing data, etc, will result in the deserialization errors.
... View more
12-01-2023
05:54 AM
@matdulgi The drivers are able to be downloaded from public internet and you are able to use them accordingly. https://www.cloudera.com/downloads/connectors/impala/odbc/2-7-0.html https://www.cloudera.com/downloads/connectors/impala/jdbc/2-6-32.html.html
... View more
11-29-2023
04:39 AM
CHeck out this link @joseomjr shared in another post: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1 And here is a great blog from Pierre Villard: https://medium.com/cloudera-inc/getting-ready-for-apache-nifi-2-0-5a5e6a67f450 Nifi 2.0 brings python native, where jython was very limited library set.
... View more
11-28-2023
10:54 AM
@mango @joseomjr Currently DTLS not supported with ListenUDP. You certainly can build your own processor or work on a version of ListenUDP that includes the necessary code changes. Additionally it may be worth taking a look at the new python native capability in NiFi 2.0.
... View more
11-28-2023
06:01 AM
@ckumar is Correct. For large volume ingestion into the receiving host, you need a maria db host that can handle 1000s of transactions per second. Nifi can easily exceed default configurations for total connections. With a well tuned highly available mariadb, you can crank up execution time and concurrency on nifi and get 10,000s+ transactions per second.
... View more
11-28-2023
05:55 AM
@Hae I am not exactly sure of your settings or the issue with transactions, but I can share what is working for me. In my CDP Public Cloud nifi flows i use some required settings to PublishKafka. SSL Context Service:Default NiFi SSL Context Service Security Protocol: SASL_SSL SASL Mechanism: PLAIN Username: CDP Workload User Name Password: CDP Workload User Password Make sure you user has access to everything of course and you have set the workload password. Additionally, be patient on first processor run, sometimes takes minute or so of startup time to see SUCCESS. Then give refresh on SMM to make sure the kafka topic is created and has the expected data.
... View more