@Techie123  Can you provide more detail around your requirement for "t he FFs order is also important". My initial thought here would be a two phase merge.  In the first Merge you utilize a correlation FlowFile attribute you create on each FlowFile based off the employees ID extracted from the record.  Setting min number of entries to 7 and max to 10.  Then you take these employee merged records and merge them together in to larger FlowFiles using MergeRecord.  The question is if 100 records per FlowFile is a hard limit or not which it does not. The MergeRecord processor Max number of records is soft limit.  Let's assume we set this to 100. So lets say one of your merged employee records comes to the MergeRecord and has 7 records in it for that employee ID, yet the bin already has 98 records in it.  Since bin min has not been met yet, this merged FlowFile still gets added and results in merged FlowFile with 105 records.  If you must keep it under 100 records per FlowFile set the max records to 94.  If at end of adding a set of merged employee records it is less than 94 another merge employee record would be added and since you stated each set of merged employee records could be up to 7, this keeps you below or at 100 in that single merged record. 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

@Ghilani  NiFi stores Templates in the flow.xml.gz file.  the flow.xml.gz is just a compressed copy of dataflow(s) which reside inside NiFi's heap memory while NiFi is running.   It is not recommended to keep templates in your NiFi.  NiFi templates are also deprecated and will go away in next major release. It is recommended to use NiFi-registry to store version controlled flows.  If not using NiFi-Registry, Flow definitions should be downloaded instead of creating templates and stored safely somewhere outside of NiFi itself. A flow definition can be downloaded by right clicking on a process group in NiFi and selecting "Download flow definition".  This json file will be generated of that flow and downloaded.  Flow definitions can be uploaded to NiFi by dragging the create Process Group icon to the canvas and selecting option to upload flow definition.   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

@dreaminz  You can create variables on a process group, those variables are then only available to that process group (scope) on which they were created. NiFi documentation on Variables: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Variables Variable shave been deprecated in favor of Parameter Contexts: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#parameter-contexts You can create a single parameter context that you add parameters to and then associate the parameter context with multiple process groups.  This will allow you to update a parameter in one parameter context  and effectively update your flows in multiple process groups. 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

@grb  Your QueryDatabaseTable processor is failing because the dependent controller service is not yet enabled. It appears that controller services is still trying to enable (enabling) because the SQLServerDriver you have configured in that controller service is not compatible with the Java JDK version you are using to run NiFi. What version of NiFi are you using? What version Java is your NiFi using?  I recommend updating your Java version to the most recent version of Java JDK 8 or Java JDK 11 (Version 11 only supported in NiFi versions 1.10+).  Otherwise, you'll need to find an older version of your SQ driver. 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

@Vinylal  You can download the Cloudera Manager installer from the following Cloudera page: https://www.cloudera.com/downloads/cdp-private-cloud.html You'll need Cloudera username and password in order to access downloads from Cloudera.   If you account with Cloudera and don't know your credentials, you can reach out to your Cloudera account representative. 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

@drewski7  New processors are created within the community all the time and the documentation for processors should include resource considerations for CPU usage and Memory usage.  Just because a processor list memory as a resource consideration, that impact is often a byproduct of how that processor has been configured. you can refer to the imbedded documentation in your installed NiFi instance or you can right click on a processor added to the canvas and select "view usage" from the displayed context menu to go directly to that components embedded documentation page. But processors like ReplaceText, SplitText, SplitContent, SplitJson,... would be examples. 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

@Bridewin  I two things you may want to try.... 1. GetFile processor was deprecated in favor of the newer ListFile --> FetchFile processors.  I'd recommend switching to these processors and see if you have the same observations. 2. I'd suggest enabling debug logging for the GetFile processor class to see what additional logging may show.  To do this, you would modify the logback.xml file in NiFi's conf directory. Add the below line down in this file where you see similar lines already. <logger name="org.apache.nifi.processors.standard.GetFile" level="DEBUG"/>    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

@Jagapriyan I suspect issue with last modified timestamps since missed files have older last modified timestamp than what was already consumed from the target directory that is compounded by the sub-directory structure.  My recommendation is  switch to using the listing strategy "Tracking Entities" instead.  Tracking Entities will keep track of filenames and timestamps so even an older timestamped file will get consumed if its filename is not in the tracked entities list stored in the distributed cache. Let me know is making this change resolves yoru issue. 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

