Does that mean I need to recreate the processor? Or there is some
workaround?
The processor gets unpacked and its bundled dependencies go in NAR_INF.
However when I drag the processor on the canvas, it comes with a yellow
triangle (and gives the error message I stated above) and properties are
I don’t remember all the reasoning behind the change, but it had to do with
an issue when we upgraded Jetty...
https://issues.apache.org/jira/browse/NIFI-5479
On Tue, Aug 13, 2019 at 9:47 PM Bimal Mehta wrote:
> Yes it does show as an option.
> One thing I noticed is that the when the nar is
Yes it does show as an option.
One thing I noticed is that the when the nar is unpacked, the bundled
dependencies are inside META_INF in the work folder in NiFi 1.6.0, however
in NiFI 1.9.0 they go inside NAR_INF.
Why does this happen?
It seems the custom processor that we have uses Springboot,
Does that custom processor type show as an option if you try to add a new
processor to the canvas?
On Tue, Aug 13, 2019 at 4:54 PM Bimal Mehta wrote:
> Hi Mike and Bryan,
>
> One of my custom processors appears as inactive in NiFi with a yellow
> triangle error.
> When I hover over it I see a
Hi Mike and Bryan,
One of my custom processors appears as inactive in NiFi with a yellow
triangle error.
When I hover over it I see a message saying 'Missing Processor' validated
against 'Any Property' is invalid. This is not a valid processor.
In the log it seems to invoke GhostProcessor.java
Joe,
Thank you for the information. Is this documented anywhere as I have a client
looking for it from Apache?.
Thank you,
:::
Jason Csencsits
Manager of Technical Operations
Technically Creative Inc.
Simplifying IT Solutions
Office: 845.725.7883
Jason
The work dir gets created at startup and possible as new nars are loaded.
I think you'd be ok to scan this.
The flowfile and content repository and provenance directories as
configured should be skipped. The logs dir should be skipped. The state
directory should be skipped. All else I
One of the easiest ways to trigger events in NiFi is to have a message
queue processor set up and listening to a queue where you post an event to
trigger the flow.
On Tue, Aug 13, 2019 at 11:45 AM Bimal Mehta wrote:
> Thanks Mike.
> ExecuteSQL looks good and am trying it.
>
> Also I wanted to
What is the recommended anti virus scanning exclusions from active scans. Can
not find anything in the documents. Need to make sure my linux redhat scans do
not compromise the flow files or anything else.
Thank you,
:::
Jason Csencsits
Manager of
Thanks Mike.
ExecuteSQL looks good and am trying it.
Also I wanted to understand how can we control triggering the NiFi jobs
from devops tools like CloudBees/ElectricFlow?
On Tue, Aug 13, 2019 at 7:35 AM Mike Thomsen wrote:
> Bimal,
>
> 1. Take a look at ExecuteSQLRecord and see if that works
oh, sorry, I forgot to mention i use the nifi docker image, with
configuration
services:
nifi-runner:
hostname: nifi-psh.adeo.com
image: apache/nifi:1.9.2
ports:
- "38080:8443"
- "5000:8000"
volumes:
-
${project.basedir}/target/docker-compose/includes/nifi/node/conf:/opt/nifi/nifi-current/conf
-
Might be a dumb question but I'm wondering why you're trying with port
38080? Did you change the configuration to use that specific port with a
secured instance?
Pierre
Le mar. 13 août 2019 à 16:00, Nicolas Delsaux a
écrit :
> To go a little further, a test with openssl s_client gives the
To go a little further, a test with openssl s_client gives the following
nicolas-delsaux@NICOLASDELSAUX C:\Users\nicolas-delsaux
$ openssl s_client -host localhost -port 38080
CONNECTED(0164)
416:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
Looks like you are using CompositeUserGroup provider which lets you combine
multiple user group providers.
The error message is saying the same user identity exists in more than one
of the user group providers which is not allowed.
The identity in the message looks like an LDAP user, so make
Great! Thank you very much for the info and references Elemir, and thanks
to Koji for the ReverseProxy experiment.
patw
On Mon, Aug 12, 2019 at 9:46 PM Elemir Stevko
wrote:
> Hi Pat,
>
> Koji Kawamura has a set of examples on how to configure NiFi behind
> reverse proxy that I have
I'm currently trying to implement ldap user group authorization in nifi.
For that, I've deployed nifi docker image with configuration files
containing required config elements (a ldap identity provider, a ldap
user group provider).
I've also configured https with a keystore/truststore that are
Bimal,
1. Take a look at ExecuteSQLRecord and see if that works for you. I don't
use SQL databases that much, but it works like a charm for me and others
for querying and getting an inferred avro schema based on the schema of the
database table (you can massage it into another format with
Hi
@Edward, @Pierre
thx for your replies. I will read the
articles and hope I find an inspiration.
Best,
Peter
On 13.08.19 09:11, Pierre Villard
wrote:
Hi Peter,
Hi Peter,
In addition to Edward's answer, you may be interested by the below posts:
https://pierrevillard.com/2017/05/11/monitoring-nifi-introduction/
https://pierrevillard.com/2018/02/07/fod-paris-jan-18-nifi-registry-and-workflow-monitoring-with-a-use-case/
Hi Mohit,
Did you create the appropriate rules in Ranger? Have the rules been
correctly synced between Ranger and NiFi nodes?
Pierre
Le mar. 13 août 2019 à 08:40, Mohit Jain a écrit :
> Hi,
>
> I've integrated Nifi-1.9.2 with ranger. When I login to the UI, following
> error is shown -
>
> No
Issue #1 - You should be able to specify an LDAP user as your initial
admin, what is the error you get?
Keep in mind it is case and white-space sensitive, and also depends on
whether you are returning full DN or short name, it must match exactly.
error
Multiple UserGroupProviders claim to
Hi,
I've integrated Nifi-1.9.2 with ranger. When I login to the UI, following
error is shown -
No applicable policies could be found. Contact the system administrator.
I'm not able to figure out what I'm missing. Kindly help.
Regards,
Mohit
22 matches
Mail list logo
