You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "CheVeyo (JIRA)" <ji...@apache.org> on 2018/01/04 10:50:00 UTC

[jira] [Updated] (NIFI-4722) [Question] External Procession, keeping the flow fileid and provenance

     [ https://issues.apache.org/jira/browse/NIFI-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

CheVeyo updated NIFI-4722:
--------------------------
    Priority: Major  (was: Minor)

> [Question] External Procession, keeping the flow fileid and provenance
> ----------------------------------------------------------------------
>
>                 Key: NIFI-4722
>                 URL: https://issues.apache.org/jira/browse/NIFI-4722
>             Project: Apache NiFi
>          Issue Type: Wish
>          Components: Core Framework
>    Affects Versions: 1.4.0
>            Reporter: CheVeyo
>              Labels: features
>
> Hi,
> If i want to do some sort of external procession (async without blocking). I would send it via amqp to the service an would reingest it with consumeamqp. First question is this the right approach to do it? or are there better options? I need something very performant above 30k flowfiles per seconds. The thing is the moment i reingest it via amqp, it gets a new flowfile id and the provenance is somehow broken :( What can we do about it? Is amqp the write option to send stuff for external processing?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)