@cotopaul Please go through my latest response before concluding its a hardware or setup issue. FYI, Nifi is working fine for more than a week for me since I removed the ExecuteScript Processor. That's the only change I did and I replicated the issue several times before posting here. Nifi has restarted several times since then without any issues.  could you please care to explain what sort of hardware issue it could be that it affects only ExecuteScript processor running python code?      ... View more

When you write a website with some links to other pages and maybe a form or two, you've already done real REST. The client (i.e. a web browser) presents the current resource to a user, automatically discovers related resources and allows the user to create/edit their own resources. Why people don't apply the same principles to the APIs they write is baffling. ... View more

@orodriguesrenan  Have you resolved your issue? If so please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.            ... View more

Thank you for replying.  I have tried so many different ports and I am even trying external zookeeper.  None of my nifi's can connect to any port I provide them.  It's almost like something is wrong with the code.  I have installed ZK on one of my actual nifi servers and that starts up immediately on port 2181.  That's what is leading me to think it's something in the code.  The other odd thing I keep seeing is, apache.zookeeper.ClientCnxnSocketNetty future isn't success. ... View more

Thank you Matt, I see its set to None. ... View more

i aslo face that problem can you provid code exmaple of the solution? ... View more

@anony  You can not use NiFi Expression Language (NEL) in component property names. NEL can only be used in component property values and even then, only when the component property supports Expression language. With ExtractText, any dynamic properties added will create a new FlowFile Attribute on the outbound FlowFile with an attribute name matching the property name "${reasonId}" and the attribute set the the capture group string extracted from the source FlowFiles content. Without understanding yoru complete use case, it is difficult to offer alternative possible solutions. Why is it important to set a FlowFile property name to a reasonID?  FlowFile attribute property names only mean something to NiFi.  So if you were able to create dynamic property names, then how would you programmatically use them later in your dataflow as FlowFiles will have a variety of Attribute property names? 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

The file can be found within your NiFi logs folder, where you have your other logs as well. ... View more

will do ... View more