@Sunil Neurgaonkar As I explained there are two levels of policies, global (controls global feature access (controller settings, provenance queries, user management, etc..) and component level access policies (controls level of user access to components added to canvas) Global policies include the following: Component level access policies include: By default components inherit the policies of the parent process group they are created in. Thanks, Matt If you found this answer helpful to your original question, please accept the answer. ... View more

@Sunil Neurgaonkar If user 1 does not have view or modify to user 2 or user 3 process groups, all user 1 will see is a ghosted boxes for those processors, remote process groups, process groups, etc. User 1 will not be able to view the configuration or FlowFiles that pass through these components either. He will not even be able to identify what kind of processor it is. The only thing they can see are the stats. This is important since all dataflows run within the same JVM. So understanding where a backlog somewhere else in the flow exists can be important. I suggest creating a label that is viewable by all users fro each process group that provides a POC for that process group in the even their is an issue. Another reason you would not want hide these components completely, is to avoid users stacking components on top of each other. Lets say user 2 can see both user 1 and user2 components, but user 1 can only see his components. User 1 now has no way of knowing where components exist making it very hard for user 2 to view the canvas since he would see all components potential layer on top of one another. Perhaps I am missing something in your use case, but I don't see the benefit or vulnerability introduced by allowoing all users to see these ghosted components. Thank you, Matt ... View more

@Anil Reddy Since you don't know where in the content these four fields will fall, I would suggest using the following: The other regex rules I provided expect address as the last field. these will work no matter where in the content these patterns are found. The .*&firstname=(.*?)&.* will not work in all cases since it expect you to have 1 or more characters followed by "&filename=" followed by a many characters up to the last found "&" followed by 1 or more trailing characters. This expression will not work should firstname be the first or last field in the content. Thank, Matt If you found my answers helpful to your question, please mark it as "accepted" ... View more

@Anil Reddy You can get rid of capture group 0 by changing the "Include Capture Group 0" property to false. Capture groups are defined using (). what falls between them is a capture group. You can create a single java expression that has multiple capture groups. So the ExtractText processor creates a attribute for each of these capture groups. Then the complete result of the regular expression is assigned to the property name you created. In the above i have created four different java regular expressions. Each runs against the content of the incoming FlowFile. Each Regex has one capture group (.*?). As result you will have address.1= to that one defined capture group. NiFi also wants to create the attribute as you defined with just "address". so the <propertyname>.num attributes are created because of the use of capture groups in your regex. For example, let assume the firstname property had the following regex: firstname=(.*?)[&]{1}lastname=(.*?)[&]{1} Here you see i have two capture groups in one regular expression. This would translate in to two new attributes on your flowfile: Thanks, Matt ... View more

@Anil Reddy Are the four fields you are trying to extract the values from consistently: "firstname" "lastname" "email" "address" ... View more

@Anil Reddy Your new example does not use a "&" between all your fields. Is that a typo? I see "&" between first two fields and "," after that. ... View more

@Gaurav Jain NiFi does not redistribution of FlowFiles at this time between nodes behind the scenes. Any redistribution of FLowFiles between nodes in a cluster has to be done programmatically through your dataflow design via components (processors like postHTTP to ListenHTTP or RPG) to push FlowFiles to other nodes. Thanks, Matt ... View more

@Gaurav Jain When you find an answer in Hortonworks Community Connections (HCC) that addresses your question, please accept that answer so that other HCC users know what worked for you. Thank you kindly, Matt ... View more

@Gaurav Jain Here is an article i wrote awhile ago that explains the differences between using GetSFTP processor or List and Fetch SFTP processors: https://community.hortonworks.com/articles/97773/how-to-retrieve-files-from-a-sftp-server-using-nif.html Thanks, Matt ... View more