[
https://issues.apache.org/jira/browse/AVRO-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831256#action_12831256
]
Todd Lipcon commented on AVRO-406:
----------------------------------
I think it's worth noting that I'm essentially saying we should expect people
to write "mini protocols" at the application on top of avro when they want to
do really complicated stuff like this. It's a bit annoying, but I think it
still provides good benefit over "do it yourself transport" - the protocol will
be way easier to evolve, and all the other transport features will be leveraged.
Would like to see arguments against this, though, if someone has one!
> Support streaming RPC calls
> ---------------------------
>
> Key: AVRO-406
> URL: https://issues.apache.org/jira/browse/AVRO-406
> Project: Avro
> Issue Type: New Feature
> Components: java, spec
> Reporter: Todd Lipcon
>
> Avro nicely supports chunking of container types into multiple frames. We
> need to expose this to RPC layer to facilitate use cases like the Hadoop
> Datanode where a single "RPC" can yield far more data than should be buffered
> in memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.