Hi ,
please ignore my previous mail.as i got the answer.
On Wed, 30 Oct, 2019, 8:16 AM sanjeet rath, wrote:
> Hi,
> I have built custom controller service(AWS-CREDENTIAL-CONTROLER-SERVICE)
> and use this one in processor service(NIFI-AWS-SERVICE).for puts3Object.
> In this controller service
Hi,
I have built custom controller service(AWS-CREDENTIAL-CONTROLER-SERVICE)
and use this one in processor service(NIFI-AWS-SERVICE).for puts3Object.
In this controller service i have used custom parameters to connect to aws
and getting token , also using this token i am able to to use connect AW
Thank you everyone!
Peter
On Mon, Oct 28, 2019 at 6:06 PM Andy LoPresto wrote:
> Congratulations Peter. Looking forward to your continued contributions.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.10.0.
As they say 'third time's a charm'.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1151
The source being voted up
Nissim
I like the idea to introduce a more refined type of event for how data is
brought into nifi (active - PULL, passive - RECEIVE).
That said it might be sufficient to simply have this distinction be on the
"RECEIVE" event as a metadata item specifying active vs passive. The
protocol utilized
Adam,
good points...
I missed a step in explaining the use case where Provenance Events is
incomplete...
Where the second nifi does a GetSFTP from the *filesytem* that the first nifi
is located on
So the second nifi currently sends a RECEIVE event, but there is no
corresponding SEND event from
