You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by ph...@orange.com on 2016/11/15 13:56:29 UTC

REST APIs provenance-events API

Hello, My SW context : nifi 1.0.0/ubuntu
I would like to know if both following REST API calls :
GET /provenance-events/{id}/content/input
GET /provenance-events/{id}/content/output

Are related to getting in the response the  flowfile content before and after an event happened on a processor .

My Use case is :
run a dataflow and inspect on every involved  processor in the DF  the flow-content data before and after some  events  ?

Best regards
Philippe


[Description : Description : Description : cid:image002.gif@01CDFAED.D49218F0]<http://www.orange.com/>
Philippe Gibert
Ingénieur R&D
FT/IMT/OLPS/BIZZ/INFSVC/ITS4B
tél. +33 4 92 94 53 70
mob. +33 6 73 41 11 18
philippe.gibert@orange.com



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Re: REST APIs provenance-events API

Posted by Matt Gilman <ma...@gmail.com>.
Philippe,

Yes, you are correct. These are the endpoints to access flowfile content
before and after a given provenance event. Specifically, these map to the
View/Download buttons in the Content tab for the Input and Output Claim in
the provenance event details dialog.

Matt

On Tue, Nov 15, 2016 at 8:56 AM, <ph...@orange.com> wrote:

> Hello, My SW context : nifi 1.0.0/ubuntu
>
> I would like to know if both following REST API calls :
>
> GET /provenance-events/{id}/content/input
>
> GET /provenance-events/{id}/content/output
>
>
>
> Are related to getting in the response the  flowfile content before and
> after an event happened on a processor .
>
>
>
> My Use case is :
>
> run a dataflow and inspect on every involved  processor in the DF  the
> flow-content data before and after some  events  ?
>
>
>
> Best regards
>
> Philippe
>
>
>
>
>
> [image: Description : Description : Description :
> cid:image002.gif@01CDFAED.D49218F0] <http://www.orange.com/>
>
> Philippe Gibert
>
> Ingénieur R&D
>
> FT/IMT/OLPS/BIZZ/INFSVC/ITS4B
>
> tél. +33 4 92 94 53 70
>
> mob. +33 6 73 41 11 18
>
> philippe.gibert@orange.com
>
>
>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>