bug? open() not getting called with RichWindowMapFunction

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

bug? open() not getting called with RichWindowMapFunction

Emmanuel

extending AbstractRichFunction gives access to the open function which is called at init if I understand correctly.

That works fine with RichMapFunction, but with RichWindowMapFunction which also extends AbstractRichFunction the open function never seems to get called.

I also tried extending AbstractRichFunction and implementing AbstractRichFunction but that does not help with this.. so it seems like the open function is just never called when setting up a mapWindow transform.

I'm using 0.9-milestone1

Is this a bug?
Thanks
   
Reply | Threaded
Open this post in threaded view
|

Re: bug? open() not getting called with RichWindowMapFunction

Gyula Fóra-2
Hi,

This was a known issue and has been fixed already on the current master.

Gyula

On Sat, May 23, 2015 at 10:26 PM, Emmanuel <[hidden email]> wrote:

extending AbstractRichFunction gives access to the open function which is called at init if I understand correctly.

That works fine with RichMapFunction, but with RichWindowMapFunction which also extends AbstractRichFunction the open function never seems to get called.

I also tried extending AbstractRichFunction and implementing AbstractRichFunction but that does not help with this.. so it seems like the open function is just never called when setting up a mapWindow transform.

I'm using 0.9-milestone1

Is this a bug?
Thanks
   

Reply | Threaded
Open this post in threaded view
|

RE: bug? open() not getting called with RichWindowMapFunction

Emmanuel
Great, thanks...
Is there a roadmap somewhere that can be consulted with a timeline for the next RC or milestone?

Thanks.


Date: Sat, 23 May 2015 23:10:59 +0200
Subject: Re: bug? open() not getting called with RichWindowMapFunction
From: [hidden email]
To: [hidden email]

Hi,

This was a known issue and has been fixed already on the current master.

Gyula

On Sat, May 23, 2015 at 10:26 PM, Emmanuel <[hidden email]> wrote:

extending AbstractRichFunction gives access to the open function which is called at init if I understand correctly.

That works fine with RichMapFunction, but with RichWindowMapFunction which also extends AbstractRichFunction the open function never seems to get called.

I also tried extending AbstractRichFunction and implementing AbstractRichFunction but that does not help with this.. so it seems like the open function is just never called when setting up a mapWindow transform.

I'm using 0.9-milestone1

Is this a bug?
Thanks
   

Reply | Threaded
Open this post in threaded view
|

Re: bug? open() not getting called with RichWindowMapFunction

rmetzger0
Since Flink is a community driven open source project, there is no fixed timeline.

But there is a thread on this mailing list discussing the next release. My gut feeling (it depends on the community) tells me that we'll have a 0.9 release in the next one or two weeks.

On Tue, May 26, 2015 at 7:34 PM, Emmanuel <[hidden email]> wrote:
Great, thanks...
Is there a roadmap somewhere that can be consulted with a timeline for the next RC or milestone?

Thanks.


Date: Sat, 23 May 2015 23:10:59 +0200
Subject: Re: bug? open() not getting called with RichWindowMapFunction
From: [hidden email]
To: [hidden email]


Hi,

This was a known issue and has been fixed already on the current master.

Gyula

On Sat, May 23, 2015 at 10:26 PM, Emmanuel <[hidden email]> wrote:

extending AbstractRichFunction gives access to the open function which is called at init if I understand correctly.

That works fine with RichMapFunction, but with RichWindowMapFunction which also extends AbstractRichFunction the open function never seems to get called.

I also tried extending AbstractRichFunction and implementing AbstractRichFunction but that does not help with this.. so it seems like the open function is just never called when setting up a mapWindow transform.

I'm using 0.9-milestone1

Is this a bug?
Thanks