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

Posted to commits@samza.apache.org by "Ajo Thomas (Jira)" <ji...@apache.org> on 2022/11/01 16:25:00 UTC

[jira] [Updated] (SAMZA-2766) [Pipeline Drain] Fix processing of Drain messages for both low-level and high level API

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

Ajo Thomas updated SAMZA-2766:
------------------------------
    Description: After some end-to-end test, it was determined that the RunLoop was stalling for both high-level and low-level API pipelines even though the integration test for both cases was running. The integration test uses an in-memory topic and in-memory metadata store and therefore it did not capture the real world behavior accurately.

> [Pipeline Drain] Fix processing of Drain messages for both low-level and high level API
> ---------------------------------------------------------------------------------------
>
>                 Key: SAMZA-2766
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2766
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Ajo Thomas
>            Priority: Major
>
> After some end-to-end test, it was determined that the RunLoop was stalling for both high-level and low-level API pipelines even though the integration test for both cases was running. The integration test uses an in-memory topic and in-memory metadata store and therefore it did not capture the real world behavior accurately.



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