Package org.apache.kafka.streams.kstream

Interface KGroupedStream<K,​V>

  • Type Parameters:
    K - Type of keys
    V - Type of values
    @Evolving
public interface KGroupedStream<K,​V>
    KGroupedStream is an abstraction of a grouped record stream of KeyValue pairs. It is an intermediate representation of a KStream in order to apply an aggregation operation on the original KStream records.

    It is an intermediate representation after a grouping of a KStream before an aggregation is applied to the new partitions resulting in a KTable.

    A KGroupedStream must be obtained from a KStream via groupByKey() or groupBy(...).

    See Also:
    KStream

    • Method Detail

      • count

        @Deprecated
KTable<K,​java.lang.Long> count​(java.lang.String queryableStoreName)
        Deprecated.
        use count(Materialized.as(queryableStoreName))
        Count the number of records in this stream by the grouped key. Records with null key or value are ignored. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // counting words
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-word";
 Long countForWord = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        queryableStoreName - the name of the underlying KTable state store; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to count().
        Returns:
        a KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key

      • count

        KTable<K,​java.lang.Long> count()
        Count the number of records in this stream by the grouped key. Records with null key or value are ignored. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view). Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Returns:
        a KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key

      • count

        @Deprecated
KTable<K,​java.lang.Long> count​(StateStoreSupplier<KeyValueStore> storeSupplier)
        Deprecated.
        use count(Materialized.as(KeyValueByteStoreSupplier))
        Count the number of records in this stream by the grouped key. Records with null key or value are ignored. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStore.name() to get the store name: 

        
 KafkaStreams streams = ... // counting words
 String queryableStoreName = storeSupplier.name();
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-word";
 Long countForWord = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key

      • count

        KTable<K,​java.lang.Long> count​(Materialized<K,​java.lang.Long,​KeyValueStore<org.apache.kafka.common.utils.Bytes,​byte[]>> materialized)
        Count the number of records in this stream by the grouped key. Records with null key or value are ignored. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) provided by the given materialized. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...). 

        
 KafkaStreams streams = ... // counting words
 String queryableStoreName = "count-store"; // the queryableStoreName should be the name of the store as defined by the Materialized instance
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-word";
 Long countForWord = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        materialized - an instance of Materialized used to materialize a state store. Cannot be null. Note: the valueSerde will be automatically set to Serdes.Long() if there is no valueSerde provided
        Returns:
        a KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key

      • count

        @Deprecated
<W extends Window> KTable<Windowed<K>,​java.lang.Long> count​(Windows<W> windows,
                                                                  java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(windows) followed by count(Materialized.as(queryableStoreName))
        Count the number of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // counting words
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-word";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> countForWordsForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        windows - the specification of the aggregation Windows
        queryableStoreName - the name of the underlying KTable state store; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to count(Windows).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window.

      • count

        @Deprecated
<W extends Window> KTable<Windowed<K>,​java.lang.Long> count​(Windows<W> windows)
        Deprecated.
        use windowedBy(windows) followed by count()
        Count the number of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        windows - the specification of the aggregation Windows
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window

      • count

        @Deprecated
<W extends Window> KTable<Windowed<K>,​java.lang.Long> count​(Windows<W> windows,
                                                                  StateStoreSupplier<WindowStore> storeSupplier)
        Deprecated.
        use windowedBy(windows) followed by count(Materialized.as(KeyValueByteStoreSupplier))
        Count the number of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // counting words
 String queryableStoreName = storeSupplier.name();
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-word";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> countForWordsForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        windows - the specification of the aggregation Windows
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window

      • count

        @Deprecated
KTable<Windowed<K>,​java.lang.Long> count​(SessionWindows sessionWindows,
                                               java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(sessionWindows) followed by count(Materialized.as(queryableStoreName))
        Count the number of records in this stream by the grouped key into SessionWindows. Records with null key or value are ignored. The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). 

        
 KafkaStreams streams = ... // compute sum
 ReadOnlySessionStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>ReadOnlySessionStore<String, Long>);
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> sumForKeyForWindows = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        sessionWindows - the specification of the aggregation SessionWindows
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-. If null then this will be equivalent to count(SessionWindows).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window

      • count

        @Deprecated
KTable<Windowed<K>,​java.lang.Long> count​(SessionWindows sessionWindows)
        Deprecated.
        use windowedBy(sessionWindows) followed by count()
        Count the number of records in this stream by the grouped key into SessionWindows. Records with null key or value are ignored. The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        Parameters:
        sessionWindows - the specification of the aggregation SessionWindows
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window

      • count

        @Deprecated