@PepeClaro  While NiFi supports parallel thread execution, there is no way to guarantee that two threads execute at the exact same time.  So one NiFi component processor is unaware of what another NiFi Component processor is doing or when it is executing.  Processors that have an inbound connection on them use an inbound connection queued FlowFile as the trigger to perform start execution. Step 1 is to identify what NiFi component processors can be used to perform/execute your 3 processes: https://nifi.apache.org/docs.html I have no idea form your description what your 3 processes do, so I can't make any recommendations on what you can/should use. Step 2 is deciding how to interconnect these NiFi processor component and preserve data needed for downstream dataflow processing in your third process.  When a processor executes the response/return from the execution can result in modification to existing NiFi FlowFile's content, Creation of new FlowFile content, Creation of an entirely new FlowFile, Creation of new FlowFile attributes (key/value pairs), modification of FlowFile attributes, or none of the above depending on the NiFi component processor being used.  Since you mention that first 2 processes get info that is needed by process 3, so would need to take that into consideration for process 3. Where is that info go ing to end up (FlowFile Content or FlowFile attributes)?  How large is that info returned (does it make sense to put it in to attribute)?  Does that returned info need to be modified in any way before process 3? In your Flow as described, you have two Process Groups (PG),  Each of these PGs performs your process 1 and process 2.  Each will be executing independent of the other and thus can not guarantee execution at the exact same time.  Cron scheduling of a processor can give a better chance of same time execution but still not a guarantee since it only schedules when to request an available thread from the NiFi Max Timer Driven Thread pool.  If at time of request all threads are in use, it will execute as soon as thread becomes available. Now out of these two PGs you will have two FlowFiles that your third process depends on.  There is no way to tell a NiFi processor component to pull attributes or content from two different FlowFiles source FlowFiles.  So before process 3 you need to combine any needed attributes and or content from the two original FlowFiles into one FlowFile that Process 3 can use.  Hard to make a recommendation here since I don't know any details about your 3 processes, what the FlowFiles that are produced by Process 1 and 2 contain in terms of content and attributes, and what content and/or attributes from process 1 and 2 are needed by process 3.   I made suggestion about maybe being able to use the "defragment" merge strategy from the MergeContent processor to combine the FlowFiles from process 1 and process 2, but not enough detail to say or say without needing to do other modification before MergeContent.  To "defragment" (combine process 1 fragment with process 2 fragment), the FlowFiles produced by both process 1 and process 2 would need to have the following FlowFile attributes present and set correctly on each:   Name Description fragment.identifier Applicable only if the <Merge Strategy> property is set to Defragment. All FlowFiles with the same value for this attribute will be bundled together. fragment.index Applicable only if the <Merge Strategy> property is set to Defragment. This attribute indicates the order in which the fragments should be assembled. This attribute must be present on all FlowFiles when using the Defragment Merge Strategy and must be a unique (i.e., unique across all FlowFiles that have the same value for the "fragment.identifier" attribute) integer between 0 and the value of the fragment.count attribute. If two or more FlowFiles have the same value for the "fragment.identifier" attribute and the same value for the "fragment.index" attribute, the first FlowFile processed will be accepted and subsequent FlowFiles will not be accepted into the Bin. fragment.count Applicable only if the <Merge Strategy> property is set to Defragment. This attribute must be present on all FlowFiles with the same value for the fragment.identifier attribute. All FlowFiles in the same bundle must have the same value for this attribute. The value of this attribute indicates how many FlowFiles should be expected in the given bundle. segment.original.filename Applicable only if the <Merge Strategy> property is set to Defragment. This attribute must be present on all FlowFiles with the same value for the fragment.identifier attribute. All FlowFiles in the same bundle must have the same value for this attribute. The value of this attribute will be used for the filename of the completed merged FlowFile. Fragment.identifier, fragment.count, and segment.original.filename need to have same values on both FlowFiles.  Fragment.index would be unique. The result would be one output FlowFile with the FlowFile content of both original process 1 and process 2 FlowFiles which process 3 could the use.  Or if process 1 and 2 produce FlowFiles with just FlowFile Attributes you need and not content, you could set " Keep All Unique Attributes" as the attribute strategy so that the 1 merged FlowFile has all unique attributes form both source FlowFiles for process 3 to use. 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

@PepeClaro  Your description is vague which makes it difficult to provide suggestions around incorporating them into a dataflow design. - What are these three "processes"? - How are those processes being executed? What processors in use for these 3 processes? - Are there any dependencies between these processes other then order of execution?  For example, is output from processes 1 and/or 2 needed by process 3?   - Do processes 1 and 2 need to be executed in parallel? - Is your NiFi a multi-node cluster?  - What are the triggers for these processes? Does it require a NiFi FlowFile to trigger each processes? What kicks off this entire process dataflow? The more detail the better would be helpful.  You may be able to set a fragment identifier, fragment count (2), and fragment index (1 or 2) for the first two process FlowFiles and then merge those fragments into one FlowFile that can trigger the third process. If either fragment is missing it will not merge and thus not trigger the 3 process. If not needing process 1 and 2 in parallel, then a single dataflows process1 --> process 2 --> process 3 where a failure anywhere along the dataflow prevents execution of next process. 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