Unfortunately, I didn't have time to work on this yet and it looks
like I won't have time this week.
I've created the following issue to track the implementation with two sub tasks:
https://issues.apache.org/jira/browse/FLINK-5779
If someone else wants to take this up in the meantime, feel free t
+1 and thanks for volunteering for an initial implementation.
Looking forward to auto-scaling of network buffers.
On Tue, Feb 7, 2017 at 3:04 AM, Ufuk Celebi wrote:
> I fully agree with you Greg.
>
> Since this is doomed to get out of sync again very shortly after clean up,
> I vote to automate
+1 for automating. The more automation the fewer mistakes we can make :-)
On Tue, Feb 7, 2017 at 11:13 AM, Robert Metzger wrote:
> +1 to automate this and describe the config parameters in the code.
>
> That's exactly the approach Apache Kafka is taking as well for their
> config.
>
> On Tue, Fe
+1 to automate this and describe the config parameters in the code.
That's exactly the approach Apache Kafka is taking as well for their config.
On Tue, Feb 7, 2017 at 9:04 AM, Ufuk Celebi wrote:
> I fully agree with you Greg.
>
> Since this is doomed to get out of sync again very shortly after
I fully agree with you Greg.
Since this is doomed to get out of sync again very shortly after clean up, I
vote to automate this. Stephan introduced the ConfigOption type, which makes it
easy to define the options. It's already planned to migrate all configuration
options from ConfigConstants to
Hi devs,
Flink's Configuration page [1] has grown intimidatingly long and complex.
Options are described across three main sections: common options (single
section), advanced options (multiple sections), and full reference. The
trailing "background" section further describes the most impactful opt
