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
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
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
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
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
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
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
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
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:
>
>
>
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
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
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.
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
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
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
15 matches
Mail list logo