KTable<Windowed<K>,​java.lang.Long> count​(SessionWindows sessionWindows,
                                               StateStoreSupplier<SessionStore> storeSupplier)
        Deprecated.
        use windowedBy(sessionWindows) followed by count(Materialized.as(KeyValueByteStoreSupplier))
        Count the number of records in this stream by the grouped key into SessionWindows. Records with null key or value are ignored. The result is written into a local SessionStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // compute sum
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlySessionStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>ReadOnlySessionStore<String, Long>);
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> sumForKeyForWindows = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        sessionWindows - the specification of the aggregation SessionWindows
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys and Long values that represent the latest (rolling) count (i.e., number of records) for each key within a window

      • reduce

        KTable<K,​V> reduce​(Reducer<V> reducer)
        Combine the values of records in this stream by the grouped key. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator)). The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate and the record's value. If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • reduce

        @Deprecated
KTable<K,​V> reduce​(Reducer<V> reducer,
                         java.lang.String queryableStoreName)
        Deprecated.
        use reduce(reducer, Materialized.as(queryableStoreName))
        Combine the values of records in this stream by the grouped key. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Serde, String)). The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // compute sum
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long sumForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        queryableStoreName - the name of the underlying KTable state store; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to reduce(Reducer) ()}.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • reduce

        @Deprecated
KTable<K,​V> reduce​(Reducer<V> reducer,
                         StateStoreSupplier<KeyValueStore> storeSupplier)
        Deprecated.
        use reduce(reducer, Materialized.as(KeyValueByteStoreSupplier))
        Combine the value of records in this stream by the grouped key. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, org.apache.kafka.streams.processor.StateStoreSupplier)). The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // compute sum
 String queryableStoreName = storeSupplier.name();
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long sumForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • reduce

        KTable<K,​V> reduce​(Reducer<V> reducer,
                         Materialized<K,​V,​KeyValueStore<org.apache.kafka.common.utils.Bytes,​byte[]>> materialized)
        Combine the value of records in this stream by the grouped key. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Materialized)). The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) provided by the given materialized. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, Materialized) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...). 

        
 KafkaStreams streams = ... // compute sum
 String queryableStoreName = "storeName" // the queryableStoreName should be the name of the store as defined by the Materialized instance
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long sumForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        materialized - an instance of Materialized used to materialize a state store. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • reduce

        @Deprecated
<W extends Window> KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                                      Windows<W> windows,
                                                      java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(windows) followed by reduce(reducer, Materialized.as(queryableStoreName))
        Combine the number of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Windows, Serde, String)). The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, Windows, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // compute sum
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-key";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> sumForKeyForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result
        windows - the specification of the aggregation Windows
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to reduce(Reducer, Windows).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • reduce

        @Deprecated
<W extends Window> KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                                      Windows<W> windows)
        Deprecated.
        use windowedBy(windows) followed by reduce(reducer)
        Combine the number of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Windows, Serde, String)). The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate and the record's value. If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, Windows, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result
        windows - the specification of the aggregation Windows
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • reduce

        @Deprecated
<W extends Window> KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                                      Windows<W> windows,
                                                      StateStoreSupplier<WindowStore> storeSupplier)
        Deprecated.
        use windowedBy(windows) followed by reduce(reducer, Materialized.as(KeyValueByteStoreSupplier))
        Combine the values of records in this stream by the grouped key and the defined windows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Windows, Serde, String)). The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, Windows, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // compute sum
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-key";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> sumForKeyForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        windows - the specification of the aggregation Windows
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • reduce

        @Deprecated
KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                   SessionWindows sessionWindows,
                                   java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(sessionWindows) followed by reduce(reducer, Materialized.as(queryableStoreName))
        Combine values of this stream by the grouped key into SessionWindows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, String)). The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, SessionWindows, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). 

        
 KafkaStreams streams = ... // compute sum
 ReadOnlySessionStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>ReadOnlySessionStore<String, Long>);
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> sumForKeyForWindows = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        sessionWindows - the specification of the aggregation SessionWindows
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to reduce(Reducer, SessionWindows).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • reduce

        @Deprecated
KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                   SessionWindows sessionWindows)
        Deprecated.
        use windowedBy(sessionWindows) followed by reduce(reducer)
        Combine values of this stream by the grouped key into SessionWindows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, String)). The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate and the record's value. If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, SessionWindows, String) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        sessionWindows - the specification of the aggregation SessionWindows
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • reduce

        @Deprecated
