[DISCUSS] Refactor StateBackend into Partitioned State and Non-Partitioned State Backends

2016-01-07 Thread Aljoscha Krettek
Hi, I’m currently examining ways to 1) change the window operators to use the partitioned state abstraction for window state and 2) implement state backends for managed memory/out-of-core state. I think it would be helpful to pull the state backend apart. Right now, for example, the DbStateBack

Re: [DISCUSS] Refactor StateBackend into Partitioned State and Non-Partitioned State Backends

2016-01-07 Thread Gyula Fóra
Hi, +1 I think it would be a good idea to separate the 2 state backends. I think you are right in most cases the new partitioned state implementations will benefit from this as it removes a lot of additional overhead (although sometimes it's nice to have the 2 together, for instance if they both