Description
It came out in the discussion for streaming SQL that we will need to define the serialization/deserialization format for stream tuple.
The ideal serialization/deserialization format should allow both forward and backward compatibility on additional/missing fields in the data.
Several choices to be considered:
1) Avro
2) Protobuf
3) Flatbuffer
It might also be interesting to consider a pluggable serialization interface that allows different serialization methods for different Samza jobs.
Attachments
Attachments
Issue Links
- relates to
-
SAMZA-429 Decouple Protocol from Task
- Open