You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/02/10 10:51:49 UTC

[GitHub] [pulsar] youzipi edited a comment on issue #14190: 请教:event time的应用场景是什么?

youzipi edited a comment on issue #14190:
URL: https://github.com/apache/pulsar/issues/14190#issuecomment-1034769623


   > 可以确保最终状态是canceled,这句话是如何确保的,因为一个消息发过去后马上就消费了,按接收到message的顺序进行消费,如何保证cancel一定是在最后的,,加上event time也不能影响在网络中发送的顺序啊。感谢
   
   in this case, you need manually check if the message is old.
   you can also put a time field in message to achieve the same goal.
   
   but why put event time in `metadata` but not `message` ?
   it is convenient and efficient for developing future advanced features.
   (we can get the field directly instead of deserialize and scan the whole message.)
   
   you can check these in the `discusstion thread` in PIP.
   
   > for now(2022-02), i did not found any feature working on event time.
   
   > in flink, you can config `window` and `watermark` to reorder the event in a period.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org