It copies all of the provenance data, and no, there's no way yet to back the provenance repository with one of those nosql databases yet unfortunately.
On Mon, May 4, 2020 at 6:40 PM Eric Secules <esecu...@gmail.com> wrote: > What information is transmitted by SiteToSiteProvenanceReporting? Is it > the content, the attributes, and the path the flowfile takes through the > system? Is there any way to connect the provenance view from NiFi to the > nosql database instead of the internal provenance storage? > > On Mon, May 4, 2020 at 3:07 PM Mike Thomsen <mikerthom...@gmail.com> > wrote: > >> One way to do it would be to set up a SiteToSiteProvenanceReporting task >> and have it send the data to another NiFi instance. That instance can post >> all of the provenance data into a NoSQL database like Mongo or >> Elasticsearch very quickly. >> >> On Mon, May 4, 2020 at 5:47 PM Eric Secules <esecu...@gmail.com> wrote: >> >>> Hello everyone, >>> >>> If I am upgrading a process group to the latest version, do you know >>> whether provenance is preserved for processors that may get deleted in the >>> upgrade? >>> I have noticed that if I delete my process group and redownload it from >>> the registry, I am no longer able to see the provenance data from flowfiles >>> that went through the first process group. >>> >>> What is the best way to view and archive provenance data for older >>> versions of flows? For background I am running NiFi in a docker container. >>> I think I might have to archive the currently running container and >>> bring the new version up on a new container. >>> >>> Thanks, >>> Eric >>> >>
