Thanks for the revert mate. Much Appreciated.  ... View more

Hi , Thanks for the revert . I just did the same last night by taking up the NAR file from the previous Nifi version and placing it in the lib directory of the current Nifi version . I then went for the restart and then could see the processors.    However , this I believe this  isn't right and every new version should be backward compatible . Yes , there can be a new flavor of a processor i.e. a few more properties here and there but not having the processor at all in the new release is actually not acceptable as it can break your existing flows . It has caused us a lot of headache as our process runs in real time . Because of this there was an outage of almost a day as it took us some time to figure out the cause and then come up with a solution .    Is there a tech support where this can be put up so that subsequent releases should have backward compatibility .  ... View more

hi , I just want to access the following link provided in the responses above https://community.hortonworks.com/content/supportkb/167107/unable-to-perform-http-connections-throug...)   I tried clicking on the link above however , I didnt get any result . The page was blank . Can someone provide me the correct link here so that I can get to know how to configure the proxy in Nifi config.    ... View more

Hi Guys, I have stumbled on the same issue however I am not sure where to add the proxy in the nifi config. I also tried to click on the link suggested however couldnt get anything there. Can someone please let me know where / how to add the proxy on the nifi server so that we can then connect to snowflake. Its a big show stopper for us in our project . Really need some help here !!!    Many thanks in Advance  ... View more

Can someone please point to me how and where to add the proxy in the nifi.properties file so that I can get Nifi connected to Snowflake.  ... View more

Thanks Matt . We edited the flow.xml file and removed the reference to 1.4 Update Attribute bundle from it and used the edited flow file to start Nifi and the issue got fixed. No more ghost Update Attribute Processors. Thanks alot for all your help and detailed explanation on this, ... View more

Thanks Matt. I had a look at the flow.xml file and could see some multiple bundled up versions of the update attribute processor . There was no mention of the custom processor though however we had multiple versions like 1.4 and 1.8. Is there a possibility that we could tweak the flow.xml file and remove these old instances and get the flow.xml uploaded ? ... View more

HI Matt , Thanks for your answer. I am attaching the screen shot below . You can see how just the " Update Attribute" seems to have those dashed lines and is in "invalid" state. I doubt think our developers made any custom change to the update attribute processor. Let me know what you think about this meanwhile I have looked at the app.log and can see this error You were bang on when you said about the 'Ghost' Implementation. What do you think should be the next steps -bash-4.2$ cat nifi-app-*.log |grep "Unable to find bundle for coordinate" Caused by: java.lang.IllegalStateException: Unable to find bundle for coordinate org.apache.nifi:nifi-update-attribute-nar:1.8.0 ERROR [main] o.a.nifi.controller.ExtensionBuilder Could not create Processor of type org.apache.nifi.processors.attributes.UpdateAttribute for ID 629d355f-0167-1000-ffff-ffffbc497b67; creating "Ghost" implementation ... View more

Hi Matt , for the existing flow , the "update attribute" processor was in an inconfigurable state i.e it had this dotted line all over it and when I clicked on it it wasnt showing anything. This has happened for all the "update attribute" processors in our flow. For now , we have had to delete this processor and add a new one and add configur it. We also realize that the new "update attribute" processor has an extra feature with version 1.9 which wasnt available in 1.8. However this should be taken care of automatically with an upgrade. ... View more