Follow up detail.. I have no problem doing a git push from the command line. This tells me that the failure is strictly within the nifi-registry. [root@sensis-90076 eids-registry]# pwd /var/lib/nifiregistry/git/eids-registry [root@sensis-90076 eids-registry]# ls FAA_Terminal_Procedures_Publications hi [root@sensis-90076 eids-registry]# git push warning: push.default is unset; its implicit value is changing in Git 2.0 from 'matching' to 'simple'. To squelch this message and maintain the current behavior after the default changes, use: git config --global push.default matching To squelch this message and adopt the new behavior now, use: git config --global push.default simple See 'git help config' and search for 'push.default' for further information. (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode 'current' instead of 'simple' if you sometimes use older versions of Git) git@mali.corp.sensis.com's password: Counting objects: 34, done. Delta compression using up to 8 threads. Compressing objects: 100% (30/30), done. Writing objects: 100% (30/30), 3.18 KiB | 0 bytes/s, done. Total 30 (delta 12), reused 0 (delta 0) To git@mali.corp.sensis.com:eids-registry.git 35c4861..72fd26c master -> master [root@sensis-90076 eids-registry]# ... View more

Ty @Bryan Bende. That is sensible answer.. the follow-up comment also makes sense. I do think that even with the GetHTTP processor.. just knowing when the process has begun is useful.. indeed i'd think thats useful detail from any processor. I'd think that a DEBUG bulletin at the right level.. could provide that for any processor. Perhaps its already there and I just missed it. ... View more

Thank you @Timothy Spann. That is indeed the right way to go. Additionally, my initial look at the registry seems to suggest that it contains support for versioning at the process group level. For some reason I thought I saw a registry JIRA issue that suggested it did not support that. I started to try it out yesterday. If we decide to use NIFI, we will definitely do so through the official HDF release. Right now I am in an evaluation mode to see if it can suit the needs of a mission critical system. ... View more

Thank you very much. I'll try these this week. Great detail in your response.. appreciated. ... View more

How can we pass dynamic attribute value in a loop condition. Something like ${i:lt({$.count})},as i am getting error while putting up this condition in RouteToAttribute processor. How can we achive this.Please help here. , How can we pass dynamic variable in a loop,for an instance i want to create a condition in RouteToAttribute like ${i:lt({$.count})}. But as from the Nifi expression language doc we can only pass static value as a paremeter in lt(). How can it be achieved.Please help here. ... View more

Jonathan. This looks like what I need. Is it your assumption that this will work with a private GIT server? GITHUB may not be an option for our organization.. Based on your information, I'm assuming that I'll be able to setup a GIT server that will work with NIFI-REGISTRY. I'll try this out. ... View more

Thank you. I like your answer very much. I do think the referenced example was not focused on a zip of zip (just a simple zip of a directory tree).. Yet I think your answer is proper.. The "path" attribute does the job. I'll try this.. and thanks. ... View more

@Matt Clarke Hi Matt. One question I'd like to get your perspective on.. Assuming that I manage independent flows within a single NIFI cluster, is it your experience that I can use the NIFI registry to properly version and manage the independent flows that are processed within that cluster? The inability to manage each independent flow as a versioned flow, could potentially drive me to using multiple NIFI clusters (and to assign each cluster one or several flows). I'm concerned about the overall complexity of the processing that is assigned to a single cluster. ... View more

to me.. this is not the simple approach.. its very limiting and its no simpler than using the jolttransformation suggested above. ... View more