KTable<Windowed<K>,​V> reduce​(Reducer<V> reducer,
                                   SessionWindows sessionWindows,
                                   StateStoreSupplier<SessionStore> storeSupplier)
        Deprecated.
        use windowedBy(sessionWindows) followed by reduce(reducer, Materialized.as(KeyValueByteStoreSupplier))
        Combine values of this stream by the grouped key into SessionWindows. Records with null key or value are ignored. Combining implies that the type of the aggregate result is the same as the type of the input value (c.f. aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, String)). The result is written into a local SessionStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Reducer is applied for each input record and computes a new aggregate using the current aggregate (first argument) and the record's value (second argument): 

        
 // At the example of a Reducer<Long>
 new Reducer<Long>() {
   public Long apply(Long aggValue, Long currValue) {
     return aggValue + currValue;
   }
 }

        If there is no current aggregate the Reducer is not applied and the new aggregate will be the record's value as-is. Thus, reduce(Reducer, SessionWindows, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like sum, min, or max.

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // compute sum
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlySessionStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>ReadOnlySessionStore<String, Long>);
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> sumForKeyForWindows = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Parameters:
        reducer - a Reducer that computes a new aggregate result. Cannot be null.
        sessionWindows - the specification of the aggregation SessionWindows
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<VR> KTable<K,​VR> aggregate​(Initializer<VR> initializer,
                                  Aggregator<? super K,​? super V,​VR> aggregator,
                                  org.apache.kafka.common.serialization.Serde<VR> aggValueSerde,
                                  java.lang.String queryableStoreName)
        Deprecated.
        use aggregate(initializer, aggregator, Materialized.as(queryableStoreName).withValueSerde(aggValueSerde))
        Aggregate the values of records in this stream by the grouped key. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Initializer is applied once directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Serde, String) can be used to compute aggregate functions like count (c.f. count(String)).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // some aggregation on value type double
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long aggForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to aggregate(Initializer, Aggregator, Serde).
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • aggregate

        <VR> KTable<K,​VR> aggregate​(Initializer<VR> initializer,
                                  Aggregator<? super K,​? super V,​VR> aggregator,
                                  Materialized<K,​VR,​KeyValueStore<org.apache.kafka.common.utils.Bytes,​byte[]>> materialized)
        Aggregate the values of records in this stream by the grouped key. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Initializer is applied once directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Serde, String) can be used to compute aggregate functions like count (c.f. count()).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // some aggregation on value type double
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long aggForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        materialized - an instance of Materialized used to materialize a state store. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • aggregate

        <VR> KTable<K,​VR> aggregate​(Initializer<VR> initializer,
                                  Aggregator<? super K,​? super V,​VR> aggregator)
        Aggregate the values of records in this stream by the grouped key. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Initializer is applied once directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator) can be used to compute aggregate functions like count (c.f. count()).

        The default value serde from config will be used for serializing the result. If a different serde is required then you should use aggregate(Initializer, Aggregator, Materialized).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • aggregate

        @Deprecated
<VR> KTable<K,​VR> aggregate​(Initializer<VR> initializer,
                                  Aggregator<? super K,​? super V,​VR> aggregator,
                                  org.apache.kafka.common.serialization.Serde<VR> aggValueSerde)
        Deprecated.
        use aggregate(initializer, aggregator, Materialized.with(null, aggValueSerde))
        Aggregate the values of records in this stream by the grouped key. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Initializer is applied once directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Serde, String) can be used to compute aggregate functions like count (c.f. count()).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • aggregate

        @Deprecated
