[
https://issues.apache.org/jira/browse/THRIFT-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665874#comment-13665874
]
Carl Yeksigian commented on THRIFT-1975:
----------------------------------------
I think the best fix for this would be to reset the read size at the end of a
message; it means that we record the size that we set up the protocol with,
then readMessageEnd would reset the read length to that value. A little extra
overhead, but not too much, and I think it will be better behavior.
> TBinaryProtocol CheckLength can't be used for a client
> ------------------------------------------------------
>
> Key: THRIFT-1975
> URL: https://issues.apache.org/jira/browse/THRIFT-1975
> Project: Thrift
> Issue Type: Bug
> Components: Java - Library
> Reporter: T Jake Luciani
> Fix For: 1.0
>
>
> If you look at CASSANDRA-5529 you can see the Hadoop format will throw an
> exception because the limit is set for the protocol but it's used for many
> calls since it's called from a thrift client.
> We need a way to reset the call at the end of each rpc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
