You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2015/02/11 19:02:13 UTC

[jira] [Resolved] (SAMZA-484) Define the serialization/deserialization format for stream tuple

     [ https://issues.apache.org/jira/browse/SAMZA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini resolved SAMZA-484.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.0

+1 Merged and committed. Tests pass locally.

> Define the serialization/deserialization format for stream tuple
> ----------------------------------------------------------------
>
>                 Key: SAMZA-484
>                 URL: https://issues.apache.org/jira/browse/SAMZA-484
>             Project: Samza
>          Issue Type: Sub-task
>          Components: sql
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Navina Ramesh
>            Priority: Minor
>              Labels: project
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-484-1.patch, SAMZA-484-2.patch, SAMZA-484-3.patch, SAMZA-484-4.patch, SAMZA-484-5.patch, SAMZA-484-6.patch, SAMZA-484.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)