Re: Expected mergerecord performance

[Richard Beare]

Any thoughts on this? Are there some extra steps required when creating an
avro file from a user defined schema?

On Thu, Dec 8, 2022 at 2:56 PM Richard Beare 
wrote:

> Here's another result that I think suggests there's something wrong with
> the avro files created by the groovy script, although I can't see what the
> problem might be.
>
> The test is as follows. Output of the groovy script creating avro files is
> passed to convertrecord, configured with an avro reader and json writer.
> This is slow. The json output is then converted back to avro with another
> convertrecord processor, configured with a jsontreereader and an avro
> writer - this is fast, instantly emptying the queue. The result of that is
> fed into the previously problematic merge processor which works exactly as
> expected, producing flowfiles with 100 records each.
>
> The difference I can see between the two flow files is the way in which
> the schema is specified. Perhaps some extras are required in the groovy
> file to set that up?
>
> The slow one has:
>
> {"type":"record","name":"document", "fields":[{
>
> The fast one
>
> {"type":"record","name":"nifiRecord","namespace":"org.apache.nifi","fields":
>
>
> Initial characters are also slightly different.
> Slow one:
>
> 000   O   b   j 001 002 026   a   v   r   o   .   s   c   h   e   m
> 020   a 346  \n   {   "   t   y   p   e   "   :   "   r   e   c   o
>
> Fast one
>
> 000   O   b   j 001 004 026   a   v   r   o   .   s   c   h   e   m
> 020   a 362  \b   {   "   t   y   p   e   "   :   "   r   e   c   o
>
>
> The groovy script is
> CogStack-NiFi/parse-tika-result-json-to-avro.groovy at master ·
> CogStack/CogStack-NiFi · GitHub
> 
>
> The schema is
> CogStack-NiFi/document.avsc at master · CogStack/CogStack-NiFi · GitHub
> 
>
>
> On Thu, Dec 8, 2022 at 1:59 PM Richard Beare 
> wrote:
>
>> I'm diving into the convertrecord tests a bit deeper on the production
>> server.
>>
>> The first test case - 259 documents, total of 1M when in avro format in
>> the input queue to the convert record processor. These avro files were not
>> created by the groovy script - they start life as a database query and the
>> text field is in one of the columns. The convertrecord processor runs very
>> quickly - click start, press refresh and it is done. The avro ends up like
>> this:
>>
>> [ {
>>   "sampleid" : 1075,
>>   "typeid" : 98,
>>   "dct" : "2020-01-25T21:40:25.515Z",
>>   "filename" : "__tmp/txt/mtsamples-type-98-sample-1075.txt",
>>   "document" : "Text removed",
>>   "docid" : "9"
>> } ]
>>
>> In the second test, where the text fields are extracted from pdf tika
>> before avro files are created by the groovy script (from the tika json
>> output), the total queue size for the 259 documents is larger - 1.77MB, and
>> the performance is very different - press start, click refresh and only two
>> flowfiles are processed.
>>
>> [ {
>>   "doc_id" : "70",
>>   "doc_text" : "text removed",
>>   "processing_timestamp" : "2022-12-07T23:09:52.354Z",
>>   "metadata_x_ocr_applied" : true,
>>   "metadata_x_parsed_by" : "org.apache.tika.parser.pdf.PDFParser",
>>   "metadata_content_type" : "application/pdf",
>>   "metadata_page_count" : 1,
>>   "metadata_creation_date" : null,
>>   "metadata_last_modified" : null
>> } ]
>>
>> I've noticed that the second one has a content.type attribute of
>> 'application/json' which doesn't seem right and doesn't match the fast
>> case. I'll see what happens if I change that.
>>
>> On Thu, Dec 8, 2022 at 9:39 AM Richard Beare 
>> wrote:
>>
>>> Hi All,
>>> Some progress on debugging options. I've found a flow that exhibits the
>>> problem using synthetic data. However the results are host dependent. On my
>>> laptop a "run-once" click of merge record gives me two flowfiles of 100
>>> records, while the same flow on the production server produces several much
>>> smaller flowfiles. This makes me think that something funny is happening
>>> with my storage setup that I'll need to chase.
>>>
>>> I had tested the convertrecord option (simply avroreader->avrowriter)
>>> and it did seem slow, but I'll investigate this further as it may be
>>> related to my storage issue.
>>>
>>>
>>>
>>> On Thu, Dec 8, 2022 at 1:23 AM Mark Payne  wrote:
>>>
 > Is there something about this structure that is likely to be causing
 the problem? Could there be other issues with the avro generated by the
 script?

 I don’t think the structure should matter. And as long as the avro
 produced is proper Avro, I don’t think it should matter. Unless perhaps
 there’s some issue with the Avro library itself that’s causing it to take a
 really long time to parse the Avro or something? I’d be curious - if you
 take the output of your script and then you run it 

Re: authorizers.xml for simple single user configuration?

[Bryan Bende]

If you want no authN and no authZ then you can have empty
authorizers.xml and empty login-identity-providers.xml, just make sure
nifi.properties does not reference an authorizer id or identity
provider id.

Keeping in mind that if you make it unsecure, hopefully your nifi
instance is not accessible from anywhere other than localhost.

On Tue, Dec 13, 2022 at 2:04 PM James McMahon  wrote:
>
> Thank you Bryan. I do have that declared in login-identity-providers.xml:
> [ec2-user@ip-172-31-73-197 conf]$ more login-identity-providers.xml
> 
> 
> 
>   
> 
> org.apache.nifi.authentication.single.user.SingleUserLoginIdentityProvider
> single-user-provider
>   
> 
>
> I am not sure I can answer your question. I thought authorizers.xml, and the 
> other xml conf files were required. For my simplified use case, what is the 
> bare minimum configuration including in the authorizers.xml and 
> login-identity-providers.xml?
>
> I realize my use case is not a good long-term objective. But I want to get a 
> nifi instance running in a minimalist form, and then after I do that tackle 
> authorization, https, etc.
>
> On Tue, Dec 13, 2022 at 1:48 PM Bryan Bende  wrote:
>>
>> The SingleUserAuthorizer requires using the
>> SingleUserLoginIdentityProvider, do you have that declared in
>> login-identity-providers.xml?
>>
>> Also if you are trying to remove authentication/authorization and run
>> over http, then why declare the SingleUserAuthorizer at all?
>>
>> On Tue, Dec 13, 2022 at 1:43 PM James McMahon  wrote:
>> >
>> > Hello. I am having difficulty getting nifi to start for a simple single 
>> > node configuration without user authentication. My goal is to get a nifi 
>> > instance running over http. I understood that there would be no user 
>> > authentication in such a case. Why then is my nifi instance failing to 
>> > start with these errors thrown for authorizers.xml  (example of the errors 
>> > at bottom)?
>> >
>> > I have no FileUserGroupProvider or LdapUserGroupProvider to access for 
>> > user account information. I establish a user named nifi and group named 
>> > nifi at the time I run my playbook.
>> >
>> > Currently I have only this in my authorizers.xml file.
>> > 
>> > 
>> > 
>> >   
>> > single-user-authorizer
>> > 
>> > org.apache.nifi.authorization.single.user.SingleUserAuthorizer
>> >   
>> > 
>> > I run my ansible playbook as user ec2-user, and the ansible role 
>> > establishes a user nifi. How must authorizers.xml be configured for such a 
>> > single-node nifi configuration?
>> >
>> > When I attempt to start nifi I get a series of errors like these in 
>> > nifi-app.log. I suspect my authorizers.xml is missing info.
>> >
>> > Caused by: 
>> > org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
>> > creating bean with name 
>> > 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration':
>> >  Unsatisfied dependency expressed through method 'setObjectPostProcessor' 
>> > parameter 0; nested exception is 
>> > org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
>> > creating
>> >  bean with name 
>> > 'org.apache.nifi.web.security.configuration.AuthenticationSecurityConfiguration':
>> >  Unsatisfied dependency expressed through constructor parameter 2; nested 
>> > exception is org.springframe
>> > work.beans.factory.BeanCreationException: Error creating bean with name 
>> > 'authorizer': FactoryBean threw exception on object creation; nested 
>> > exception is java.lang.Exception: Unable to load the authorizer 
>> > configuration file at: 
>> > /opt/nifi/releases/nifi-1.16.3/./conf/authorizers.xml

RE: [EXTERNAL] Re: Disabling flows - nifi registry

[Chirthani, Deepak Reddy]

The version of Nifi where I had UI performance issues was 1.11.4
The current version of our nifi instance is 1.15.3

One other disadvantage of having Process Groups with Stopped components is that 
when a dataflow manager or a developer inadvertently right click and select 
“start” on the root canvas page, that will start all the components in the 
child process groups.

Thanks
Deepak

[image005]
Deepak Reddy | Data Engineer
​IT Centers of Excellence
13736 Riverport Dr., Maryland Heights, MO 63043

From: Kevin Doran 
Sent: Tuesday, December 13, 2022 10:26 AM
To: users@nifi.apache.org
Subject: RE: [EXTERNAL] Re: Disabling flows - nifi registry

CAUTION: The e-mail below is from an external source. Please exercise caution 
before opening attachments, clicking links, or following guidance.
Thanks for sharing Deepak. That's interesting. I think we may look into a way 
of disabling components that doesn't impact version control, or else fix 
performance issues such that disabling is not necessary.

Just out of curiosity, what version of NiFi are you on? The reason I ask is 
that I know there have been some UI performance improvements made in recent 
versions of NiFi, so I'm wondering if some of this might already have been 
addressed...

Thanks,
Kevin

On Dec 13, 2022 at 09:52:47, "Chirthani, Deepak Reddy" 
mailto:c-deepakreddy.chirth...@charter.com>>
 wrote:

Hi Kevin,

Thank you for your quick response. The only reason why I prefer processors to 
be disabled is to improve the NiFi UI performance by simply disabling stopped 
processors which I am not using.

https://community.cloudera.com/t5/Support-Questions/Nifi-UI-Working-very-Slow-How-to-increase-performance-of-a/td-p/214550

I had issues with Nifi UI performance in the past where the refresh wheel keeps 
on spinning like for 10 seconds and disabling stopped processors really helped 
me.

Thanks
Deepak


[image005]
Deepak Reddy | Data Engineer
​IT Centers of Excellence
13736 Riverport Dr., Maryland Heights, MO 63043

From: Kevin Doran mailto:kdo...@apache.org>>
Sent: Friday, December 9, 2022 9:33 AM
To: users@nifi.apache.org
Subject: [EXTERNAL] Re: Disabling flows - nifi registry

CAUTION: The e-mail below is from an external source. Please exercise caution 
before opening attachments, clicking links, or following guidance.
Hi Deepak,

So far, we have been honoring the following policy for what constitutes a 
change in version control:


  1.  stopped/started does not count as a "local change"
  2.  enabled/disabled does count as a change, and that state is captured in 
the flow snapshot json version saved to registry.

One reason for this is that some users want to setup CI/CD to deploy from 
Registry and automatically start a flow in the target NiFi. If there are 
components they don't want to start, the disabled state gives them a way to 
capture that configuration in the flow.

Is there a reason you prefer disable over stop in your lower environment? I 
leave flows stopped in dev environments all the time and have never run into an 
issue, but of course, everyone's workflow and use case is slightly different, 
so I'm interested in hearing your perspective on this to see if we need to 
consider something more flexible.

Cheers,
Kevin

On Dec 9, 2022 at 10:26:27, "Chirthani, Deepak Reddy" 
mailto:c-deepakreddy.chirth...@charter.com>>
 wrote:
Hey guys,

So, once I fully develop and parameterize my nifi dataflow, let’s say in dev 
environment, I enable the version control, import the flow in higher 
environment and turn on the dataflow. In most of the cases both the flows in 
lower and higher environments will be running. Let says dev nifi connects to 
dev gcp pubsub and prod nifi connects to prod gcp pubsub. However, in some 
cases, we do want to stop and disable the flow in lower env. When I do that the 
registry is identifying that local changes are made to the flow which is 
nothing but all the components are disabled. I don’t want to keep the 
processors in stopped state on the canvas(registry do not identify for 
stopping) but want to disable them. Any workaround for registry not to identify 
local changes when flow is disabled?

Thanks
Deepak

[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.
The contents of this e-mail message and
any attachments are intended solely for the
addressee(s) and may contain 

Re: authorizers.xml for simple single user configuration?

[James McMahon]

Thank you Bryan. I do have that declared in login-identity-providers.xml:
[ec2-user@ip-172-31-73-197 conf]$ more login-identity-providers.xml



  

org.apache.nifi.authentication.single.user.SingleUserLoginIdentityProvider
single-user-provider
  


I am not sure I can answer your question. I thought authorizers.xml, and
the other xml conf files were required. For my simplified use case, what is
the bare minimum configuration including in the authorizers.xml and
login-identity-providers.xml?

I realize my use case is not a good long-term objective. But I want to get
a nifi instance running in a minimalist form, and then after I do that
tackle authorization, https, etc.

On Tue, Dec 13, 2022 at 1:48 PM Bryan Bende  wrote:

> The SingleUserAuthorizer requires using the
> SingleUserLoginIdentityProvider, do you have that declared in
> login-identity-providers.xml?
>
> Also if you are trying to remove authentication/authorization and run
> over http, then why declare the SingleUserAuthorizer at all?
>
> On Tue, Dec 13, 2022 at 1:43 PM James McMahon 
> wrote:
> >
> > Hello. I am having difficulty getting nifi to start for a simple single
> node configuration without user authentication. My goal is to get a nifi
> instance running over http. I understood that there would be no user
> authentication in such a case. Why then is my nifi instance failing to
> start with these errors thrown for authorizers.xml  (example of the errors
> at bottom)?
> >
> > I have no FileUserGroupProvider or LdapUserGroupProvider to access for
> user account information. I establish a user named nifi and group named
> nifi at the time I run my playbook.
> >
> > Currently I have only this in my authorizers.xml file.
> > 
> > 
> > 
> >   
> > single-user-authorizer
> >
>  org.apache.nifi.authorization.single.user.SingleUserAuthorizer
> >   
> > 
> > I run my ansible playbook as user ec2-user, and the ansible role
> establishes a user nifi. How must authorizers.xml be configured for such a
> single-node nifi configuration?
> >
> > When I attempt to start nifi I get a series of errors like these in
> nifi-app.log. I suspect my authorizers.xml is missing info.
> >
> > Caused by:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration':
> Unsatisfied dependency expressed through method 'setObjectPostProcessor'
> parameter 0; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating
> >  bean with name
> 'org.apache.nifi.web.security.configuration.AuthenticationSecurityConfiguration':
> Unsatisfied dependency expressed through constructor parameter 2; nested
> exception is org.springframe
> > work.beans.factory.BeanCreationException: Error creating bean with name
> 'authorizer': FactoryBean threw exception on object creation; nested
> exception is java.lang.Exception: Unable to load the authorizer
> configuration file at: /opt/nifi/releases/nifi-1.16.3/./conf/authorizers.xml
>

Re: authorizers.xml for simple single user configuration?

[Bryan Bende]

The SingleUserAuthorizer requires using the
SingleUserLoginIdentityProvider, do you have that declared in
login-identity-providers.xml?

Also if you are trying to remove authentication/authorization and run
over http, then why declare the SingleUserAuthorizer at all?

On Tue, Dec 13, 2022 at 1:43 PM James McMahon  wrote:
>
> Hello. I am having difficulty getting nifi to start for a simple single node 
> configuration without user authentication. My goal is to get a nifi instance 
> running over http. I understood that there would be no user authentication in 
> such a case. Why then is my nifi instance failing to start with these errors 
> thrown for authorizers.xml  (example of the errors at bottom)?
>
> I have no FileUserGroupProvider or LdapUserGroupProvider to access for user 
> account information. I establish a user named nifi and group named nifi at 
> the time I run my playbook.
>
> Currently I have only this in my authorizers.xml file.
> 
> 
> 
>   
> single-user-authorizer
> 
> org.apache.nifi.authorization.single.user.SingleUserAuthorizer
>   
> 
> I run my ansible playbook as user ec2-user, and the ansible role establishes 
> a user nifi. How must authorizers.xml be configured for such a single-node 
> nifi configuration?
>
> When I attempt to start nifi I get a series of errors like these in 
> nifi-app.log. I suspect my authorizers.xml is missing info.
>
> Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: 
> Error creating bean with name 
> 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration':
>  Unsatisfied dependency expressed through method 'setObjectPostProcessor' 
> parameter 0; nested exception is 
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating
>  bean with name 
> 'org.apache.nifi.web.security.configuration.AuthenticationSecurityConfiguration':
>  Unsatisfied dependency expressed through constructor parameter 2; nested 
> exception is org.springframe
> work.beans.factory.BeanCreationException: Error creating bean with name 
> 'authorizer': FactoryBean threw exception on object creation; nested 
> exception is java.lang.Exception: Unable to load the authorizer configuration 
> file at: /opt/nifi/releases/nifi-1.16.3/./conf/authorizers.xml

authorizers.xml for simple single user configuration?

[James McMahon]

Hello. I am having difficulty getting nifi to start for a simple single
node configuration without user authentication. My goal is to get a nifi
instance running over http. I understood that there would be no user
authentication in such a case. Why then is my nifi instance failing to
start with these errors thrown for authorizers.xml  (example of the errors
at bottom)?

I have no FileUserGroupProvider or LdapUserGroupProvider to access for user
account information. I establish a user named nifi and group named nifi at
the time I run my playbook.

Currently I have only this in my authorizers.xml file.



  
single-user-authorizer

org.apache.nifi.authorization.single.user.SingleUserAuthorizer
  

I run my ansible playbook as user ec2-user, and the ansible role
establishes a user nifi. How must authorizers.xml be configured for such a
single-node nifi configuration?

When I attempt to start nifi I get a series of errors like these in
nifi-app.log. I suspect my authorizers.xml is missing info.

Caused by:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration':
Unsatisfied dependency expressed through method 'setObjectPostProcessor'
parameter 0; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating
 bean with name
'org.apache.nifi.web.security.configuration.AuthenticationSecurityConfiguration':
Unsatisfied dependency expressed through constructor parameter 2; nested
exception is org.springframe
work.beans.factory.BeanCreationException: Error creating bean with name
'authorizer': FactoryBean threw exception on object creation; nested
exception is java.lang.Exception: Unable to load the authorizer
configuration file at: /opt/nifi/releases/nifi-1.16.3/./conf/authorizers.xml

RE: [EXTERNAL] Re: Disabling flows - nifi registry

[Kevin Doran]

Thanks for sharing Deepak. That's interesting. I think we may look into a
way of disabling components that doesn't impact version control, or else
fix performance issues such that disabling is not necessary.

Just out of curiosity, what version of NiFi are you on? The reason I ask is
that I know there have been some UI performance improvements made in recent
versions of NiFi, so I'm wondering if some of this might already have been
addressed...

Thanks,
Kevin

On Dec 13, 2022 at 09:52:47, "Chirthani, Deepak Reddy" <
c-deepakreddy.chirth...@charter.com> wrote:

> Hi Kevin,
>
> Thank you for your quick response. The only reason why I prefer processors
> to be disabled is to improve the NiFi UI performance by simply disabling
> stopped processors which I am not using.
>
>
> https://community.cloudera.com/t5/Support-Questions/Nifi-UI-Working-very-Slow-How-to-increase-performance-of-a/td-p/214550
>
> I had issues with Nifi UI performance in the past where the refresh wheel
> keeps on spinning like for 10 seconds and disabling stopped processors
> really helped me.
>
> Thanks
> Deepak
>
>
>
>
>
> *[image: image005]*
>
> *Deepak Reddy* | Data Engineer
> ​IT Centers of Excellence
> 13736 Riverport Dr., Maryland Heights, MO 63043
>
>
>
> *From:* Kevin Doran 
> *Sent:* Friday, December 9, 2022 9:33 AM
> *To:* users@nifi.apache.org
> *Subject:* [EXTERNAL] Re: Disabling flows - nifi registry
>
>
>
> *CAUTION:* The e-mail below is from an external source. Please exercise
> caution before opening attachments, clicking links, or following guidance.
>
> Hi Deepak,
>
>
>
> So far, we have been honoring the following policy for what constitutes a
> change in version control:
>
>
>
>- stopped/started does not count as a "local change"
>- enabled/disabled does count as a change, and that state is captured
>in the flow snapshot json version saved to registry.
>
>
>
> One reason for this is that some users want to setup CI/CD to deploy from
> Registry and automatically start a flow in the target NiFi. If there are
> components they don't want to start, the disabled state gives them a way to
> capture that configuration in the flow.
>
>
>
> Is there a reason you prefer disable over stop in your lower environment?
> I leave flows stopped in dev environments all the time and have never run
> into an issue, but of course, everyone's workflow and use case is slightly
> different, so I'm interested in hearing your perspective on this to see if
> we need to consider something more flexible.
>
>
>
> Cheers,
>
> Kevin
>
>
>
> On Dec 9, 2022 at 10:26:27, "Chirthani, Deepak Reddy" <
> c-deepakreddy.chirth...@charter.com> wrote:
>
> Hey guys,
>
> So, once I fully develop and parameterize my nifi dataflow, let’s say in
> dev environment, I enable the version control, import the flow in higher
> environment and turn on the dataflow. In most of the cases both the flows
> in lower and higher environments will be running. Let says dev nifi
> connects to dev gcp pubsub and prod nifi connects to prod gcp pubsub.
> However, in some cases, we do want to stop and disable the flow in lower
> env. When I do that the registry is identifying that local changes are made
> to the flow which is nothing but all the components are disabled. I don’t
> want to keep the processors in stopped state on the canvas(registry do not
> identify for stopping) but want to disable them. Any workaround for
> registry not to identify local changes when flow is disabled?
>
>
>
> Thanks
>
> Deepak
>
>
>
> *[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.
>
> 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.
>

Re: Error on nifi start

[Kevin Doran]

 Yep, was just about to say the same. NiFi 1.14.0 does not run on Java 17,
but recent versions of NiFi do. So either move to a NiFi >= 1.16.3 which
does support on Java 17, or else downgrade Java to 8 or 11.

On Dec 13, 2022 at 10:47:00, Joe Witt  wrote:

> We support 8, 11, and 17 now.  As far as NiFi 1.14 which James mentioned
> he was using we didn't support it then.  Support started in NiFi 1.16.
>
> Thanks
>
> On Tue, Dec 13, 2022 at 8:43 AM James Srinivasan <
> james.sriniva...@gmail.com> wrote:
>
>> I think nifi currently supports java 8 or 11, not 17:
>>
>>
>> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#system_requirements
>>
>> On Tue, 13 Dec 2022, 12:45 James McMahon,  wrote:
>>
>>> I am using an Ansible role from Ansible GALAXY that has been tested and
>>> validated up through Apache NiFi v1.14.0. I download and install 1.14.0.bin
>>> from the Apache NiFi archives fir this reason.
>>>
>>> I am using ansible to install on and AWS EC2 instance. My java version
>>> on this instance is:
>>>
>>> openjdk 17.0.5 2022-10-18 LTS
>>>
>>> OpenJDK Runtime Environment Corretto-17.0.5.8.1
>>>
>>> The install goes well. But when nifi attempts to start, it fails with
>>> the following error message. Is this error indicating a compatibility issue
>>> with the java installation on AWS? How should I proceed to get nifi to
>>> start?
>>>
>>> 2022-12-13 02:50:39,316 ERROR [main] org.apache.nifi.NiFi Failure to
>>> launch NiFi due to org.xerial.snappy.SnappyError:
>>> [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to make p
>>>
>>> rotected final java.lang.Class
>>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
>>> throws java.lang.ClassFormatError acce
>>>
>>> ssible: module java.base does not "opens java.lang" to unnamed module
>>> @31b289da
>>>
>>> org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to
>>> make protected final java.lang.Class
>>> java.lang.ClassLoader.defineClass(java.lang.String,byte[]
>>>
>>> ,int,int,java.security.ProtectionDomain) throws
>>> java.lang.ClassFormatError accessible: module java.base does not "opens
>>> java.lang" to unnamed module @31b289da
>>>
>>> at
>>> org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:297)
>>>
>>> at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227)
>>>
>>> at org.xerial.snappy.Snappy.(Snappy.java:48)
>>>
>>> at
>>> org.apache.nifi.processors.hive.PutHiveStreaming.(PutHiveStreaming.java:158)
>>>
>>> at java.base/java.lang.Class.forName0(Native Method)
>>>
>>> at java.base/java.lang.Class.forName(Class.java:467)
>>>
>>> at
>>> org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328)
>>>
>>> at
>>> org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100)
>>>
>>> at
>>> org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65)
>>>
>>> at
>>> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126)
>>>
>>> at org.apache.nifi.NiFi.(NiFi.java:159)
>>>
>>> at org.apache.nifi.NiFi.(NiFi.java:71)
>>>
>>> at org.apache.nifi.NiFi.main(NiFi.java:303)
>>>
>>>
>>>
>>>
>>>
>>>
>>>

Re: Error on nifi start

[Joe Witt]

We support 8, 11, and 17 now.  As far as NiFi 1.14 which James mentioned he
was using we didn't support it then.  Support started in NiFi 1.16.

Thanks

On Tue, Dec 13, 2022 at 8:43 AM James Srinivasan 
wrote:

> I think nifi currently supports java 8 or 11, not 17:
>
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#system_requirements
>
> On Tue, 13 Dec 2022, 12:45 James McMahon,  wrote:
>
>> I am using an Ansible role from Ansible GALAXY that has been tested and
>> validated up through Apache NiFi v1.14.0. I download and install 1.14.0.bin
>> from the Apache NiFi archives fir this reason.
>>
>> I am using ansible to install on and AWS EC2 instance. My java version on
>> this instance is:
>>
>> openjdk 17.0.5 2022-10-18 LTS
>>
>> OpenJDK Runtime Environment Corretto-17.0.5.8.1
>>
>> The install goes well. But when nifi attempts to start, it fails with the
>> following error message. Is this error indicating a compatibility issue
>> with the java installation on AWS? How should I proceed to get nifi to
>> start?
>>
>> 2022-12-13 02:50:39,316 ERROR [main] org.apache.nifi.NiFi Failure to
>> launch NiFi due to org.xerial.snappy.SnappyError:
>> [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to make p
>>
>> rotected final java.lang.Class
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
>> throws java.lang.ClassFormatError acce
>>
>> ssible: module java.base does not "opens java.lang" to unnamed module
>> @31b289da
>>
>> org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to
>> make protected final java.lang.Class
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[]
>>
>> ,int,int,java.security.ProtectionDomain) throws
>> java.lang.ClassFormatError accessible: module java.base does not "opens
>> java.lang" to unnamed module @31b289da
>>
>> at
>> org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:297)
>>
>> at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227)
>>
>> at org.xerial.snappy.Snappy.(Snappy.java:48)
>>
>> at
>> org.apache.nifi.processors.hive.PutHiveStreaming.(PutHiveStreaming.java:158)
>>
>> at java.base/java.lang.Class.forName0(Native Method)
>>
>> at java.base/java.lang.Class.forName(Class.java:467)
>>
>> at
>> org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328)
>>
>> at
>> org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100)
>>
>> at
>> org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65)
>>
>> at
>> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126)
>>
>> at org.apache.nifi.NiFi.(NiFi.java:159)
>>
>> at org.apache.nifi.NiFi.(NiFi.java:71)
>>
>> at org.apache.nifi.NiFi.main(NiFi.java:303)
>>
>>
>>
>>
>>
>>
>>

