[
https://issues.apache.org/jira/browse/HADOOP-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903483#action_12903483
]
Doug Cutting commented on HADOOP-6930:
--------------------------------------
> Here clients HAVE to choose between 'reflect' and 'specific' Avro engine, but
> that should be ok for now.
That would work if you only transition protocols to Specific and never wish to
rely on Reflect. Since some parameter types are used by multiple protocols,
this requires you to transition more (all?) protocols at once, whereas, if some
parameters could use Reflect, you could transition things from Writable to Avro
protocol-by-protocol, which might be easier to debug. But
AvroSpecificRpcEngine should be easy to write, and, long-term, when all
protocols use Specific, we'll want this, so it'd be a good addition. +1
> AvroRpcEngine doesn't work with generated Avro code
> ---------------------------------------------------
>
> Key: HADOOP-6930
> URL: https://issues.apache.org/jira/browse/HADOOP-6930
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Reporter: Sharad Agarwal
>
> AvroRpcEngine uses 'reflect' based java implementation. There should be a way
> to have it work with 'specific' (generated code from avro idl).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
