osal.
>
>
>
> -Original Message-
> From: Kostas Kloudas [mailto:k.klou...@data-artisans.com]
> Sent: Thursday, May 18, 2017 11:49 AM
> To: dev@flink.apache.org
> Subject: Re: ListState to List
>
> Hi Radu,
>
> Why not using a ValueState that inside stored th
it would be worth
considering have many specialized types of states - hence my proposal.
-Original Message-
From: Kostas Kloudas [mailto:k.klou...@data-artisans.com]
Sent: Thursday, May 18, 2017 11:49 AM
To: dev@flink.apache.org
Subject: Re: ListState to List
Hi Radu,
Why not using a
e appropriate. What do you think?
>
> -Original Message-
> From: Aljoscha Krettek [mailto:aljos...@apache.org]
> Sent: Thursday, May 18, 2017 12:15 AM
> To: dev@flink.apache.org
> Subject: Re: ListState to List
>
> Hi,
> The interface is restrictive on purpose because depending
users would use the one it is more
appropriate. What do you think?
-Original Message-
From: Aljoscha Krettek [mailto:aljos...@apache.org]
Sent: Thursday, May 18, 2017 12:15 AM
To: dev@flink.apache.org
Subject: Re: ListState to List
Hi,
The interface is restrictive on purpose because depe
Hi,
The interface is restrictive on purpose because depending on the state backend
it might not be possible to provide a List-like interface. There might be state
backends that stream in the list from somewhere else or other restrictions. If
we now allowed a more general interface here we would
Hi,
I would like to work with ListState, more specifically I would need to access
the contents and sort them. For this I would need a collection type (e.g., the
List, Array...).
However, I see that if I have a variable of type <> the
only interfaces I have are:
state.get -> which returns an Ite
