We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pattern
The Dev UI for Kafka Streams shows no / an empty topology when the source topic uses a Pattern instead of static names.
package org.acme.consumer; import org.apache.kafka.common.serialization.Serdes; import org.apache.kafka.streams.StreamsBuilder; import org.apache.kafka.streams.Topology; import org.apache.kafka.streams.kstream.Consumed; import org.apache.kafka.streams.kstream.KStream; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import javax.enterprise.context.ApplicationScoped; import javax.enterprise.inject.Produces; import java.util.regex.Pattern; @ApplicationScoped class NotificationTopologyBuilder { private static final Logger LOGGER = LoggerFactory.getLogger(NotificationTopologyBuilder.class); @Produces public Topology topology() { final var streamsBuilder = new StreamsBuilder(); streamsBuilder .stream(Pattern.compile("notification\\..+"), Consumed.with(Serdes.String(), Serdes.String())) .foreach((key, notification) -> LOGGER.info(notification)); final Topology topology = streamsBuilder.build(); LOGGER.info("Topology: {}", topology.describe()); return topology; } }
Upon startup, this logs:
Topology: Topologies: Sub-topology: 0 Source: KSTREAM-SOURCE-0000000000 (topics: notification\..+) --> KSTREAM-FOREACH-0000000001 Processor: KSTREAM-FOREACH-0000000001 (stores: []) --> none <-- KSTREAM-SOURCE-0000000000
The Dev UI should show display the topology, even when the input topic uses a pattern.
The Dev UI does not pick up the topology. It is neither available in image, nor in text format.
Changing the source topic to a static name causes the topology to be picked up correctly:
The log output in this case is:
Topology: Topologies: Sub-topology: 0 Source: KSTREAM-SOURCE-0000000000 (topics: [notification.repository]) --> KSTREAM-FOREACH-0000000001 Processor: KSTREAM-FOREACH-0000000001 (stores: []) --> none <-- KSTREAM-SOURCE-0000000000
kafka-streams
uname -a
ver
Linux ctrl 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
java -version
openjdk version "17.0.4.1" 2022-08-12 OpenJDK Runtime Environment Temurin-17.0.4.1+1 (build 17.0.4.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (build 17.0.4.1+1, mixed mode, sharing)
No response
2.14.1.Final
mvnw --version
gradlew --version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
The text was updated successfully, but these errors were encountered:
/cc @alesj, @cescoffier, @gunnarmorling, @ozangunalp, @rquinio
Sorry, something went wrong.
@tmihalac this one might be a good fit for you.
See #46599 for a fix proposal
Successfully merging a pull request may close this issue.
Describe the bug
The Dev UI for Kafka Streams shows no / an empty topology when the source topic uses a
Pattern
instead of static names.Upon startup, this logs:
Expected behavior
The Dev UI should show display the topology, even when the input topic uses a pattern.
Actual behavior
The Dev UI does not pick up the topology. It is neither available in image, nor in text format.
Changing the source topic to a static name causes the topology to be picked up correctly:
The log output in this case is:
How to Reproduce?
kafka-streams
extensionOutput of
uname -a
orver
Linux ctrl 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.4.1" 2022-08-12 OpenJDK Runtime Environment Temurin-17.0.4.1+1 (build 17.0.4.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (build 17.0.4.1+1, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.14.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Additional information
No response
The text was updated successfully, but these errors were encountered: