@JamesE  This is easy enough do using the splitContent processor: for the "Byte Sequence" property simply hit your spacebar to set a single space. If you found this answer addressed your question, please take a moment to accept to resolve this thread.   Hope this helps, Matt ... View more

@justenji    What version of NiFi-Registry are you using? If the NiFi-Registry version is older then 0.5.0, you will encounter this bug. https://issues.apache.org/jira/browse/NIFI-6025 Hope this helps, Matt ... View more

@VijaySankar    Is there a full stack trace that follows the error message in the actual nifi-app.log? Is this a multi-node NiFi cluster that perhaps has multiple Nodes installed and running on the same server? If so, when you start the processor only one node is going to be able to bind to the configured port and the other nodes will throw the exception.  Since both nodes are on the same host, the processor will appear as though it is working because the node that did bind will receive the requests.  It is also possible that port 9099 is not unused on every host in your NiFi cluster.  Since the bulletin you are sharing indicates a specific hostname:port, it is possible that port 9099 is already in use by some other process on that one host.  But on your other host(s) it is not in use and binds successfully allowing those host(s) to receive request fine. I recommend stopping the HandleHttpRequest processor and then from command line check to see if there is anything still listening on port 9099.  If so, you'll need to use another port that is available on all your NiFi nodes. Hope this helps, Matt ... View more

Hello @Former Member  Now that you have both NiFi and NiFi-Registry secured they will use TLS to authenticate with one another.  NiFi-Registry does not initiate any connections to NiFi.  NiFi will always act as the client talking to NiFi-Registry. 1. All 3 of your NiFi nodes must exist as users in the NiFi-Registry. 2. Any users who will be version controlling NiFi process Groups will need to exist as users in NiFi-Registry. 3. Your NiFi nodes must be authorized in NiFi-Registry for "Can proxy user requests" and read for "can manage buckets".  Found by clicking on settings in NiFi-Regsitry UI, then selecting Users tab, and clicking pencil to right of each of your NiFi nodes. 4. You users must create a bucket(s) in NiFi-Registry and authorize your NiFi user(s) for read, write, delete on the bucket.  From same setting UI click buckets tab, click "add bucket" then using pencil to left of bucket authorize your user(s). 5. From the NiFi UI, click on the global menu (upper right corner) --> Controller Settings --> Registry Clients tab.  Click the "+" icon to add a new NiFi-Registry client.  Provide the HTTPS://<nifi-regsitry-hostname:port> as the URL and a name of your choosing. Provide the keystores and truststores created for your NiFi and NiFi-Registry can support mutual authentication between these two services, you will be good to go.  Otherwise check your nifi and nifi-registry app logs for any TLS handshake errors which would need to be resolved. Hope this helps you get going with NiFi-Registry, Matt ... View more

@stevenmatison    I don't see any reason why you can not do this.  Do NOT put the 1.10 nar in to NiFi's defualt lib directory. Instead create a new custom lib directory by adding a new property to the nifi.properties file: nifi.nar.library.directory.custom1=/<path>/custom-libs  Copy the 1.10 parquet nars in to this directory and make sure the permissions and ownership are set correctly for this custom path and libs so that the NiFi service user can access them.   Once NiFi is restarted, you should see both versions of the parquet processor available for adding to the NiFi canvas. Note: Adding additional versions of the same nars can make upgrading a bit more challenging.   After copying the new nar in to custom nar lib, you now have both 1.9 and 1.10 versions of the NiFi components.  Let's say later you upgrade to 1.11 when it becomes available for example.  NIFi normally handles upgrading to new versions during startup (1.9 processors upgraded to 1.11), but in you case after upgrade you will have this custom lib nar 1.10 and 1.11 that cam with upgrade.  Any 1.9 parquet components from your flow.xml.gz will become ghost processors on the canvas because NiFi does not have a version 1.9 and there are two options (1.10 and 1.11) so it picks neither.  You would need to either drop ghost processors and add the 1.10 or 1.11 version in its place or manually edit the flow.xml.gz to change version number manually to desired available version. Hope this helps, Matt ... View more

@Former Member  Since you are asking a new question unrelated to the question asked in the original subject, I kindly ask that you start a new question.  Would be happy to help.  Asking multiple questions in one thread makes a thread harder to follow for other users of this community forum. If you feel this question subject has been answered, please accept a solution provided to close out this thread. Thank you, Matt ... View more

@Former Member    Make sure you have configured "nifi.registry.security.needClientAuth=false". When not set it defaults to true. NeedClientAuth=true tells NiFi that in the TLS handshake it will "require" client to present a client side certificate.  If one is not presented, the connection will just close and NiFi-Registry will never try any other authentication method. This property must be set to false in order for NiFi-Registry to support any authentication method other than TLS. Hope this gets you going, Matt ... View more