ProcessFunction broke : Flink 1.3 upgrade

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

ProcessFunction broke : Flink 1.3 upgrade

rhashmi
with 1.3 what should we use for processFunction?


org.apache.flink.streaming.api.functions.RichProcessFunction
org.apache.flink.streaming.api.functions.ProcessFunction.{OnTimerContext, Context}
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ProcessFunction broke : Flink 1.3 upgrade

Tzu-Li (Gordon) Tai
Hi,

The RichProcessFunction variant gives access to the functionality provided by the RichFunction interface (e.g. allows overriding the `open` function lifecycle method, access to the runtime context, etc.).
Whether or not to use it depends on your use case. You should be able to just continue using whatever you were using before 1.3.

Cheers,
Gordon

On 5 June 2017 at 11:03:14 PM, rhashmi ([hidden email]) wrote:

with 1.3 what should we use for processFunction?


org.apache.flink.streaming.api.functions.RichProcessFunction
org.apache.flink.streaming.api.functions.ProcessFunction.{OnTimerContext,
Context}



--
View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ProcessFunction-broke-Flink-1-3-upgrade-tp13492.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ProcessFunction broke : Flink 1.3 upgrade

rhashmi
yes i see that so shall i update code from RichProcessFunction to RichFunction(based object)? The implementation throw compile exception as RichProcessFunction has been removed from 1.3.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ProcessFunction broke : Flink 1.3 upgrade

Tzu-Li (Gordon) Tai
Hi,

Sorry for my misunderstanding here.

Yes, the RichProcessFunction variant was removed in 1.3.
Now, ProcessFunction has been changed to always be a RichFunction, so access to the runtime context / lifecycle methods is always available through the ProcessFunction interface.
You should simply use ProcessFunction now.

Cheers,
Gordon


On 6 June 2017 at 9:14:30 AM, rhashmi ([hidden email]) wrote:

yes i see that so shall i update code from RichProcessFunction to
RichFunction(based object)? The implementation throw compile exception as
RichProcessFunction has been removed from 1.3.



--
View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ProcessFunction-broke-Flink-1-3-upgrade-tp13492p13498.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
Loading...