Hi,

Is it possible to support two different `TimeCharacteristic` in one job at
the same time?
I guess the answer is no. So I don't think there exists such a scenario.


M Singh <mans2si...@yahoo.com> 于2019年7月19日周五 上午12:19写道:

> Hey Folks - Just checking if you have any pointers for me.  Thanks for
> your advice.
>
> On Sunday, July 14, 2019, 03:12:25 PM EDT, M Singh <mans2si...@yahoo.com>
> wrote:
>
>
> Also, are the event time timers and processing time timers handled
> separately - ie,  if I register event time timer and then use the same
> timestamp to delete processing time timer - will it remove the event time
> timer registration ?
>
> In the example
> https://github.com/streaming-with-flink/examples-scala/blob/master/src/main/scala/io/github/streamingwithflink/chapter6/CoProcessFunctionTimers.scala#L87
>  should
> the delete and register be on the processing time timer and is it ok to
> delete event time timer and register processing time timer ?
>
>   override def processElement2(
>       switch: (String, Long),
>       ctx: CoProcessFunction[SensorReading, (String, Long),
> SensorReading]#Context,
>       out: Collector[SensorReading]): Unit = {
>
>     // enable reading forwarding
>     forwardingEnabled.update(true)
>     // set disable forward timer
>     val timerTimestamp = ctx.timerService().currentProcessingTime() +
> switch._2
>     val curTimerTimestamp = disableTimer.value()
>     if (timerTimestamp > curTimerTimestamp) {
>       // remove current timer and register new timer
>      * ctx.timerService().deleteEventTimeTimer(curTimerTimestamp)*
> *      ctx.timerService().registerProcessingTimeTimer(timerTimestamp)*
>       disableTimer.update(timerTimestamp)
>     }
>   }
>
>
>
>
>
> On Sunday, July 14, 2019, 01:52:44 PM EDT, M Singh <mans2si...@yahoo.com>
> wrote:
>
>
> Hi:
>
> If I register both event time timer and processing time timer with the
> same timestamp for a particular key - will they both fire or only one will
> fire ? If only one, what will be its time domain ?
>
> Thanks
>

Reply via email to