<VR> KTable<K,​VR> aggregate​(Initializer<VR> initializer,
                                  Aggregator<? super K,​? super V,​VR> aggregator,
                                  StateStoreSupplier<KeyValueStore> storeSupplier)
        Deprecated.
        use aggregate(initializer, aggregator, Materialized.as(KeyValueByteStoreSupplier))
        Aggregate the values of records in this stream by the grouped key. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Furthermore, updates to the store are sent downstream into a KTable changelog stream.

        The specified Initializer is applied once directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like count (c.f. count()).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // some aggregation on value type double
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlyKeyValueStore<String,Long> localStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>keyValueStore());
 String key = "some-key";
 Long aggForKey = localStore.get(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key

      • aggregate

        @Deprecated
<W extends Window,​VR> KTable<Windowed<K>,​VR> aggregate​(Initializer<VR> initializer,
                                                                   Aggregator<? super K,​? super V,​VR> aggregator,
                                                                   Windows<W> windows,
                                                                   org.apache.kafka.common.serialization.Serde<VR> aggValueSerde,
                                                                   java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(windows) followed by aggregate(initializer, aggregator, Materialized.as(queryableStoreName).withValueSerde(aggValueSerde))
        Aggregate the values of records in this stream by the grouped key and defined windows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per window directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Windows, Serde, String) can be used to compute aggregate functions like count (c.f. count(Windows)).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...): 

        
 KafkaStreams streams = ... // some windowed aggregation on value type double
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-key";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> aggForKeyForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. Therefore, the store name must be a valid Kafka topic name and cannot contain characters other than ASCII alphanumerics, '.', '_' and '-'. The changelog topic will be named "${applicationId}-${queryableStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "queryableStoreName" is the provide queryableStoreName, and "-changelog" is a fixed suffix. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        windows - the specification of the aggregation Windows
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to aggregate(Initializer, Aggregator, Windows, Serde).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<W extends Window,​VR> KTable<Windowed<K>,​VR> aggregate​(Initializer<VR> initializer,
                                                                   Aggregator<? super K,​? super V,​VR> aggregator,
                                                                   Windows<W> windows,
                                                                   org.apache.kafka.common.serialization.Serde<VR> aggValueSerde)
        Deprecated.
        use windowedBy(windows) followed by TimeWindowedKStream.aggregate(Initializer, Aggregator, Materialized) aggregate(initializer, aggregator, Materialized.with(null, aggValueSerde))}
        Aggregate the values of records in this stream by the grouped key and defined windows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per window directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Windows, Serde, String) can be used to compute aggregate functions like count (c.f. count(Windows)).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        For failure and recovery the store will be backed by an internal changelog topic that will be created in Kafka. The changelog topic will be named "${applicationId}-${internalStoreName}-changelog", where "applicationId" is user-specified in StreamsConfig via parameter APPLICATION_ID_CONFIG, "internalStoreName" is an internal name and "-changelog" is a fixed suffix. Note that the internal store name may not be queriable through Interactive Queries. You can retrieve all generated internal topic names via KafkaStreams.toString().

        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        windows - the specification of the aggregation Windows
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<W extends Window,​VR> KTable<Windowed<K>,​VR> aggregate​(Initializer<VR> initializer,
                                                                   Aggregator<? super K,​? super V,​VR> aggregator,
                                                                   Windows<W> windows,
                                                                   StateStoreSupplier<WindowStore> storeSupplier)
        Deprecated.
        use windowedBy(windows) followed by aggregate(initializer, aggregator, Materialized.as(KeyValueByteStoreSupplier))
        Aggregate the values of records in this stream by the grouped key and defined windows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The specified windows define either hopping time windows that can be overlapping or tumbling (c.f. TimeWindows) or they define landmark windows (c.f. UnlimitedWindows). The result is written into a local windowed KeyValueStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. Windows are retained until their retention time expires (c.f. Windows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per window directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Windows, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like count (c.f. count(Windows)).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local windowed KeyValueStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // some windowed aggregation on value type Long
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlyWindowStore<String,Long> localWindowStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>windowStore());
 String key = "some-key";
 long fromTime = ...;
 long toTime = ...;
 WindowStoreIterator<Long> aggForKeyForWindows = localWindowStore.fetch(key, timeFrom, timeTo); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Type Parameters:
        VR - the value type of the resulting KTable
        Parameters:
        initializer - an Initializer that computes an initial intermediate aggregation result
        aggregator - an Aggregator that computes a new aggregate result
        windows - the specification of the aggregation Windows
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<T> KTable<Windowed<K>,​T> aggregate​(Initializer<T> initializer,
                                          Aggregator<? super K,​? super V,​T> aggregator,
                                          Merger<? super K,​T> sessionMerger,
                                          SessionWindows sessionWindows,
                                          org.apache.kafka.common.serialization.Serde<T> aggValueSerde,
                                          java.lang.String queryableStoreName)
        Deprecated.
        use windowedBy(sessionWindows) followed by aggregate(initializer, aggregator, sessionMerger, Materialized.as(queryableStoreName).withValueSerde(aggValueSerde))
        Aggregate the values of records in this stream by the grouped key and defined SessionWindows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per session directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, String) can be used to compute aggregate functions like count (c.f. count(SessionWindows))

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local SessionStore it must be obtained via KafkaStreams#store(...). 

        
 KafkaStreams streams = ... // some windowed aggregation on value type double
 ReadOnlySessionStore<String, Long> sessionStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>sessionStore());
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> aggForKeyForSession = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Type Parameters:
        T - the value type of the resulting KTable
        Parameters:
        initializer - the instance of Initializer
        aggregator - the instance of Aggregator
        sessionMerger - the instance of Merger
        sessionWindows - the specification of the aggregation SessionWindows
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        queryableStoreName - the name of the state store created from this operation; valid characters are ASCII alphanumerics, '.', '_' and '-'. If null then this will be equivalent to aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde).
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<T> KTable<Windowed<K>,​T> aggregate​(Initializer<T> initializer,
                                          Aggregator<? super K,​? super V,​T> aggregator,
                                          Merger<? super K,​T> sessionMerger,
                                          SessionWindows sessionWindows,
                                          org.apache.kafka.common.serialization.Serde<T> aggValueSerde)
        Deprecated.
        use windowedBy(sessionWindows) followed by aggregate(initializer, aggregator, sessionMerger, Materialized.with(null, aggValueSerde))
        Aggregate the values of records in this stream by the grouped key and defined SessionWindows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local SessionStore (which is basically an ever-updating materialized view) that can be queried using the provided queryableStoreName. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per session directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, String) can be used to compute aggregate functions like count (c.f. count(SessionWindows))

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        Type Parameters:
        T - the value type of the resulting KTable
        Parameters:
        initializer - the instance of Initializer
        aggregator - the instance of Aggregator
        sessionMerger - the instance of Merger
        sessionWindows - the specification of the aggregation SessionWindows
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window

      • aggregate

        @Deprecated