Re: Error on nifi start

[James Srinivasan]

I think nifi currently supports java 8 or 11, not 17:

https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#system_requirements

On Tue, 13 Dec 2022, 12:45 James McMahon,  wrote:

> I am using an Ansible role from Ansible GALAXY that has been tested and
> validated up through Apache NiFi v1.14.0. I download and install 1.14.0.bin
> from the Apache NiFi archives fir this reason.
>
> I am using ansible to install on and AWS EC2 instance. My java version on
> this instance is:
>
> openjdk 17.0.5 2022-10-18 LTS
>
> OpenJDK Runtime Environment Corretto-17.0.5.8.1
>
> The install goes well. But when nifi attempts to start, it fails with the
> following error message. Is this error indicating a compatibility issue
> with the java installation on AWS? How should I proceed to get nifi to
> start?
>
> 2022-12-13 02:50:39,316 ERROR [main] org.apache.nifi.NiFi Failure to
> launch NiFi due to org.xerial.snappy.SnappyError:
> [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to make p
>
> rotected final java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> throws java.lang.ClassFormatError acce
>
> ssible: module java.base does not "opens java.lang" to unnamed module
> @31b289da
>
> org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to
> make protected final java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[]
>
> ,int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError
> accessible: module java.base does not "opens java.lang" to unnamed module
> @31b289da
>
> at
> org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:297)
>
> at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227)
>
> at org.xerial.snappy.Snappy.(Snappy.java:48)
>
> at
> org.apache.nifi.processors.hive.PutHiveStreaming.(PutHiveStreaming.java:158)
>
> at java.base/java.lang.Class.forName0(Native Method)
>
> at java.base/java.lang.Class.forName(Class.java:467)
>
> at
> org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328)
>
> at
> org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100)
>
> at
> org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65)
>
> at
> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126)
>
> at org.apache.nifi.NiFi.(NiFi.java:159)
>
> at org.apache.nifi.NiFi.(NiFi.java:71)
>
> at org.apache.nifi.NiFi.main(NiFi.java:303)
>
>
>
>
>
>
>

