attaching 2.1-rebased patch for this
- send whether we can keep sstable levels in StreamInitMessage
- send sstable level in FileMessageHeader
- during bootstrap, only do STCS in L0 to avoid getting overlap in L1
Note that this still does not handle backwards compatibility as it is quite complicated to fix and should probably be done in another ticket.
My suggested fix is that when the stream initiator sends a StreamInitMessage with CURRENT_VERSION, the receiver needs to reply with the max version that both nodes supports and the messages are then sent using that version.
Another approach would be to figure out what version the remote node is before deciding on streaming version, but that would mean we have to bump messaging version whenever we change something in a stream message which we probably shouldn't.
WDYT Yuki Morishita ?