Hi Aljoscha Thanks for your reply.
Regarding question 2, the web dashboard does provide a properties section, besides ( Plan <http://ec2-52-58-144-190.eu-central-1.compute.amazonaws.com:8081/#/jobs/1d5973f40ab0951e7c733a2c439b013a>Timeline <http://ec2-52-58-144-190.eu-central-1.compute.amazonaws.com:8081/#/jobs/1d5973f40ab0951e7c733a2c439b013a/timeline>Exceptions <http://ec2-52-58-144-190.eu-central-1.compute.amazonaws.com:8081/#/jobs/1d5973f40ab0951e7c733a2c439b013a/exceptions>Properties <http://ec2-52-58-144-190.eu-central-1.compute.amazonaws.com:8081/#/jobs/1d5973f40ab0951e7c733a2c439b013a/properties>Configuration <http://ec2-52-58-144-190.eu-central-1.compute.amazonaws.com:8081/#/jobs/1d5973f40ab0951e7c733a2c439b013a/config> ) Whats the most common way to handle properties in flink? Is there a general way to go and any kind of integration in flink? --Simon > On 21 May 2016, at 10:44, Aljoscha Krettek <aljos...@apache.org> wrote: > > Hi Simon, > regarding 1. yes, the value that you get from state_item.value() and that you > set using state_item.update() is scoped to the key of the incoming element. > > regarding 2. the open(conf: Configuration) signature is legacy from how > Functions used to work quite a while back. In the streaming API this > Configuration is always empty. If you want to configure your user function > you can have the values as fields in your class and pass them in the > constructor. > > Cheers, > Aljoscha > > On Fri, 20 May 2016 at 17:49 simon peyer <simon.pe...@soom-it.ch > <mailto:simon.pe...@soom-it.ch>> wrote: > Hi folks > > I'm extending a RichFlatMapFunction in order to use states on a keyed stream. > Concerning this i have two questions: > > 1. I have a var state_item: ValueState[Option[String]] as a local variable > in this class. Initialized with state_item = getRuntimeContext.getState(new > ValueStateDescriptor..... in the open function. > Is the field state_item for every key different? > > In other words if I have a key with val1 and val2 will these get two > different states? > > > 2. The open function contains a override def open(conf: Configuration) > configuration. > Is there a way to input a custom configuration in there? > > Thanks Simon
