Thanks for the detailed explanation regarding the reasoning behind not
using opens' configuration parameters!
On Wed, Oct 11, 2017 at 1:46 AM, Chesnay Schepler
wrote:
> The Configuration parameter in open() is a relic of the previous java API
> where operators were instantiated generically.
>
>
I think we should remove that part from the best-practices documentation. I'll
quickly open a PR.
> On 11. Oct 2017, at 10:46, Chesnay Schepler wrote:
>
> The Configuration parameter in open() is a relic of the previous java API
> where operators were instantiated generically.
>
> Nowadays, t
The Configuration parameter in open() is a relic of the previous java
API where operators were instantiated generically.
Nowadays, this is no longer the case as they are serialized instead,
which simplifies the passing of parameters as you can
simply store them in a field of your UDF.
The con
I was looking for withParameters(config) in the Streaming API today. I
stumbled across the following thread.
http://apache-flink-mailing-list-archive.1008284.n3.
nabble.com/withParameters-for-Streaming-API-td9332.html#a9333
It appears that some of the StreamingAPI developers are in favor of
remov