<T> KTable<Windowed<K>,​T> aggregate​(Initializer<T> initializer,
                                          Aggregator<? super K,​? super V,​T> aggregator,
                                          Merger<? super K,​T> sessionMerger,
                                          SessionWindows sessionWindows,
                                          org.apache.kafka.common.serialization.Serde<T> aggValueSerde,
                                          StateStoreSupplier<SessionStore> storeSupplier)
        Deprecated.
        use windowedBy(sessionWindows) followed by aggregate(initializer, aggregator, sessionMerger, Materialized.as(KeyValueByteStoreSupplier).withValueSerde(aggValueSerde))
        Aggregate the values of records in this stream by the grouped key and defined SessionWindows. Records with null key or value are ignored. Aggregating is a generalization of combining via reduce(...) as it, for example, allows the result to have a different type than the input values. The result is written into a local SessionStore (which is basically an ever-updating materialized view) provided by the given storeSupplier. SessionWindows are retained until their retention time expires (c.f. SessionWindows.until(long)). Furthermore, updates to the store are sent downstream into a windowed KTable changelog stream, where "windowed" implies that the KTable key is a combined key of the original record key and a window ID.

        The specified Initializer is applied once per session directly before the first input record is processed to provide an initial intermediate aggregation result that is used to process the first record. The specified Aggregator is applied for each input record and computes a new aggregate using the current aggregate (or for the very first record using the intermediate aggregation result provided via the Initializer) and the record's value. Thus, #aggregate(Initializer, Aggregator, Merger, SessionWindows, Serde, org.apache.kafka.streams.processor.StateStoreSupplier) can be used to compute aggregate functions like count (c.f. count(SessionWindows)).

        Not all updates might get sent downstream, as an internal cache is used to deduplicate consecutive updates to the same window and key. The rate of propagated updates depends on your input data rate, the number of distinct keys, the number of parallel running Kafka Streams instances, and the configuration parameters for cache size, and commit intervall.

        To query the local SessionStore it must be obtained via KafkaStreams#store(...). Use StateStoreSupplier.name() to get the store name: 

        
 KafkaStreams streams = ... // some windowed aggregation on value type double
 Sting queryableStoreName = storeSupplier.name();
 ReadOnlySessionStore<String, Long> sessionStore = streams.store(queryableStoreName, QueryableStoreTypes.<String, Long>sessionStore());
 String key = "some-key";
 KeyValueIterator<Windowed<String>, Long> aggForKeyForSession = localWindowStore.fetch(key); // key must be local (application state is shared over all running Kafka Streams instances)
        For non-local keys, a custom RPC mechanism must be implemented using KafkaStreams.allMetadata() to query the value of the key on a parallel running instance of your Kafka Streams application.
        Type Parameters:
        T - the value type of the resulting KTable
        Parameters:
        initializer - the instance of Initializer
        aggregator - the instance of Aggregator
        sessionMerger - the instance of Merger
        sessionWindows - the specification of the aggregation SessionWindows
        aggValueSerde - aggregate value serdes for materializing the aggregated table, if not specified the default serdes defined in the configs will be used
        storeSupplier - user defined state store supplier. Cannot be null.
        Returns:
        a windowed KTable that contains "update" records with unmodified keys, and values that represent the latest (rolling) aggregate for each key within a window