Hi Joe, This provides access to the entire Provenance Repository. Typically, what you would do is use the State Management feature (ReportingContext.getStateManager()) to store LOCAL-scoped state that includes the ID of the last provenance event pulled. You can then get a new batch of Provenance Events by calling ProvenanceEventRepository.getEvents(long startId, int maxResults).
Once you've processed those events, you can store the state via the state manager. Then, on each invocation, just use getStateManager().getState() to determine the last ID processed and go from there. Does this all make sense? Thanks -Mark > On Jul 6, 2016, at 9:02 AM, Gresock, Joseph <joseph.gres...@lmco.com> wrote: > > Hi folks, > > When developing a ReportingTask, I see that i can call > reportingContext.getEventAccess().getProvenanceRepository(). Will this > repository contain only provenance events created since the last time my > ReportingTask's onTrigger() was fired, or does it contain the entire > provenance repository to date? > > I'd like to develop a reporting task for metric purposes, and my hope is that > I can simply grab all the latest provenance events each time the reporting > task triggers. > > Thanks, > > Joe Gresock > Lockheed Martin Software Engineer Stf > 443-294-2661 > joseph.gres...@lmco.com
