[ 
https://issues.apache.org/jira/browse/FLINK-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-24356:
-----------------------------------
    Labels: pull-request-available  (was: )

> Not able to cancel delayed message using remote stateful function mode
> ----------------------------------------------------------------------
>
>                 Key: FLINK-24356
>                 URL: https://issues.apache.org/jira/browse/FLINK-24356
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System / Stateful Functions
>    Affects Versions: statefun-3.1.0
>            Reporter: Julia Pedrycz
>            Assignee: Igal Shilman
>            Priority: Major
>              Labels: pull-request-available
>
> My use case is processing delayed messages with ability to cancel them and 
> update their delay. Whole logic is to wait with sending messages from ingress 
> to egress. 
> At first I worked with embedded mode, with 
> org.apache.flink.statefun.sdk.Context. Just for testing I’ve made a function 
> that invoked cancelDelayedMessage() method and straight after sendAfter() 
> method. I used message id as cancellation token. My function worked just 
> fine, message was overridden (cancelled and send with new delay).
> After that I wanted to switch to remote mode, so I used 
> org.apache.flink.statefun.sdk.java.Context. I’ve made similar function as 
> previously, but it did not work. Just to be sure that cancellation works, I 
> invoked sendAfter() and straight after that cancelDelayedMessage() method. 
> Messages were still appearing on egress topic after original delay. 
> Questions:
> 1. Whether cancelDelayedMessage() is working in remote mode? 
> 2. Should it work the same like in embedded mode?
> 3. Should it work as expected if we call cancelDelayedMessage() in a moment 
> after sendAfter()? (for testing purposes)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to