[
https://issues.apache.org/jira/browse/SAMZA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172674#comment-14172674
]
Jonathan Herriott commented on SAMZA-429:
-----------------------------------------
Anyways, honestly, all of this is just my perception on the issue, and seeing
as how I'm not running the project, I won't be offended if this is a direction
you don't want to go in, so if you think this is a non-issue, then feel free to
close the ticket. In terms of having a recommended way, as you described, I
think that is a step in the right direction, however, I think eventually you'll
see a separate project pop up that people will develop against in order to make
tasks open-sourceable and reusable between companies as each company will end
up with their own protocols they want to use, but will still want the same
functionality out of tasks. If you guys end up just having a recommended way
of handling things, I'm open to creating a separate project myself for
abstracting the protocols out.
> Decouple Protocol from Task
> ---------------------------
>
> Key: SAMZA-429
> URL: https://issues.apache.org/jira/browse/SAMZA-429
> Project: Samza
> Issue Type: Improvement
> Reporter: Jonathan Herriott
>
> Maybe someone can point me in the right direction if this is wrong. One
> thing I've disliked about tasks is the fact that the protocols have to be
> baked directly into the Task, so if you want to process JSON, you have to
> treat the message contents as a HashMap, but if you want to use Avro, it
> needs to be treated as a GenericRecord object, etc. I think it would be
> super beneficial to fully abstract this from the Task object and just treat
> each thing as a "Message" object. I think the advantage of this is that you
> can test with JSON and run with Avro in production or whatever as debugging
> with JSON is a lot easier than Avro.
> The thing is, in the Task, I only care about the structure, I don't really
> care about what protocol it is. Maybe this statement is a bit naive, but I
> don't think there would ever be a good situation in which you would pass just
> a string or integer or whatever instead of some form of hierarchical message.
> In my opinion, all Serde should return a common interface for a Record for
> deserialization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
