e these two kind of operations together.
> >
> > I'd like to create a JIRA about this improvement, what's your opinions?
> >
> > Best
> > Yun Tang
> >
> > ________________
> > From: Thomas Weise
> > Sent: Tuesday, Novem
Sent: Tuesday, November 13, 2018 1:53
> To: dev@flink.apache.org
> Cc: u...@apache.org
> Subject: Re: How to use RocksDBStateBackend predefined options
>
> Sounds good. Perhaps it would also be good to allow the user to specify an
> options factory in flink-conf.yaml for more flexibilit
er 13, 2018 1:53
To: dev@flink.apache.org
Cc: u...@apache.org
Subject: Re: How to use RocksDBStateBackend predefined options
Sounds good. Perhaps it would also be good to allow the user to specify an
options factory in flink-conf.yaml for more flexibility?
Thomas
On Mon, Nov 12, 2018 at 9:48
Sounds good. Perhaps it would also be good to allow the user to specify an
options factory in flink-conf.yaml for more flexibility?
Thomas
On Mon, Nov 12, 2018 at 9:48 AM Stefan Richter
wrote:
> Hi,
>
> Ufuk is right, for historical reasons there is currently only the
> programatic way but I th
Hi,
Ufuk is right, for historical reasons there is currently only the programatic
way but I think nothing speaks fundamentally against offering configuration via
config in the future (maybe just a lot of config keys must be introduced to
cover all options).
Best,
Stefan
> On 9. Nov 2018, at 2
Hey Thomas,
On Fri, Nov 9, 2018 at 6:07 PM Thomas Weise wrote:
> Is there a way to activate the predefined options via configuration / flink-
> conf.yaml? Or only programmatically, like in [4]? The difficulty with the
> programmatic route (assuming this works now), is that in my case the client
>
Hi,
We are observing unbounded memory consumption with the default
RocksDBStateBackend configuration [1]. According to [2] it is possible to
control that through custom options or by using the predefined options from
[3].
Is there a way to activate the predefined options via configuration / flink
