You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In MessageMetadata the message key (partition key) is of type string while the ordering key is of type bytes.
When using the Java client to build and send a message the TypedMessageBuilder provides these methods:
key(String key)
keyBytes(byte[] key)
orderingKey(byte[] orderingKey)
For setting the key there is the possibility to use a string or byte array. Internally the bytes will be base64 encoded to string.
Would it make sense to have something similar for the ordering key for convenience, i.e. allowing to provide it as a string and then internally encoding it as a byte array?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In MessageMetadata the message key (partition key) is of type string while the ordering key is of type bytes.
When using the Java client to build and send a message the TypedMessageBuilder provides these methods:
For setting the key there is the possibility to use a string or byte array. Internally the bytes will be base64 encoded to string.
Would it make sense to have something similar for the ordering key for convenience, i.e. allowing to provide it as a string and then internally encoding it as a byte array?
Beta Was this translation helpful? Give feedback.
All reactions