perf(stream): optimize sink latency when sink pk mismatch about risingwave

[st1page]

Does it mean that the user needs to be aware of the "wrong" results and somehow also be able to tolerate a temporary wrong result in the user's application?

Just try to understand the scope of this improvement that can be applied to

1. the downstream system must be an "upsert" system, in other words, when the system receives a new inserted value, it should overwrite the exist value in the system with the same key.
2. the result of a specific will be "eventually correct" but maybe some key will lost for a while... (I think maybe there could be another solution when I write this. maybe we can delay the delete operation to achieve a better experience for user)
3. the order of different key's update during a barrier is not guaranteed. And that's not guaranteed in our current implementation too.

[lmatz]

Does it mean that the user needs to be aware of the "wrong" results and somehow also be able to tolerate a temporary wrong result in the user's application?

Just try to understand the scope of this improvement that can be applied to