Re: OutputFormat in streaming job

2016-05-06 Thread Andrea Sella
Hi Fabian, So I misunderstood the behaviour of configure(), thank you. Andrea 2016-05-06 14:17 GMT+02:00 Fabian Hueske : > Hi Andrea, > > actually, OutputFormat.configure() will also be invoked per task. So you > would also end up with 16 ActorSystems. > However, I think you can use synchronize

Re: OutputFormat in streaming job

2016-05-06 Thread Fabian Hueske
Hi Andrea, actually, OutputFormat.configure() will also be invoked per task. So you would also end up with 16 ActorSystems. However, I think you can use synchronized singleton object to start one ActorSystem per TM (each TM and all tasks run in a single JVM). So from the point of view of configur

Re: OutputFormat in streaming job

2016-05-06 Thread Andrea Sella
Hi Fabian, ATM I am not interesting to guarantee exactly-once processing, thank you for the clarification. As far as I know, it is not present a similar method as OutputFormat's configure for RichSinkFunction, correct? So I am not able to instantiate an ActorSystem per TM but I have to instantiat

Re: OutputFormat in streaming job

2016-05-06 Thread Fabian Hueske
Hi Andrea, you can use any OutputFormat to emit data from a DataStream using the writeUsingOutputFormat() method. However, this method does not guarantee exactly-once processing. In case of a failure, it might emit some records a second time. Hence the results will be written at least once. Hope