You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2022/12/23 17:32:00 UTC

[jira] [Updated] (NIFI-10988) Using multiple ConsumeGCPubSubLite processors causes misrouting of messages

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

Pierre Villard updated NIFI-10988:
----------------------------------
    Affects Version/s: 1.19.1
                       1.19.0
                       1.18.0
                       1.16.3
                       1.16.2
                       1.16.1
                       1.17.0
                       1.16.0

> Using multiple ConsumeGCPubSubLite processors causes misrouting of messages
> ---------------------------------------------------------------------------
>
>                 Key: NIFI-10988
>                 URL: https://issues.apache.org/jira/browse/NIFI-10988
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.16.0, 1.17.0, 1.16.1, 1.16.2, 1.16.3, 1.18.0, 1.19.0, 1.19.1
>            Reporter: Eric Bernard
>            Assignee: Eric Bernard
>            Priority: Major
>              Labels: PubsubLiteIO
>             Fix For: 1.20.0
>
>   Original Estimate: 24h
>          Time Spent: 20m
>  Remaining Estimate: 23h 40m
>
> The first instance of a ConsumeGCPubSubLite processor works as-expected. However, every subsequent instance of the processor, even if consuming from different subscriptions, will produce FlowFiles from the original instance's queue.
> For example, Processor A is consuming data from Subscription A and routes messages without issue. Then, Processor B consuming from Subscription B is added. The FlowFiles produced by Processor B will contain data from Subscription A; moreover, no FlowFiles with data from Subscription B will ever be emitted by Processor B. Any subsequent ConsumeGCPubSubLite processor will show the same behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)