Thank you @Bryan Bende! I thought variable registry could be modified on runtime to change workflow behavior. I think I'm not going to use the REST API to solve my design. It only implies penalization to the performance due to it is going to be done each time a new message from a sensor arrives. I could do the it obtaining those values from a DB but it has the same penalization. I will do a more static approach, routing with attributes and changing the design if the categories and/or the types of the sensors change. ... View more

When NiFi refactored it's security model between 0.x and 1.x lines, templates were moved to be associated with the process group where you uploaded the template. This was done so that template was protected by the same security policies as the process group where it was uploaded. Unfortunately the "View Templates" capability is still from the global menu, but should really be from the context palette on the left based on the process group you are in. ... View more

Glad to hear it! Can you please mark this answer as "accepted" ? ... View more

Thank you very much Bryan I'll follow that stackoverflow and further updates there. ... View more

@Bryan Bende looks like I have an option to use SegmentContent and MergeContent after I use ReplaceText on each segment. I tried it with 10mb segment size on a 120 mb file and it worked..now will try on the bigger file. ... View more

Thank you very much @Bryan Bende for your valuable inputs. I finally got it working by following your suggestion. Here is my working authorizers.xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <authorizers> <userGroupProvider> <identifier>file-user-group-provider</identifier> <class>org.apache.nifi.authorization.FileUserGroupProvider</class> <property name="Users File">./conf/users.xml</property> <property name="Legacy Authorized Users File"></property> <property name="Initial User Identity 1">CN=node1-nifi.jp.local, OU=NIFI</property> <property name="Initial User Identity 2">CN=node2-nifi.jp.local, OU=NIFI</property> <property name="Initial User Identity 3">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> </userGroupProvider> <accessPolicyProvider> <identifier>file-access-policy-provider</identifier> <class>org.apache.nifi.authorization.FileAccessPolicyProvider</class> <property name="User Group Provider">file-user-group-provider</property> <property name="Authorizations File">./conf/authorizations.xml</property> <property name="Initial Admin Identity">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> <property name="Legacy Authorized Users File"></property> <property name="Node Identity 1">CN=node1-nifi.jp.local, OU=NIFI</property> <property name="Node Identity 2">CN=node2-nifi.jp.local, OU=NIFI</property> <property name="Node Identity 3">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> </accessPolicyProvider> <authorizer> <identifier>managed-authorizer</identifier> <class>org.apache.nifi.authorization.StandardManagedAuthorizer</class> <property name="Access Policy Provider">file-access-policy-provider</property> </authorizer> </authorizers> Apart from the above changes, I have modified identity mapping pattern in nifi.properties nifi.security.identity.mapping.pattern.dn=^cn=(.*?),ou=(.*?),dc=(.*?),dc=(.*?),dc=(.*?)$ nifi.security.identity.mapping.value.dn=$1 Thanks again! ... View more

yes I've added some custom JARs. But my whole setup is created with ansible and I've tested it with NiFi 1.4.0 and 1.5.0. The error above occurs only with NiFi 1.5.0 and only if SSL is enabled. But good point, I can skip the copy JAR part and try it with an out of the box NiFi installation. Will do that and give feedback. EDIT: you were right, my splunk jar (for logging nifi logs) caused the problem. I've removed it and now I don't see any error ... View more

Based on all this info, it sounds like you have an identity mapping setup that maps your certificate identity like "CN=myuser, OU=xyz" to just "myuser". You can setup another identity mapping to handle kerberos identities... Something like this would map "myuser@myrealm" to "myuser" # nifi.security.identity.mapping.pattern.kerb=^(.*?)/instance@(.*?)$ # nifi.security.identity.mapping.value.kerb=$1 ... View more

Bin packing is the standard strategy that is used when merging together data, it just writes the bytes of each flow file one after another, inserting optional header, footer, and demarcators. Defragment strategy is for when you have previously used one of the "split" processors and want to undo the split back to a single flow file. This mode requires that all of the incoming flow files have the standard "fragment" attributes like fragment.identifier, fragment.index, and fragment.count which are created by the split processors. ... View more