You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2020/06/02 09:11:03 UTC
Slack digest for #dev - 2020-06-02
2020-06-01 13:30:13 UTC - Ankush: @Ankush has joined the channel
----
2020-06-01 14:00:25 UTC - Lawal Azeez: @Lawal Azeez has joined the channel
----
2020-06-01 18:42:25 UTC - Thomas Jamet: Thanks for the reply. I was hoping for a mechanism to support different types of messages (i.e. different schemas) while keeping the time ordering between them. If I use different topics for my different message types then my understanding is that a consumer who would consume the different topics would not necessarily get the messages in the order they were published.
----
2020-06-01 18:46:13 UTC - Thomas Jamet: It doesn't seem such a unique use-case to have different message types while keeping them in chronological order. Is there a Pulsar way of doing this? One way I can think of is to use a property to indicate the message type and to do the serde client-side (producers / consumers).
----
2020-06-01 22:02:35 UTC - Sijie Guo: You can disable compatibility check for that topic to achieve so.
@Shivji Kumar Jha from Nutanix did the same thing. You can check this video: <https://www.youtube.com/watch?v=zAHxgG_U67Q>
+1 : Shivji Kumar Jha
----
2020-06-02 06:29:11 UTC - Shalom Tuby: @Shalom Tuby has joined the channel
----