@AlokKumar  The more detail you provide the better response you will get. In this case, more detail around the content/format of the source file (samples are great) and how it is being or will be processed downstream.  A NiFi FlowFile is what is passed from one processor component to the next.  There is no direct relationship between what processing was done in one processor versus another.  Each Processor will read the FlowFile (consists of FlowFile Attributes/metadata and FlowFile content) and execute its processor code against the FlowFile and output a FlowFile(s) to one or more outbound relationships.  So processing against the content of A FlowFile becomes the responsibility of each processor separately.   So the questions asked correlate to the answer you'll get. With what you shared, I can only suggest that you remove the first line from the content of the FlowFile so that downstream processor will only have line 2 to process against.  This can be accomplished easily with a ReplaceText processor.  Simply configure it for  "Evaluation Mode" = "line-by-line", "line-by-line Evaluation Mode" = "First-Line", and in "Replacement Value" property "Set empty string" check box. The output FlowFile' content, which is sent to the success relationship, will have everything except its first line.  Do you need to preserve line 1? If so, maybe use ExtractText to extract line 1 to a FlowFile attribute you can then use after processing to add back to Content again using ReplaceText. 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

@jcsilva @gourexe  The red flag that stands out here is that you stated you were using NiFi 1.16.2 and trying to upgrade to Nifi 1.16.3; however, you then state that the problematic component is version 1.18.0.   This implies that you or someone else added additional nar files from NiFi 1.18.0 to your NiFi 1.16.2 install lib directory.  Those newer version components may have introduced new properties that do not exist in the NiFi 1.16.x versions.  When you upgraded to NiFi 1.16.3, those 1.18.0 nar versions no longer exist, so NiFi attempts to load the same class from 1.16.3 thus resulting in your issue. You should instead upgrade to 1.18.0 or newer version or you'll need to add in the additional nars once added before from 1.18. 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

@NaveedButt  The exception you shared is complaining about the nifi.sensitive.props.key property not being set in the nifi.properties file at startup: This pops key value is used to encrypt all sensitive component properties created in the flow.json.gz as you build your dataflows via the NiFi canvas. If you have not built any dataflows that utilize sensitive properties in the component configurations, you can just set some value and start your NiFi.   If you have already existing dataflows on your NiFi canvas containing sensitive values set (passwords) in the configurtion(s), you'll need to retrieve the exact password from the original nifi.properties and use that.  If original props key is not set, NiFi will fail to start when it tries to load the flow.json.gz since it will not be able to decrypt those passwords using the new props key. If you get stuck, you can carefully manually edit the flow.json.gz and remove all "enc{.....}" values.  This will allow you to start your NiFi using a new sensitive props key value; however, all your configured passwords will be cleared and you will need to enter them again into your various component configurations. 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

@AlokKumar  You have multiple questions here, let me address them separately: Renaming your content file:  A NiFi FlowFile holds its filename in a FlowFile Attribute named "filename".  You can use the UpdateAttribute processor to change/modify a FlowFiles filename through the use of the NiFi Expression Language (NEL) Add a dynamic new property to the UpdateAttribute processor using the "+"icon in upper right corner of [processors configure window. "Property" = FlowFile attribute to be modified (filename).  Value = A FlowFile NEL statement that manipulates the existing filename as desired.  Example:    ${filename:substringBeforeLast('.')}_${now():format('MM_dd_yyyy_hh_mm')}.${filename:substringAfterLast('.')}​     With above example, I passed my UpdateAttribute a FlowFile with a "filename" attribute of "testfile.txt".  The above sample NEL statement modified the filename attribute on the FlowFile to "testfile_09_09_2024_12_57.txt". Archive a FlowFile:  You were not clear on how you want to handle your archived files.  Do you have some external service that monitors and cleans out your archive folder? NiFi has a PutFile processor that can write FlowFiles to some local directory on your local NiFi instance or other processors that may be able to write to an external service. If you are looking for NiFi to monitor that directory and purge archived files after 30 days, you would need to build another NiFi dataflow to handle that.  For example: GetFile (configured with minimum File age of 30 day) which you then auto-terminate its "success" relationship.  This will consume files older then 30 days and purge them from the configured directory. 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