Re: how to organise processor or PG in the Nifi canvas ?
Try importing via thr NiFi cli tool. I've implemented the logic to auto layout newly imported PGs. But I agree, this should be something included in the core NiFi logic itself. Andrew On Fri, Sep 14, 2018, 4:17 PM Dominique De Vito wrote: > Hi, > > Is there a way to re-organize automatically the processors or PG inside > the Nifi canvas ? > > I create PG through REST api. > I set originX and originY for all PG I create, but the created PG could be > on top of another PG (for example, previously existing) and the first one > could be hiding the second one. > > So, I wonder if there is already a way in Nifi to re-organize the "boxes" > inside the Nifi canvas to minimize box overlapping for example. > > Any idea ? > > Thanks. > > Dominique > >
how to organise processor or PG in the Nifi canvas ?
Hi, Is there a way to re-organize automatically the processors or PG inside the Nifi canvas ? I create PG through REST api. I set originX and originY for all PG I create, but the created PG could be on top of another PG (for example, previously existing) and the first one could be hiding the second one. So, I wonder if there is already a way in Nifi to re-organize the "boxes" inside the Nifi canvas to minimize box overlapping for example. Any idea ? Thanks. Dominique
Re: problem with instanciating NEW (custom) processors
Well, I have found the pb. Not on the Nifi side ;-) I have had some config troubles leading to using wrong env. Sorry for the msg... I need some rest these days. Le ven. 14 sept. 2018 à 13:42, Mike Thomsen a écrit : > Did you change their names when you created your new versions? > On Fri, Sep 14, 2018 at 6:59 AM Dominique De Vito > wrote: > >> Hi, >> >> I have defined 5 new (custom) processors (derivated respectively from >> existing ones - ConsumeKafka, GetSFTP, GetFile, ListenTCP an ListFile) into >> 2 NAR (1 NAR with 1 processor, the other processors are into the other NAR). >> >> After copying the NARs into /lib, and after restarting Nifi, only 3 over >> 5 are proposed by Nifi UI. >> >> No ERROR message in the logs. >> >> No exception in the logs. >> >> And according to the traces, the processor constructors are called / >> instanciated and there are all declared into META-INF/services directory. >> >> Still, I have found only 3 over 5 processors in the Nifi UI. >> >> Does anyone have a clue about it ? >> >> Thanks. >> >> >> Dominique >> >>
Re: problem with instanciating NEW (custom) processors
> Did you change their names when you created your new versions? Yes, for all of them. As I have modified those processors for fetching the source defs from Atlas, GetFile processor, for example, has been derivated into GetFileWithAtlas. All their names follow the pattern "xxxWithAtlas" Anyway, thanks for the idea. Dominique Le ven. 14 sept. 2018 à 13:42, Mike Thomsen a écrit : > Did you change their names when you created your new versions? > On Fri, Sep 14, 2018 at 6:59 AM Dominique De Vito > wrote: > >> Hi, >> >> I have defined 5 new (custom) processors (derivated respectively from >> existing ones - ConsumeKafka, GetSFTP, GetFile, ListenTCP an ListFile) into >> 2 NAR (1 NAR with 1 processor, the other processors are into the other NAR). >> >> After copying the NARs into /lib, and after restarting Nifi, only 3 over >> 5 are proposed by Nifi UI. >> >> No ERROR message in the logs. >> >> No exception in the logs. >> >> And according to the traces, the processor constructors are called / >> instanciated and there are all declared into META-INF/services directory. >> >> Still, I have found only 3 over 5 processors in the Nifi UI. >> >> Does anyone have a clue about it ? >> >> Thanks. >> >> >> Dominique >> >>
Re: problem with instanciating NEW (custom) processors
Did you change their names when you created your new versions? On Fri, Sep 14, 2018 at 6:59 AM Dominique De Vito wrote: > Hi, > > I have defined 5 new (custom) processors (derivated respectively from > existing ones - ConsumeKafka, GetSFTP, GetFile, ListenTCP an ListFile) into > 2 NAR (1 NAR with 1 processor, the other processors are into the other NAR). > > After copying the NARs into /lib, and after restarting Nifi, only 3 over 5 > are proposed by Nifi UI. > > No ERROR message in the logs. > > No exception in the logs. > > And according to the traces, the processor constructors are called / > instanciated and there are all declared into META-INF/services directory. > > Still, I have found only 3 over 5 processors in the Nifi UI. > > Does anyone have a clue about it ? > > Thanks. > > > Dominique > >
problem with instanciating NEW (custom) processors
Hi, I have defined 5 new (custom) processors (derivated respectively from existing ones - ConsumeKafka, GetSFTP, GetFile, ListenTCP an ListFile) into 2 NAR (1 NAR with 1 processor, the other processors are into the other NAR). After copying the NARs into /lib, and after restarting Nifi, only 3 over 5 are proposed by Nifi UI. No ERROR message in the logs. No exception in the logs. And according to the traces, the processor constructors are called / instanciated and there are all declared into META-INF/services directory. Still, I have found only 3 over 5 processors in the Nifi UI. Does anyone have a clue about it ? Thanks. Dominique
