GitHub user kasparjarek edited a discussion: KeyValue schema encoding types 
INLINE vs SEPARATED

I have a few questions regarding KeyValue schema encoding types (INLINE vs 
SEPARATED). I have seen conflicting answers from AI bots and was unable to find 
clear information in the documentation.

1. Is it true that when using INLINE encoding, the key is not used for routing 
decisions and therefore the ordering guarantees of the `Key_Shared` 
subscription type are lost?
2. What are the practical advantages and disadvantages of these two encoding 
types? If the statement above is true, why would I ever want to use INLINE type?

Thank you

GitHub link: https://github.com/apache/pulsar/discussions/25849

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to