Re: [DISCUSSION] Database state backend

2016-03-19 Thread Gyula Fóra
Hey, Yes, I agree that it is probably best to remove this backend from Flink and make it an external library instead. I will prepare a JIRA and PR. Gyula Aljoscha Krettek ezt írta (időpont: 2016. márc. 16., Sze, 10:35): > Hi, > if you yourself (Gyula) don’t want to maintain it anymore in the

Re: [DISCUSSION] Database state backend

2016-03-16 Thread Aljoscha Krettek
Hi, if you yourself (Gyula) don’t want to maintain it anymore in the Flink codebase I would vote to move it to an external repository. If you are not using it anymore I’m afraid no one will really work on it. On more thing. When using the DB state backend savepoints don’t work. Cleanup/compact

Re: [DISCUSSION] Database state backend

2016-03-14 Thread Ufuk Celebi
On Mon, Mar 14, 2016 at 11:20 AM, Gyula Fóra wrote: > We developed (and contributed) the DB state backend to be able to handle > large state sizes, but have moved to RocksDB for much better read/write > performance. I have a pending PR with some improvements to the MySQL > adapter but the question

[DISCUSSION] Database state backend

2016-03-14 Thread Gyula Fóra
Hello everyone! I would like to start a discussion regarding the future of the Database state backend for the streaming API. The main question is whether we want to keep this as a flink-contrib moduel and continue development as part of Flink or should we move it to an outside library. Just as a