Member since
07-30-2019
3470
Posts
1641
Kudos Received
1018
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 249 | 05-06-2026 09:16 AM | |
| 437 | 05-04-2026 05:20 AM | |
| 315 | 05-01-2026 10:15 AM | |
| 506 | 03-23-2026 05:44 AM | |
| 385 | 02-18-2026 09:59 AM |
08-06-2024
05:18 AM
1 Kudo
@akash007 The ConsumeJMS processor configuration has an option to select a StandardRestrictedSSLContextService which would be configured with the keystore and/or truststore needed to facilitate your TLS connection with a secured JMS endpoint. For one-way TLS, You'll only need to configure the Truststore properties. If mutual TLS is needed, you'll need to configure both the keystore and truststore properties. Please help our community thrive. 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
08-05-2024
09:00 AM
@DeepakDonde I may not be completely clear on what you have tried above. I am not sure what you mean by "completely new process group". The rest-api endpoints used in both commands above are the same except each has a unique process group UUID: 1e373804-0191-1000-e950-856de82e267d <-- worked 01911000-3804-1e37-10a0-827d946513c6 <-- did not work The second throws an exception that implies the process-group with that UUID does not exist. That uuid needs to be the uuid of the process group in which you are uploading your flow definition. A flow definition will consist of a Process Group (PG) that normally contains components. I am guessing that the UUID you shared that did not work is some random uuid you created? When you flow definition is uploaded to the NiFi UI, its PG and components are assigned UUIDs. You can upload the same flow definition multiple times and each time all components get new UUIDs. NiFi Flow Definitions can only be created by right clicking on a Process Group and selecting "Download flow Definition" from the displayed context menu or via the equivalent rest-api endpoint. That flow definition is stored as a json file which can later be uploaded to the canvas of the same NiFi or to another NiFi. A flow definition is uploaded only by specifying the process group you want upload the flow definition to and the x and y coordinates at which the flow definition's Process Group will be placed. It is not possible to upload a flow definition without this valid information. Even a freshly installed NIFi will generate a root process group on first startup. When you access the UI of a new NiFi install, the blank canvas you are presented with is the root process group and has an assigned UUID (uuid is shown in the "operate" panel in left side of the canvas). Form that root process group you can add many levels of chid process groups and can upload a flow definition to the root process group or any child process group level. Please help our community thrive. 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
08-02-2024
08:33 AM
1 Kudo
@Adyant001 The JsonQueryElasticSearch processor does not store state. If the processor has no inbound connection, it will be scheduled to execute its code using the configured properties and scheduling configured. So upon every execution it is going to make the same same query to ElasticSearch. This processor can also be triggered by an inbound FlowFile. So you would have some upstream dataflow to build a query in to its content and that FlowFile is fed to the JsonQueryElasticSearch processor to fetch that specific result. The processor would then not execute again until it received another inbound FlowFile to trigger the execution. Please help our community thrive. 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
08-02-2024
06:44 AM
@kleyson Apache NiFi provides a simple to use UI that facilitates flow based programming through the used of hundreds of available components. NiFi's primary function is the ability to ingest unstructured data from a large variety of sources, transform, route , and push that data to a variety of destinations. While NiFi certainly has numerous HTTP processor components (ListenHTTP, HandleHTTPRequest, HandleHTTPResponse) that can be added to the canvas to support HTTP based connections into a dataflow, NiFi is so much more then just that. There are many many ways to ingest data in to NiFi and many many ways to manipulate, modify, generate, split, merge, write, send, etc. the data once it is inside NiFi. The NiFi documentation includes details on all the included components available in the download. Apache NiFi 1.x documentation: https://nifi.apache.org/docs/nifi-docs/ Apache NiFi 2.x documentation: https://nifi.apache.org/documentation/v2/ There are additional add-on NiFi nars that can add even more components. Please help our community thrive. 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
08-01-2024
02:10 PM
@Dave0x1 Add Encrypt and Decrypt PGP Processors and Services The EncryptContentGPG processor functions in accordance with the openGPG specification defined in RFC 4880. The specification has changed since then refreshed specification for OpenPGP , which have resulted in changes in the latest Apache NiFi 2.0 milestone releases: Remove Compression from EncryptContentPGP and SignContentPGP 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
08-01-2024
06:25 AM
1 Kudo
@Tiger_Name The encrypt-config toolkit was deprecated and removed in the Apache NiFi 2.0.0 release. https://issues.apache.org/jira/browse/NIFI-13414 It was refactored in 2.0.0-M1 (milestone 1) before it was deprecated and removed completely: https://issues.apache.org/jira/browse/NIFI-12243 Your exception sounds like something was not set correctly with regards to the master key in the bootstrap.conf. I'd double check to make sure you set that value correctly. Please help our community thrive. 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
08-01-2024
06:04 AM
@Althotta NiFi node disconnections are rarely the result of some underlying issue in NiFi code. Node disconnection are more commonly the result of resource consumption or configurations not being optimal in a NiFi deployment. This particular post if two years old. You should create a new post and provide details around your node disconnection issue and the specific Apache NiFi version you are running to get better assistance. The NiFi cluster UI is a good place to start. The "view details" icon to the far left for each node will provide you with node events which will include disconnect events along with reason. 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
07-30-2024
01:03 PM
1 Kudo
@kk-nifi Replay is not the proper way to handle failures. Failures should be handled in real-time through dataflow design. The "replay" option is only possible if NiFI still holds the content of the FlowFile you want to replay in its content repository. The replay ability is really built with the intention to be used in dataflow development testing ( Replaying a FlowFile ) Replay also required numerous manual steps making it difficult to automate retry. - First you need to execute a Provenance query. - From list of provenance events select the event(s) you want to replay one by one. - If content is still available you will have option to "replay" that FlowFile. There is also another option to "Replay last event", but again only works if last FlowFile's content still exists in the NiFi node's content repository. In your case, you talk about multiple failed FlowFiles for which this will not work to replay them all. NiFi stores the content in content claims with the NiFi content_repository. A content claim can hold the content for 1 too many FlowFiles. Once all FlowFiles referencing a content claim have reached point of auto-terminate, the claimant count would be zero. At that point the content claim will either be moved to archive or deleted depending on archive configuration. Even if archived, it is only retained for a limited amount of time. Also keep in mind that replay is NOT taking the original FlowFile and replaying it. Replay generates a new FlowFile with all the same FlowFile attributes and same content as the original FlowFile. Dataflow programatic handling is better. On failure configure auto retry as i described or route failure to some other processor(s) (optionally for tagging, updating, etc ) and then route back to failed processor. or better yet configured X number of auto-retry that only routes to "failure" relationships if all retry events end up failing. Please help our community thrive. 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
07-30-2024
10:57 AM
@Tiger_Name The issue you described matches up very well with https://issues.apache.org/jira/browse/NIFI-10018 which caused by https://issues.apache.org/jira/browse/NIFI-9988. While these jiras point at an issue in Apache NiFi 1.16.1, you are using the first milestone (M1) releases of Apache NiFi 2.0.0. So it quite possible that this issue may have been ported into the early milestone release. I would recommend downloading the latest milestone release of Apache NiFi 2.0.0-Mx, which at time of writing this is M4, to see if startup issue still presents itself. 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
07-29-2024
01:09 PM
@rich197 Providing the exact steps you perform to reproduce might help here. I am not clear in this step: "Next I attempted to upload a flow into a process group". Are you trying to upload a template or a flow definition? A flow definition is a Process group containing one or more components. A template can be just a collection of components (Templates are deprecated and removed as of Apache NiFi 2.x) Thank you, Matt
... View more