You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Chad Zobrisky <cz...@gmail.com> on 2021/04/01 02:34:31 UTC
Provenance issues
Hello,
We have a single nifi instance that is experiencing weird provenance
results.
When querying for specific processors, there is no data returned and in the
logs we see...
2021-04-01 02:29:37,639 INFO [Provenance Query-1]
o.a.nifi.provenance.StandardQueryResult Completed Query[
[e286d901-a721-4743-be19-5aed93d9582f] ] comprise
d of 1 steps in 5 millis. Index found 2 hits. Read 0 events from Event
Files.
there
Is there any way to recover the events? New events for that processor also
aren't generated or queryable from the provenance UI; The index hits go up,
but no events returned still.
Thanks,
Chad
Re: Provenance issues
Posted by Joe Witt <jo...@gmail.com>.
Got ya. Would love to hear what you find when you give 1.13.2 a go
thanks
On Wed, Mar 31, 2021 at 7:41 PM Chad Zobrisky <cz...@gmail.com> wrote:
> We are on 1.12.1. Been trying to wait to update until 1.13 has been vetted
> a little more since this is a prod system, unless the consensus is to go
> straight to 1.13.2!
>
> Chad
>
> On Wed, Mar 31, 2021 at 10:36 PM Joe Witt <jo...@gmail.com> wrote:
>
> > i *think* this is fixed in 1.13. What version are you on?
> >
> > On Wed, Mar 31, 2021 at 7:34 PM Chad Zobrisky <cz...@gmail.com>
> wrote:
> >
> > > Hello,
> > >
> > > We have a single nifi instance that is experiencing weird provenance
> > > results.
> > >
> > > When querying for specific processors, there is no data returned and in
> > the
> > > logs we see...
> > >
> > > 2021-04-01 02:29:37,639 INFO [Provenance Query-1]
> > > o.a.nifi.provenance.StandardQueryResult Completed Query[
> > > [e286d901-a721-4743-be19-5aed93d9582f] ] comprise
> > > d of 1 steps in 5 millis. Index found 2 hits. Read 0 events from Event
> > > Files.
> > > there
> > >
> > > Is there any way to recover the events? New events for that processor
> > also
> > > aren't generated or queryable from the provenance UI; The index hits go
> > up,
> > > but no events returned still.
> > >
> > > Thanks,
> > > Chad
> > >
> >
>
Re: Provenance issues
Posted by Chad Zobrisky <cz...@gmail.com>.
We are on 1.12.1. Been trying to wait to update until 1.13 has been vetted
a little more since this is a prod system, unless the consensus is to go
straight to 1.13.2!
Chad
On Wed, Mar 31, 2021 at 10:36 PM Joe Witt <jo...@gmail.com> wrote:
> i *think* this is fixed in 1.13. What version are you on?
>
> On Wed, Mar 31, 2021 at 7:34 PM Chad Zobrisky <cz...@gmail.com> wrote:
>
> > Hello,
> >
> > We have a single nifi instance that is experiencing weird provenance
> > results.
> >
> > When querying for specific processors, there is no data returned and in
> the
> > logs we see...
> >
> > 2021-04-01 02:29:37,639 INFO [Provenance Query-1]
> > o.a.nifi.provenance.StandardQueryResult Completed Query[
> > [e286d901-a721-4743-be19-5aed93d9582f] ] comprise
> > d of 1 steps in 5 millis. Index found 2 hits. Read 0 events from Event
> > Files.
> > there
> >
> > Is there any way to recover the events? New events for that processor
> also
> > aren't generated or queryable from the provenance UI; The index hits go
> up,
> > but no events returned still.
> >
> > Thanks,
> > Chad
> >
>
Re: Provenance issues
Posted by Joe Witt <jo...@gmail.com>.
i *think* this is fixed in 1.13. What version are you on?
On Wed, Mar 31, 2021 at 7:34 PM Chad Zobrisky <cz...@gmail.com> wrote:
> Hello,
>
> We have a single nifi instance that is experiencing weird provenance
> results.
>
> When querying for specific processors, there is no data returned and in the
> logs we see...
>
> 2021-04-01 02:29:37,639 INFO [Provenance Query-1]
> o.a.nifi.provenance.StandardQueryResult Completed Query[
> [e286d901-a721-4743-be19-5aed93d9582f] ] comprise
> d of 1 steps in 5 millis. Index found 2 hits. Read 0 events from Event
> Files.
> there
>
> Is there any way to recover the events? New events for that processor also
> aren't generated or queryable from the provenance UI; The index hits go up,
> but no events returned still.
>
> Thanks,
> Chad
>