Streams: consider allowing non-numerical values for publishingId about rabbitmq-server HOT 3 CLOSED

@zenios thank you for the context. We move the majority of issues to discussions, at least at first, because they lack context. But this is a fairly specific change request and you did explain what you are doing and why. Thank you.

My primary concern is that this would be a breaking protocol change, so we can likely only ship it in 4.0, if publishingId even can accept non-numerical values.

from rabbitmq-server.

Protocol wise indeed it would be. The clients though shipped as of now i am sure can be converted in a compatible way to support old and new way of working.

For informational purposes is there a specific reason publishingId was designed as a uint64 instad of byte[]?

from rabbitmq-server.

@zenios according to other members of the team, this was a conscious protocol design decision. Positive integers are unique, easy to reason about, and most importantly, are very efficient to compare.

I don't have an alternative to offer for Debezium but we would like to keep the protocol this way.

from rabbitmq-server.