-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEI8mthP+5zxXZZdDSO4miYXKq/OgFAl5XcjwACgkQO4miYXKq
/OjP5w//bJmVYo/XJ8nwkaFkXC48/zgoEzDvA2ZZ+cGhM9D+rXaPr0HpxKZPgZ+a
kjlhC+wwZTPbuEDezmmz4FyoyUOaT0sBr2sk/Pay4jOXo/FeI831+VxuexzuwMJf
YCsFlAcqO8rGpnBzQgwO1QLt0ZI358LXCA5wgwhFl6LLpg5dA562jzggfnV0xcfh
B/zm4loaKMCZCutCT3Dfswz7vkEvxTdGZo47ilfeLF37rD1z89EYaBnT67CaG8FI
7TpqaZ8HRQpC83d/S3SDJiK/Y+1/WD2bmmUKyr67a7lJdHfEcXYo03HWvHO5brhR
xq/eb91w0+w1lhAWD+jD7ouvaMlpYqh2sADLthYbr0rnlm8M2gfCHKmMr45l5ANi
2LnwyKeiwsv4ahHf9a7wMsa/9HfEarfG4dIpGHJyFXuzREmnZEA0Lf3ssE34L0u6
0CdKm2E3Ty8//tls8WssamgKlsQDaCZCi3bt4fI8wq4S3gSrXtrKGUgXoqVfAV9X
xP37NX6kstl6Z446MGTcOMIUwNOnSj0RaQeGsgSZOexvAGrLm72gHVvoeYzI63uT
oIoHZFXRN7Df6E3os8GL4pYRv6Fe6A9paI4LOSovfU7szB8ZuWMmEJ2VNynibgFl
CQTo/2o4xoI75xb09HvkK7uKRqtXkvA9mN+M7EeFeL8TMBFZ5dw=
=+BzF
-----END PGP SIGNATURE-----
What you call "sliding window" is called "hopping window" in Kafka Streams.
And yes, you can use a windowed-store for this case: In fact, a
non-overlapping tumbling window is just a special case of a hopping
window with advance == window-size.
In Kafka Streams we have a single implementation for hopping windows
(that we use for tumbling windows, too):
https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/internals/KStreamWindowAggregate.java
-Matthias
On 2/26/20 9:47 PM, Sachin Mittal wrote:
> Hi,
> So far how I have understood is that when we create a rocksdb window store;
> we specify a window size and retention period.
>
> So windows are created from epoch time based on size, say size if 100 then
> windows are:
> [0, 100), [100, 200), [200, 300) ...
>
> Windows are retained based on retention period and after which it is
> dropped.
>
> Also a window is divided into segments which is implemented using a treemap.
>
> Please confirm if my understanding is correct.
>
> Also looks from all this is that windows are always hopping.
>
> Is there a case of sliding windows that can be created? If yes how?
> Example of sliding window would be:
> [0, 100), [75, 175), [150, 250) ...
>
> Thanks
> Sachin
>
iQIzBAEBCAAdFiEEI8mthP+5zxXZZdDSO4miYXKq/OgFAl5XcjwACgkQO4miYXKq
/OjP5w//bJmVYo/XJ8nwkaFkXC48/zgoEzDvA2ZZ+cGhM9D+rXaPr0HpxKZPgZ+a
kjlhC+wwZTPbuEDezmmz4FyoyUOaT0sBr2sk/Pay4jOXo/FeI831+VxuexzuwMJf
YCsFlAcqO8rGpnBzQgwO1QLt0ZI358LXCA5wgwhFl6LLpg5dA562jzggfnV0xcfh
B/zm4loaKMCZCutCT3Dfswz7vkEvxTdGZo47ilfeLF37rD1z89EYaBnT67CaG8FI
7TpqaZ8HRQpC83d/S3SDJiK/Y+1/WD2bmmUKyr67a7lJdHfEcXYo03HWvHO5brhR
xq/eb91w0+w1lhAWD+jD7ouvaMlpYqh2sADLthYbr0rnlm8M2gfCHKmMr45l5ANi
2LnwyKeiwsv4ahHf9a7wMsa/9HfEarfG4dIpGHJyFXuzREmnZEA0Lf3ssE34L0u6
0CdKm2E3Ty8//tls8WssamgKlsQDaCZCi3bt4fI8wq4S3gSrXtrKGUgXoqVfAV9X
xP37NX6kstl6Z446MGTcOMIUwNOnSj0RaQeGsgSZOexvAGrLm72gHVvoeYzI63uT
oIoHZFXRN7Df6E3os8GL4pYRv6Fe6A9paI4LOSovfU7szB8ZuWMmEJ2VNynibgFl
CQTo/2o4xoI75xb09HvkK7uKRqtXkvA9mN+M7EeFeL8TMBFZ5dw=
=+BzF
-----END PGP SIGNATURE-----
What you call "sliding window" is called "hopping window" in Kafka Streams.
And yes, you can use a windowed-store for this case: In fact, a
non-overlapping tumbling window is just a special case of a hopping
window with advance == window-size.
In Kafka Streams we have a single implementation for hopping windows
(that we use for tumbling windows, too):
https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/internals/KStreamWindowAggregate.java
-Matthias
On 2/26/20 9:47 PM, Sachin Mittal wrote:
> Hi,
> So far how I have understood is that when we create a rocksdb window store;
> we specify a window size and retention period.
>
> So windows are created from epoch time based on size, say size if 100 then
> windows are:
> [0, 100), [100, 200), [200, 300) ...
>
> Windows are retained based on retention period and after which it is
> dropped.
>
> Also a window is divided into segments which is implemented using a treemap.
>
> Please confirm if my understanding is correct.
>
> Also looks from all this is that windows are always hopping.
>
> Is there a case of sliding windows that can be created? If yes how?
> Example of sliding window would be:
> [0, 100), [75, 175), [150, 250) ...
>
> Thanks
> Sachin
>
Comments
Post a Comment