[
https://issues.apache.org/jira/browse/KAFKA-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-12506:
----------------------------------
Description:
Right now the AdjustStreamThreadCountTest runs a minimal topology that just
consumes a single input topic, and doesn't produce any data to this topic. Some
of the complex concurrency bugs that we've found only showed up when we had
some actual data to process and a stateful topology:
[KAFKA-12503|https://issues.apache.org/jira/browse/KAFKA-12503] KAFKA-12500
We should try to expand the Streams application in this test to really flex the
feature. Imo this would include
# Produce some data to the input topic
# One or more stateful operators in the topology, with caching enabled
# A repartition to get multiple subtopologies
# Write out some results to an output topic
# Verify that these results show up in the output
was:
Right now the AdjustStreamThreadCountTest runs a minimal topology that just
consumes a single input topic, and doesn't produce any data to this topic. Some
of the complex concurrency bugs that we've found only showed up when we had
some actual data to process and a stateful topology:
[KAFKA-12503|https://issues.apache.org/jira/browse/KAFKA-12503]
https://issues.apache.org/jira/browse/KAFKA-12500
We should try to expand the Streams application in this test to really flex the
feature. Imo this would include
# Produce some data to the input topic
# One or more stateful operators in the topology, with caching enabled
# A repartition to get multiple subtopologies
# Write out some results to an output topic
# Verify that these results show up in the output
> Expand AdjustStreamThreadCountTest
> ----------------------------------
>
> Key: KAFKA-12506
> URL: https://issues.apache.org/jira/browse/KAFKA-12506
> Project: Kafka
> Issue Type: Improvement
> Components: streams, unit tests
> Reporter: A. Sophie Blee-Goldman
> Priority: Major
> Labels: newbie, newbie++
>
> Right now the AdjustStreamThreadCountTest runs a minimal topology that just
> consumes a single input topic, and doesn't produce any data to this topic.
> Some of the complex concurrency bugs that we've found only showed up when we
> had some actual data to process and a stateful topology:
> [KAFKA-12503|https://issues.apache.org/jira/browse/KAFKA-12503] KAFKA-12500
> We should try to expand the Streams application in this test to really flex
> the feature. Imo this would include
> # Produce some data to the input topic
> # One or more stateful operators in the topology, with caching enabled
> # A repartition to get multiple subtopologies
> # Write out some results to an output topic
> # Verify that these results show up in the output
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
