You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2025/08/26 15:18:00 UTC

[jira] [Updated] (KAFKA-19647) Implement integration test for offline migration

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

Lucas Brutschy updated KAFKA-19647:
-----------------------------------
    Description: 
In https://issues.apache.org/jira/browse/KAFKA-19570 we implemented offline migration between groups, that is, the following integration test or system test should be possible:

Test A:
 * Start a streams application with classic protocol, process up to a certain offset and commit the offset and shut down.

 * Start the same streams application with streams protocol (same app ID!).

 * Make sure that the offsets before the one committed in the first run are not reprocessed in the second run.

 

Test B:
 * Start a streams application with streams protocol, process up to a certain offset and commit the offset and shut down.

 * Start the same streams application with classic protocol (same app ID!).

 * Make sure that the offsets before the one committed in the first run are not reprocessed in the second run.

 

We have unit tests that make sure that non-empty groups will not be converted. This should be enough.

> Implement integration test for offline migration
> ------------------------------------------------
>
>                 Key: KAFKA-19647
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19647
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Lucas Brutschy
>            Assignee: Lucas Brutschy
>            Priority: Major
>
> In https://issues.apache.org/jira/browse/KAFKA-19570 we implemented offline migration between groups, that is, the following integration test or system test should be possible:
> Test A:
>  * Start a streams application with classic protocol, process up to a certain offset and commit the offset and shut down.
>  * Start the same streams application with streams protocol (same app ID!).
>  * Make sure that the offsets before the one committed in the first run are not reprocessed in the second run.
>  
> Test B:
>  * Start a streams application with streams protocol, process up to a certain offset and commit the offset and shut down.
>  * Start the same streams application with classic protocol (same app ID!).
>  * Make sure that the offsets before the one committed in the first run are not reprocessed in the second run.
>  
> We have unit tests that make sure that non-empty groups will not be converted. This should be enough.



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