Member since
07-30-2019
3471
Posts
1642
Kudos Received
1020
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 173 | 06-03-2026 06:06 PM | |
| 462 | 05-06-2026 09:16 AM | |
| 836 | 05-04-2026 05:20 AM | |
| 504 | 05-01-2026 10:15 AM | |
| 630 | 03-23-2026 05:44 AM |
08-08-2023
12:01 PM
Yep! Had moved on to that after your response and written up a JIRA for my team to build the needed tool. Thanks again for the response. My plan is the below > Find all the processors which may have state, then check if each has state, and if so, clear it. Find processors of used types which can contain state: e.g., QueryDatabaseTableRecord For each, pull the state by the ID and check if it has any stored state if totalEntryCount of cluster or local state is non-zero If so, call the clear state endpoint Query URL: /nifi-api/flow/search-results?q=QueryDatabaseTableRecord Pull Processor State: /nifi-api/processors/41584e33-adc6-171d-0000-0000581caccb/state Clear Processor State: POST /nifi-api/processors/41584e33-adc6-171d-0000-0000581caccb/state/clear-requests
... View more
08-08-2023
08:54 AM
Sure. I had to make some extract it from a larger PG and make some adjustments due to key code being in a parameter. But the remainder of the parameters are really placeholders for your environment information. The main complication might be that I used a few external controller services that you will have to replace. But their names in the externalControllerServices JSON should help you replace them.
... View more
08-07-2023
11:10 AM
1 Kudo
@sam_s0ni Apache NiFi never intended with the context of the NiFi framework to allow parameters to be dynamically accessed within NiFi Expression Language (NEL). The EvaluateElString() exposed a bug in which this was possible while never intended. That bug was addressed in apache NiFi 1.19 thus resulting in what you are seeing. As an alternative, you could store your schemas in an external database and pull those schemas back dynamically based on a FlowFile attribute instead of using Parameter contexts to store those schemas. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
08-07-2023
04:01 AM
Thanks MattWho, Yeah We figure out that the causing of issue the special character. Thank you Very Much
... View more
08-04-2023
01:37 PM
@MWM MergeContent is probably not the processor you want to use to merge your JSON files as it will simply concatenate them together instead of creating one larger json. You should use the MergeRecord processor instead. In this processor you can specify a JsonTreeReader to read your source Json files and then use a CSVRecordSetWriter to output merged CSV file(s). The rest of the MergeRecord processor configuration will control how many source Json records are added in to a single output CSV. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
07-31-2023
08:11 AM
@Kiranq What version of Java is your NiFi using? Sharing the output for your NiFi-Registry configured keystore and truststore in the nifi-registry.properties file would help. Sharing the keystore and truststore configured in your NiFi registry client would help as well. ./keytool -v -list -keystore <keystore or trustsore> You can also use openssl to see what is sent from the server (NiFi-Registry) to client (NiFi) in the initial TLS exchange. ./openssl s_client -connect <nifi-regisry hostname>:<NiFi-Registry port> -showcerts Matt
... View more
07-31-2023
08:01 AM
@Sivaluxan NiFi exposes APIs for a lot of endpoints. So not really sure what you are trying to accomplish in your use case. If you want to use a third party app to access info exposed by NiF that is possible. Or are you trying to setup some custom endpoint to expose some custom data? Here you can find NiFi Rest-Api documentation for the latest NiFi release: https://nifi.apache.org/docs/nifi-docs/rest-api/index.html You can also find the NIFi rest-api documentation for your installed release directly in the application via the global menu ( 3 horizontal lines upper right corner of UI) --> help. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
07-28-2023
05:21 PM
@Fabricio Has the reply helped resolve your issue? 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. Thanks.
... View more
07-27-2023
10:03 AM
@Luwi I agree that it is likely not some kinda of quota and rather a connection interruption and since the default timeout in the smtp client is indefinite, the PutEmail processor will never timeout the bad connection and then execute a new thread to establish a new connection. The Jira (https://issues.apache.org/jira/browse/NIFI-9758) I mentioned in previous response provides the new capability to set smtp timeouts to resolve this issue. You'll need to upgrade to Apache NiFi 1.17 or newer to get this processor improvement. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more