Yep, this though is suboptimal as you imagined. Two things
* has a internally has a that is a ultra lite version of IN,
only required for the path analysis.
* Sessionization being expensive, we piggy back multiple other aggregations
that do not depend on the path or order ( count etc ) . Essen
Thanks Till and Sendoh
On 5 January 2018 at 12:38, Till Rohrmann wrote:
> Hi Alberto,
>
> currently, the queryable state is not exposed via a REST interface. You
> have to use the QueryableStateClient for that [1]. If it's not possible to
> directly connect to the machines running your Flink clu