Re: Error on nifi start

[James McMahon]

I now try to set this at end of my bootstrap.conf file:
java.arg.snappy=-Dorg.xerial.snappy.tempdir=/usr/hdf/current/nifi/tmp

But this only throws another ERROR to the log that causes nifi to fail:
2022-12-13 15:09:49,284 ERROR [NiFi logging handler] org.apache.nifi.StdErr
java.lang.reflect.InaccessibleObjectException: Unable to make protected
final java.lang.Class java.lang.ClassLoader.defineC
lass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws
java.lang.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module @2326180c
2022-12-13 15:09:49,285 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
2022-12-13 15:09:49,285 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:275)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.xerial.snappy.Snappy.(Snappy.java:48)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.apache.nifi.processors.hive.PutHiveStreaming.(PutHiveStreaming.java:158)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at java.base/java.lang.Class.forName0(Native
Method)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
java.base/java.lang.Class.forName(Class.java:467)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at
org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at org.apache.nifi.NiFi.(NiFi.java:159)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at org.apache.nifi.NiFi.(NiFi.java:71)
2022-12-13 15:09:49,286 ERROR [NiFi logging handler]
org.apache.nifi.StdErr at org.apache.nifi.NiFi.main(NiFi.java:303)

Some research suggests this may be fixable by setting this as follows,
presumably to the java startup:
--illegal-access=permit
(see cglib - java.lang.ExceptionInInitializerError with Java-16 |
j.l.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module - Stack Overflow

 )

