liuliuOD opened a new pull request, #23533:
URL: https://github.com/apache/kafka/pull/23533

   ## Summary
   
   `KTableKTableForeignKeyInnerJoinMultiIntegrationTest` reused the same 
application ID across parameterized invocations. This allowed the next 
invocation to reuse the previous Streams application and consumer group 
identity.
   
   ## Scope
   
   - Affected test: `KTableKTableForeignKeyInnerJoinMultiIntegrationTest`
   - Affected module: `streams/integration-tests`
   
   ## Optimization
   
   Assign a test-specific application ID and result consumer group to each 
parameterized invocation.
   
   The three Kafka Streams instances within the same invocation continue to 
share the same application ID, preserving the original multi-instance test 
scenario.
   
   ## Before / After
   
   | Measurement | Before | After | Improvement |
   | --- | ---: | ---: | ---: |
   | `withHeaders=true` | 47.473s | 5.870s | 41.603s faster |
   | Both parameterized cases | 56.589s | 15.100s | 41.489s faster |
   
   Measurements use the same test filter and compare JUnit XML execution time, 
excluding Gradle build and compilation.
   
   ## Test Semantics Preserved
   
   - Both parameterized cases remain unchanged.
   - The three Streams instances continue to share one application ID per 
invocation.
   - The topology, input data, materialized stores, and assertions remain 
unchanged.
   - Multi-partition and foreign-key join behavior are still covered.
   
   ## Validation
   
   ```text
   ./gradlew :streams:integration-tests:test \
     --tests 
org.apache.kafka.streams.integration.KTableKTableForeignKeyInnerJoinMultiIntegrationTest
 \
     --no-daemon
   ```
   
   Both parameterized cases passed:
   
   - `withHeaders=false`
   - `withHeaders=true`
   
   ## Risk and Compatibility
   
   This is a test-only change. It does not modify production code, public APIs, 
protocols, configuration, topology, or assertions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to