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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17651698#comment-17651698 ] 

ASF subversion and git services commented on NIFI-10988:
--------------------------------------------------------

Commit b65431564ddf14073e3bf2f75cd0750a0ef07169 in nifi's branch refs/heads/main from Eric Bernard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b65431564d ]

NIFI-10988 - Fix ConsumeGCPubSubLite processors delivering incorrect messages

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #6788.


> 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
>            Reporter: Eric Bernard
>            Priority: Major
>              Labels: PubsubLiteIO
>   Original Estimate: 24h
>          Time Spent: 10m
>  Remaining Estimate: 23h 50m
>
> 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)