[
https://issues.apache.org/jira/browse/AVRO-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880694#action_12880694
]
Philip Zeyliger commented on AVRO-578:
--------------------------------------
It's a question of whether we are considering the Plugin API evolving or
stable, and I'm not sure. The safest thing to do is to add more methods to the
RPCContext class, representing the clearer API you propose, and mark as
deprecated the old ones. The code will continue calling both for a release,
until we can delete the deprecated methods. If we're less scrupulous, we could
delete the old methods altogether, but that might cause someone pain.
Doug, do you have an opinion?
> Add RPC Payload to RPCContext class
> -----------------------------------
>
> Key: AVRO-578
> URL: https://issues.apache.org/jira/browse/AVRO-578
> Project: Avro
> Issue Type: Sub-task
> Components: java
> Reporter: Patrick Wendell
> Assignee: Patrick Wendell
> Attachments: AVRO-578.patch, AVRO-578.patch.v2
>
>
> For stats/monitoring it is helpful to see how many bytes are encoded for a
> given RPC call. Right now Encoder's don't track how many payload bytes are
> actually written out when encoding is done.
> Ideally this bytesWritten() would be in Encoder interface, however not sure
> JSON plugin can track the number of characters actually written, so
> alternatively just could be added to BinaryEncoder, and stats plugin will
> only provide payload sizes when that encoder is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
