From d491cf08ebf694867c0575004974194c08cb5a27 Mon Sep 17 00:00:00 2001 From: Kamal Chandraprakash Date: Tue, 9 Oct 2018 16:32:44 +0530 Subject: [PATCH] KAFKA-7198: Enhance KafkaStreams start method javadoc. --- streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java | 1 + 1 file changed, 1 insertion(+) diff --git a/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java b/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java index 5fb89598507c8..49a701ae8aad5 100644 --- a/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java +++ b/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java @@ -765,6 +765,7 @@ private static HostInfo parseHostInfo(final String endPoint) { * This function is expected to be called only once during the life cycle of the client. *

* Because threads are started in the background, this method does not block. + * However, if you have global stores in your topology, this method blocks until all global stores are restored. * As a consequence, any fatal exception that happens during processing is by default only logged. * If you want to be notified about dying threads, you can * {@link #setUncaughtExceptionHandler(Thread.UncaughtExceptionHandler) register an uncaught exception handler}