> But a flowfile that was PULLed by the second nifi (from the first nifi)
will not necessarily have any provenance event generated by the first nifi.
Isn't this the fault of the first NiFi to fail to emit a SEND event in
response to the second NiFi's request? In this scenario, shouldn't the
Some developer could verify this problem:
https://issues.apache.org/jira/browse/NIFI-6800
regards
Ivan
Adam,
I believe there is a need for more detailed ProvenanceEvents.
A use case would be a customer that is trying to track data passed between two
nifi's and trying to match up SENDs and RECEIVEs
So a flowfile that has a SEND event on the first nifi should have a RECEIVE
event on the second
David
No - i get it. I'm just giving some color to help explain what makes it
easier to get things in. We effectively have two motions
1) Contributions made
2) Contributions reviewed/tested/merged
We have a lot more people focused on #1 and a lot fewer on #2. As a result
the pipeline of open
Hey Joe,
I hope you didn't understand my email to be some sort of complaint or
critique of the process. I can now see how it could be misconstrued as
such. What I meant was that I was motivated to get in done, just needed
some direction.
Thanks again,
David
On Mon, Oct 28, 2019, 4:58 PM Joe
David - I will take a look at this for you. However I will say here (and on
the review) that I believe the "ignorelocality" should be defaulted to
"True" by default simply to maintain functionality closer to the
original implementation.
Thanks,
Jeremy Dyer
On Mon, Oct 28, 2019 at 4:55 PM David
I am deep in the RC3 prep process and have been grabbing as I can. This
looks ok to grab and I plan to do so now. But, please understand we need
help from detailed/thoughtful reviews to help this pipeline function. We
get tons of great contribs but the review part is equally important.
Please
I do apologies if I am sending a duplicate of the following message. I'm
not sure if the first one went through...
I've been working on this effort for more than a year. I'm hoping someone
can assist me in getting it over the finish line.
PR needs a review.
Hi,
We are doing a migration from a single instance NiFi to a NiFi cluster mode
(with 3 nodes) using Cloudera Manager.
After staring all the 3 nodes from Cloudera Manager, only 1 shows connected
and the others appear disconnected.
In the log file for the 2 nodes that are showing disconnected, we
pulled that pr in and am testing build after fixing conflict. If it seems
ok will merge.
But no the intent isn't to grab things from the PR pile between RCs. The
community should always work to merge in features/fixes/etc.. and we should
also work to generate releases.
Thanks
On Mon, Oct 28,
Joe/Andy,
Should we include this one bug fix that a user recently needed for an
Elastic/Apache HttpClient SSL bug?
https://github.com/apache/nifi/pull/3828
On Mon, Oct 28, 2019 at 2:11 PM Joe Witt wrote:
> Team,
>
> Please be careful in JIRA to mark new things merged to master as fixed for
>
Team,
Please be careful in JIRA to mark new things merged to master as fixed for
1.11.
The 1.10 release is now in release candidate stage and therefore going to
master is for the next release line. If appropriate/able the release
manager (in this case me) will pull it into the 1.10 release and
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
> On Oct 28, 2019, at 9:39 AM, Matt Burgess wrote:
>
> Congratulations Peter!
>
> On Sun,
Congratulations Peter!
On Sun, Oct 27, 2019 at 9:05 PM Aldrin Piri wrote:
>
> Apache NiFi community,
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Peter
> has accepted the PMC's invitation to become a committer on the Apache NiFi
> project. We greatly appreciate all of
Congratulations!
On October 27, 2019 at 21:05:58, Aldrin Piri (aldrinp...@gmail.com) wrote:
Apache NiFi community,
On behalf of the Apache NiFI PMC, I am very pleased to announce that Peter
has accepted the PMC's invitation to become a committer on the Apache NiFi
project. We greatly
Welcome and thanks Peter
On Mon, Oct 28, 2019 at 7:52 AM Kevin Doran wrote:
> Congrats, Peter! Thanks for your contributions!
>
> On Mon, Oct 28, 2019 at 5:24 AM Mike Thomsen
> wrote:
> >
> > Congratulations, Peter!
> >
> > On Mon, Oct 28, 2019 at 3:13 AM Sivaprasanna
> > wrote:
> >
> > >
Congrats, Peter! Thanks for your contributions!
On Mon, Oct 28, 2019 at 5:24 AM Mike Thomsen wrote:
>
> Congratulations, Peter!
>
> On Mon, Oct 28, 2019 at 3:13 AM Sivaprasanna
> wrote:
>
> > Congratulations, Peter.
> >
> > On Mon, 28 Oct 2019 at 12:30 PM, Pierre Villard <
> >
Congratulations, Peter!
On Mon, Oct 28, 2019 at 3:13 AM Sivaprasanna
wrote:
> Congratulations, Peter.
>
> On Mon, 28 Oct 2019 at 12:30 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> > Congratulations Peter!
> >
> > Le lun. 28 oct. 2019 à 02:05, Aldrin Piri a
> écrit :
> >
> >
Congratulations, Peter.
On Mon, 28 Oct 2019 at 12:30 PM, Pierre Villard
wrote:
> Congratulations Peter!
>
> Le lun. 28 oct. 2019 à 02:05, Aldrin Piri a écrit :
>
> > Apache NiFi community,
> >
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Peter
> > has accepted the
Congratulations Peter!
Le lun. 28 oct. 2019 à 02:05, Aldrin Piri a écrit :
> Apache NiFi community,
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Peter
> has accepted the PMC's invitation to become a committer on the Apache NiFi
> project. We greatly appreciate all of
20 matches
Mail list logo