Would I set this in bootstrap.conf? How?

On Tue, Dec 13, 2022 at 7:45 AM James McMahon  wrote:

> I am using an Ansible role from Ansible GALAXY that has been tested and
> validated up through Apache NiFi v1.14.0. I download and install 1.14.0.bin
> from the Apache NiFi archives fir this reason.
>
> I am using ansible to install on and AWS EC2 instance. My java version on
> this instance is:
>
> openjdk 17.0.5 2022-10-18 LTS
>
> OpenJDK Runtime Environment Corretto-17.0.5.8.1
>
> The install goes well. But when nifi attempts to start, it fails with the
> following error message. Is this error indicating a compatibility issue
> with the java installation on AWS? How should I proceed to get nifi to
> start?
>
> 2022-12-13 02:50:39,316 ERROR [main] org.apache.nifi.NiFi Failure to
> launch NiFi due to org.xerial.snappy.SnappyError:
> [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to make p
>
> rotected final java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> throws java.lang.ClassFormatError acce
>
> ssible: module java.base does not "opens java.lang" to unnamed module
> @31b289da
>
> org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to
> make protected final java.lang.Class
> java.lang.ClassLoader.defineClass(java.lang.String,byte[]
>
> ,int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError
> 

RE: [EXTERNAL] Re: Disabling flows - nifi registry

[Chirthani, Deepak Reddy]

Hi Kevin,

Thank you for your quick response. The only reason why I prefer processors to 
be disabled is to improve the NiFi UI performance by simply disabling stopped 
processors which I am not using.

https://community.cloudera.com/t5/Support-Questions/Nifi-UI-Working-very-Slow-How-to-increase-performance-of-a/td-p/214550

I had issues with Nifi UI performance in the past where the refresh wheel keeps 
on spinning like for 10 seconds and disabling stopped processors really helped 
me.

Thanks
Deepak


[image005]
Deepak Reddy | Data Engineer
​IT Centers of Excellence
13736 Riverport Dr., Maryland Heights, MO 63043

From: Kevin Doran 
Sent: Friday, December 9, 2022 9:33 AM
To: users@nifi.apache.org
Subject: [EXTERNAL] Re: Disabling flows - nifi registry

CAUTION: The e-mail below is from an external source. Please exercise caution 
before opening attachments, clicking links, or following guidance.
Hi Deepak,

So far, we have been honoring the following policy for what constitutes a 
change in version control:


  *   stopped/started does not count as a "local change"
  *   enabled/disabled does count as a change, and that state is captured in 
the flow snapshot json version saved to registry.

One reason for this is that some users want to setup CI/CD to deploy from 
Registry and automatically start a flow in the target NiFi. If there are 
components they don't want to start, the disabled state gives them a way to 
capture that configuration in the flow.

Is there a reason you prefer disable over stop in your lower environment? I 
leave flows stopped in dev environments all the time and have never run into an 
issue, but of course, everyone's workflow and use case is slightly different, 
so I'm interested in hearing your perspective on this to see if we need to 
consider something more flexible.

Cheers,
Kevin

On Dec 9, 2022 at 10:26:27, "Chirthani, Deepak Reddy" 
mailto:c-deepakreddy.chirth...@charter.com>>
 wrote:
Hey guys,

So, once I fully develop and parameterize my nifi dataflow, let’s say in dev 
environment, I enable the version control, import the flow in higher 
environment and turn on the dataflow. In most of the cases both the flows in 
lower and higher environments will be running. Let says dev nifi connects to 
dev gcp pubsub and prod nifi connects to prod gcp pubsub. However, in some 
cases, we do want to stop and disable the flow in lower env. When I do that the 
registry is identifying that local changes are made to the flow which is 
nothing but all the components are disabled. I don’t want to keep the 
processors in stopped state on the canvas(registry do not identify for 
stopping) but want to disable them. Any workaround for registry not to identify 
local changes when flow is disabled?

Thanks
Deepak

[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.
E-MAIL CONFIDENTIALITY NOTICE: 
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.

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

[Simon Bence]

Hi Josef,

I assigned it to myself and will take a deeper look shortly. Understanding the 
reasons and fixing it might need more time and I am asking for your patience.

Best regards,
Bence

> On 2022. Dec 13., at 13:53,  
>  wrote:
> 
> Hi Bence
>  
> I mentioned yesterday another issue which we thought would be solved after 
> the upgrade steps. Sadly it happened again and after an investigation on our 
> side it seems to be fully reproducible, I’ve opened a Jira Bugticket 
> https://issues.apache.org/jira/browse/NIFI-10973 
>  with more details. It’s as 
> well related to NiFi Registry nested flows…
>  
> Thanks for taking care of it :-).
>  
> Cheers Josef
>  
>  
> From: Simon Bence mailto:simonbence@gmail.com>>
> Reply to: "users@nifi.apache.org " 
> mailto:users@nifi.apache.org>>
> Date: Monday, 12 December 2022 at 16:40
> To: "users@nifi.apache.org" 
> Subject: Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes 
> issue
>  
> Hi Josef, 
>  
> Thanks for the quick update! Meanwhile I tried to reproduce this situation 
> but based on the known facts I was not able (Note: without any version 
> change). I think it is connected to the version change indeed, but if you 
> face with this ever again, please let me know!
>  
> Regards,
> Bence
> 
> 
>> On 2022. Dec 12., at 16:33, > > > > wrote:
>>  
>> Ok quick update on this. We investigated the changes on the *.snapshot files 
>> on NiFi Registry. It seems that it’s mainly caused due to the fact that the 
>> NiFi Version changes from 1.18.0 to 1.19.1 and some other facts caused due 
>> to the upgrade. After commiting all the child PGs once the “Show Local 
>> Changes” seems to behave as expected.
>> We have seen another issue caused only on the first commit of the child PGs 
>> on v1.19.1, however I’ll not mention them as I’m guessing that this is 
>> highly related to the last commits with the older NiFi version.
>>  
>> Cheers Josef
>>  
>>  
>> From: "Zahner Josef, GSB-LR-TRW-LI" > >
>> Date: Monday, 12 December 2022 at 14:44
>> To: "users@nifi.apache.org " 
>> mailto:users@nifi.apache.org>>
>> Subject: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes 
>> issue
>>  
>> Hi guys
>>  
>> Sorry that I’ve to bother you again. We just upgraded to NiFi 1.19.1 due to 
>> the major issues with the NiFi Registry Client on NiFi 1.18.0.
>>  
>> The following issue still persists in the new version. Let’s say everything 
>> is up-to-date (parent and child PGs) from NiFi Registry perspective, now I 
>> do change eg. a label directly in the parent PG. I do see on that parent PG, 
>> that most likely every connection/service/processor has changed, even though 
>> I’ve changed only one single label size, please check the screenshot for 
>> NiFi Registry Client under “Show Local Changes”.  
>>  
>> 
>>  
>> Is this a cosmetical issue or do we have to worry about that (we had massive 
>> NiFi registry issue on NiFi 1.18.0) ? Because in theory it makes no sense to 
>> that NiFi tells that everything has changed if only one label changes.
>>  
>> Thanks in advance
>> Josef

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

[Josef.Zahner1]

Hi Bence

I mentioned yesterday another issue which we thought would be solved after the 
upgrade steps. Sadly it happened again and after an investigation on our side 
it seems to be fully reproducible, I’ve opened a Jira Bugticket 
https://issues.apache.org/jira/browse/NIFI-10973 with more details. It’s as 
well related to NiFi Registry nested flows…

Thanks for taking care of it :-).

Cheers Josef


From: Simon Bence 
Reply to: "users@nifi.apache.org" 
Date: Monday, 12 December 2022 at 16:40
To: "users@nifi.apache.org" 
Subject: Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes 
issue

Hi Josef,

Thanks for the quick update! Meanwhile I tried to reproduce this situation but 
based on the known facts I was not able (Note: without any version change). I 
think it is connected to the version change indeed, but if you face with this 
ever again, please let me know!

Regards,
Bence


On 2022. Dec 12., at 16:33, 
mailto:josef.zahn...@swisscom.com>> 
mailto:josef.zahn...@swisscom.com>> wrote:

Ok quick update on this. We investigated the changes on the *.snapshot files on 
NiFi Registry. It seems that it’s mainly caused due to the fact that the NiFi 
Version changes from 1.18.0 to 1.19.1 and some other facts caused due to the 
upgrade. After commiting all the child PGs once the “Show Local Changes” seems 
to behave as expected.
We have seen another issue caused only on the first commit of the child PGs on 
v1.19.1, however I’ll not mention them as I’m guessing that this is highly 
related to the last commits with the older NiFi version.

Cheers Josef


From: "Zahner Josef, GSB-LR-TRW-LI" 
mailto:josef.zahn...@swisscom.com>>
Date: Monday, 12 December 2022 at 14:44
To: "users@nifi.apache.org" 
mailto:users@nifi.apache.org>>
Subject: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

Hi guys

Sorry that I’ve to bother you again. We just upgraded to NiFi 1.19.1 due to the 
major issues with the NiFi Registry Client on NiFi 1.18.0.

The following issue still persists in the new version. Let’s say everything is 
up-to-date (parent and child PGs) from NiFi Registry perspective, now I do 
change eg. a label directly in the parent PG. I do see on that parent PG, that 
most likely every connection/service/processor has changed, even though I’ve 
changed only one single label size, please check the screenshot for NiFi 
Registry Client under “Show Local Changes”.



Is this a cosmetical issue or do we have to worry about that (we had massive 
NiFi registry issue on NiFi 1.18.0) ? Because in theory it makes no sense to 
that NiFi tells that everything has changed if only one label changes.

Thanks in advance
Josef



smime.p7s
Description: S/MIME Cryptographic Signature

Error on nifi start

[James McMahon]

I am using an Ansible role from Ansible GALAXY that has been tested and
validated up through Apache NiFi v1.14.0. I download and install 1.14.0.bin
from the Apache NiFi archives fir this reason.

I am using ansible to install on and AWS EC2 instance. My java version on
this instance is:

openjdk 17.0.5 2022-10-18 LTS

OpenJDK Runtime Environment Corretto-17.0.5.8.1

The install goes well. But when nifi attempts to start, it fails with the
following error message. Is this error indicating a compatibility issue
with the java installation on AWS? How should I proceed to get nifi to
start?

2022-12-13 02:50:39,316 ERROR [main] org.apache.nifi.NiFi Failure to launch
NiFi due to org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY]
Unable to make p

rotected final java.lang.Class
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
throws java.lang.ClassFormatError acce

ssible: module java.base does not "opens java.lang" to unnamed module
@31b289da

org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] Unable to
make protected final java.lang.Class
java.lang.ClassLoader.defineClass(java.lang.String,byte[]

,int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError
accessible: module java.base does not "opens java.lang" to unnamed module
@31b289da

at
org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:297)

at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227)

at org.xerial.snappy.Snappy.(Snappy.java:48)

at
org.apache.nifi.processors.hive.PutHiveStreaming.(PutHiveStreaming.java:158)

at java.base/java.lang.Class.forName0(Native Method)

at java.base/java.lang.Class.forName(Class.java:467)

at
org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328)

at
org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100)

at
org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65)

at
org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126)

at org.apache.nifi.NiFi.(NiFi.java:159)

at org.apache.nifi.NiFi.(NiFi.java:71)

at org.apache.nifi.NiFi.main(NiFi.java:303)