Deepak, As a general rule you can't mix and match versions of a NAR due to possible changes in the way they're loaded, packaged, etc. If you're using NiFi 1.14.0 I recommend using the 1.14.0 version of that NAR [1]. If one "just works" in a different version that's more about serendipity than support :)
Regards, Matt [1] https://repository.apache.org/content/repositories/releases/org/apache/nifi/nifi-splunk-nar/1.14.0/nifi-splunk-nar-1.14.0.nar On Mon, Feb 28, 2022 at 12:26 PM Chirthani, Deepak Reddy < c-deepakreddy.chirth...@charter.com> wrote: > Hello, > > We are currently using GetSplunk processor to pull data from Splunk > Enterprise on a scheduled basis in our Nifi β 1.12.1 instance. We have > observed that new properties added to the GetSplunk processor in the latest > version of Nifi 1.15.3 and we would like to bring that processor to our > current instance of Nifi to meet our requirements. > > For accomplishing this, we brought the nifi-splunk-nar-1.15.3.nar file and > tested that by uploaded it to the lib folder of a separate > Nifi-1.14.0(local instance) and restarted it. Nifi β 1.14.0 was unable to > launch however it was able to launch if I removed that particular nar file. > > Any suggestions why this is happening? In the past we were able to bring > processors from lower versions of Nifi successfully but not higher versions. > > > > Thanks > > > > *[image: image005]* > > *Deepak Reddy* | Data Engineer > βIT Centers of Excellence > 13736 Riverport Dr., Maryland Heights, MO 63043 > > > The contents of this e-mail message and > any attachments are intended solely for the > addressee(s) and may contain confidential > and/or legally privileged information. If you > are not the intended recipient of this message > or if this message has been addressed to you > in error, please immediately alert the sender > by reply e-mail and then delete this message > and any attachments. If you are not the > intended recipient, you are notified that > any use, dissemination, distribution, copying, > or storage of this message or any attachment > is strictly prohibited. >
